Yes — Hermes Agent can build, launch and manage your cold email campaigns 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. Cold email through Hermes Agent suits people who keep their tooling in version-controlled config: add the WarmySender block to ~/.hermes/config.yaml, run /reload-mcp, sign in, and drive campaigns from the chat. Every tool on this page is then one sentence away.
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 cold email |
|---|---|
| Can | Create a multi-step campaign, edit it, and set the sending window and daily limits. |
| Can | Start, pause and resume a campaign — starting only hands it to the scheduler. |
| Can | Add prospects one at a time or in bulk, update their details, and enroll or unenroll them. |
| Can | Work from your saved email templates instead of writing every email from scratch. |
| Can | Read and add to your suppression list so the wrong people are never contacted. |
| Can | Report on every campaign and explain why nothing went out today. |
| Can | Add a branded tracking domain and check that it is set up correctly. |
| Can | Set the postal address and opt-out wording used in your email footer. |
| Cannot | Send an email itself — it writes the campaign and WarmySender’s scheduler sends at your safe pace. |
| Cannot | Raise a daily cap, a warmup stage or a domain ceiling — nothing it can call moves a limit. |
| Cannot | Connect or disconnect a mailbox — credentials never pass through an agent. |
| Cannot | Switch off the opt-out in your footer — it can change the style, never remove it. |
| Cannot | Read or reply to responses — 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 three-step campaign called "Agency founders" for this list, weekdays only, from my two warmed mailboxes, then start it.
Pause every campaign that uses the sales@ mailbox until Monday.
Why did the "Q4 partners" campaign send nothing yesterday?
Add these 40 people to the suppression list and take them out of any running campaign.
Build a three-step campaign called "Agency founders" from the addresses below, weekdays only, and start it once I confirm.
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 cold email campaigns. 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 a mailbox’s daily cap, your domain’s ceiling or the pace across the sending window. 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 mailbox once in WarmySender; after that Hermes Agent can use it.
Nothing goes out in a burst. Starting a campaign only queues it, and WarmySender’s scheduler drains that queue at your normal daily pace across your sending window, inside each mailbox’s limit and your domain’s ceiling. Pausing is one sentence and is never blocked, and everything the agent built is a normal campaign you can open, edit or delete.
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