Yes — Hermes Agent can build, launch and manage your WhatsApp 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. WhatsApp campaigns via Hermes Agent suit a team standardising on one agent config across machines: the same block gives every machine the WarmySender tools. Build the intro and follow-up from the chat and ask where the number sits on its ramp.
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 WhatsApp outreach |
|---|---|
| Can | Create a WhatsApp campaign on a connected number and choose the steps and waits. |
| Can | Start, pause and resume a campaign, and enroll the people you choose. |
| Can | Report on results and check the health of every connected number. |
| Cannot | Send a WhatsApp message itself — WarmySender’s scheduler paces every message with a natural pause between them. |
| Cannot | Raise the daily, first-message or hourly budget, or shorten a new number’s ramp. |
| Cannot | Connect or disconnect a WhatsApp number — that stays in the app. |
| Cannot | Fire messages in a burst — a large enrollment drains at the number’s safe pace. |
| 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 WhatsApp campaign on my business number: a short intro, then a follow-up three days later if they have not replied, and enroll this list.
Pause every WhatsApp campaign until the new number has finished ramping.
How is my WhatsApp number doing today, and how many first messages does it have left?
Show me reply rates for every WhatsApp campaign this month.
Create a two-message WhatsApp campaign on my business number and enroll the numbers below.
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 WhatsApp 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 the daily, first-message or hourly budget, or a new number’s ramp. 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 WhatsApp number once in WarmySender; after that Hermes Agent can use it.
No. New numbers ramp up gradually and stay within a safe daily, first-message and hourly budget with a natural pause between messages, whether a person or an agent created the campaign. The agent can tell you where the number is on its ramp and when it picks up again; it cannot move it.
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