Yes — Hermes Agent can build, launch and manage your LinkedIn campaigns, posts and recruiter jobs in WarmySender, all in plain language, through the same 78-tool connection Claude, ChatGPT, Cursor, Codex, OpenClaw, and Hermes Agent share. You ask in Hermes Agent’s chat, configured from ~/.hermes/config.yaml. It never sends a message itself and can never raise a limit: it writes the campaign and hands it to WarmySender’s scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits no matter who is driving. Connecting and disconnecting accounts stays in the app.
Hermes Agent is configured from a file, and you talk to it in its own chat once the WarmySender block is loaded. It connects through a short block in ~/.hermes/config.yaml; run /reload-mcp in the chat and sign in when prompted. LinkedIn outreach via Hermes Agent suits an operator who already runs Hermes Agent for other work and wants LinkedIn campaigns alongside it: create the campaign, enroll profiles, and ask about account health from the same chat. Invites and messages are paced by the scheduler, not the agent.
Every "can" below stands on a real tool in the WarmySender connection. Every "cannot" is not a setting — there is simply nothing an agent can call that does it.
| Can / cannot | What that means for LinkedIn outreach |
|---|---|
| Can | Create a connection-and-message campaign and choose the account and steps. |
| Can | Start, pause and resume a campaign, and enroll the people you choose. |
| Can | Draft, publish and delete posts, and read their engagement. |
| Can | Create, publish and close recruiter job postings and read the applicants. |
| Can | Report on campaign stats, account health, and why an account is quiet today. |
| Cannot | Send an invite or a message itself — WarmySender’s scheduler spaces every action inside your account’s daily and hourly limits. |
| Cannot | Raise a daily or hourly limit, shorten the ramp on a newer account, or skip a cooldown. |
| Cannot | Connect or disconnect a LinkedIn account — that stays with you in the app, and a LinkedIn seat is required. |
| Cannot | Fire actions in a burst — enrolling a thousand people still goes out at the safe rate, spread over time. |
| Cannot | Read or reply to conversations — replies stay in WarmySender’s inbox, with you. |
Hermes Agent reads a short block in its config file, reloads, and signs in — after that, every WarmySender tool is one sentence away.
Add this to ~/.hermes/config.yaml, then run /reload-mcp in the chat and sign in when prompted.
File: ~/.hermes/config.yaml
mcp_servers:
warmysender:
url: "https://warmysender.com/mcp"
auth: oauthPrefer a key? Create one under Settings › API Keys and choose exactly which permissions it carries, including read-only. With a key, the Hermes Agent route is: Add this to ~/.hermes/config.yaml, then run /reload-mcp in the chat.
Both routes reach the same workspace and stay inside the same safe limits. Every agent's steps live on the AI Agents hub.
Create a LinkedIn campaign called "Founders Q4" on my main account: connect first, message three days after they accept, enroll these 60 profiles, then start it.
Pause every LinkedIn campaign on that account until Monday.
Why is my LinkedIn account quiet today, and when does it pick up again?
Publish a post about our new release, then show me the engagement in two days.
Create a LinkedIn campaign on my main account from the profiles below — connect, then message three days after acceptance — and enroll them.
Hermes Agent never sends a message itself and can never raise a limit. Creating or launching a campaign only writes it and hands it to WarmySender's scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits and a gradual ramp — the same protections that apply when a human clicks the buttons. Connecting and disconnecting accounts stays in the app. Account safety always wins.
Yes. Connect Hermes Agent to WarmySender and ask in plain language, in Hermes Agent’s chat, configured from ~/.hermes/config.yaml — it can build, launch and manage your LinkedIn campaigns, posts and recruiter jobs. It never sends a message itself and can never raise a limit: it writes the campaign and hands it to WarmySender’s scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits no matter who is driving. Connecting and disconnecting accounts stays in the app.
Hermes Agent reads a short block in its config file, reloads, and signs in — after that, every WarmySender tool is one sentence away. Add this to ~/.hermes/config.yaml, then run /reload-mcp in the chat and sign in when prompted. The block for ~/.hermes/config.yaml is: mcp_servers: warmysender: url: "https://warmysender.com/mcp" auth: oauth — the server address is https://warmysender.com/mcp. The steps are on this page under "Connect Hermes Agent", and the full install hub for every agent is at /ai-agents.
No. Nothing an agent can call moves a limit — not the daily or hourly invite and message limits, the ramp on a newer account or a cooldown. Hermes Agent can read where you are against a limit and tell you when a pause lifts; WarmySender’s scheduler decides what actually goes out.
No. Connecting and disconnecting accounts stays in the app on purpose — a credential should never pass through an agent or a chat log. Connect the LinkedIn account once in WarmySender; after that Hermes Agent can use it.
No. The agent never sends an invite or a message directly and can never raise a limit. Creating or launching a campaign only writes the plan and hands it to WarmySender’s scheduler, which paces every LinkedIn action inside safe daily and hourly caps and a gradual ramp — the same protections that apply when a human clicks the buttons. Run only one automation tool per account; account safety always wins.
Under mcp_servers in ~/.hermes/config.yaml, exactly as shown on this page, with the address https://warmysender.com/mcp. Then run /reload-mcp in the chat and sign in when prompted — no restart needed.
Run /reload-mcp in the chat: Hermes Agent reads the file on reload, not on save. Then check the indentation of the block (the file is whitespace-sensitive) and that the address reads exactly https://warmysender.com/mcp.
Yes. Create a key under Settings › API Keys and use the key form of the block on the AI Agents hub; the sign-in form on this page is the one that stores no key in the file.
Last updated: 2026-09-09