Integration
Hermes Agent WhatsApp Integration: Mobile Bot Setup and Safe Workflows
Connect Hermes Agent to WhatsApp for private mobile requests, group handoffs, media-aware workflows, scheduled reports, and safe gateway rollout.
Quick answer
Use Hermes Agent WhatsApp when you want a phone-first agent surface for trusted contacts or groups. Start with one private smoke test, confirm the active profile and allowed contacts, then expand to groups, media, cron reports, and project workflows only after logs are clean.
Managed cloud · API costs included · No gateway maintenance
Best for
People who want Hermes reachable from a private or team messaging app instead of only the terminal.
Mobile approvals and short operational requests where opening a laptop would slow the workflow down.
Team-visible reports from cron jobs, deploy checks, support triage, or incident response.
Narrow project agents where the channel itself defines the work boundary.
Features
- ✓WhatsApp private chat and group workflow support
- ✓Mobile-first approvals and short operational requests
- ✓Media handoffs when the configured bridge supports them
- ✓WhatsApp gateway access for trusted chat-based Hermes requests
- ✓Private smoke test before group or production rollout
- ✓Delivery target for cron reports, incident summaries, approvals, and project updates
- ✓Profile-level credential and tool boundaries for safer mobile/team use
- ✓Support for routing chat requests into tools such as GitHub, Linear, Notion, webhooks, or terminal workflows
Setup path
- 1Prepare the WhatsApp bridge or Business API path required by your deployment.
- 2Link or authorize the WhatsApp session and store credentials in the Hermes profile environment.
- 3Run
hermes gateway setupand enable the platform adapter in the active Hermes profile. - 4Restrict allowed users, groups, rooms, or contacts before sending the first real request.
- 5Restart the gateway and send one harmless private test message.
- 6Check gateway logs and confirm the response came from the expected Hermes profile.
- 7Only after the smoke test, add groups, scheduled reports, media handling, or project-specific skills.
What WhatsApp should and should not do
WhatsApp is a front door for Hermes, not a reason to expose every local capability to every chat. The message starts the agent run; Hermes still uses the active profile, enabled tools, skills, and MCP servers behind the scenes. Keep the chat surface narrow and expand only after the first end-to-end test is clean.
- •Use chat for requests, approvals, short status checks, and delivery notifications.
- •Use terminal or a private admin channel for broad filesystem access, deploys, credentials, and irreversible actions.
- •Keep project-specific memories and skills tied to the correct Hermes profile so cross-project context does not leak into the channel.
Safe rollout checklist
The first goal is not a flashy automation. The first goal is proving that the gateway receives the right message, routes it to the right profile, and sends a correct reply without exposing secrets or responding to untrusted users.
- •Configure credentials outside source control.
- •Allowlist one trusted sender or room.
- •Send a harmless test prompt.
- •Check logs for routing, profile, and platform errors.
- •Write down the working setup once repeated use proves it is stable.
Useful workflows after setup
After the gateway is stable, WhatsApp can become the place where humans approve work and receive outputs, while Hermes does the heavier work through other tools. That split keeps the chat simple and the automation useful.
- •Ask for a GitHub PR or Actions failure summary while away from the desk.
- •Approve a draft email, issue, or deployment step after Hermes explains the risk.
- •Receive daily cron summaries or anomaly alerts.
- •Turn a chat thread into a Linear issue, Notion note, or reusable Hermes skill.
Reach your agent from the app you already use
WhatsApp connects Hermes to the messaging app most people open daily, so you and anyone you authorize reach the agent from your phone with no new app to install. It's media-aware and supports group handoffs, which makes it a natural front-end for quick, on-the-go requests.
Mobile access without exposing a dashboard
A messaging channel like WhatsApp lets you control the agent from anywhere without opening a Web UI port to the internet, which keeps the attack surface small. As with every channel, the gateway must stay running — for dependable mobile access when your own machine is off, a managed host keeps the agent reachable around the clock.
Common setup issues
- No reply in WhatsApp — confirm the gateway is running, the platform is enabled, and the sender or room is allowlisted.
- It works in a DM but not a group — check group permissions, mention requirements, and whether the gateway actually received the group update.
- The wrong tools or memories are active — verify the profile that runs the gateway and move project-specific secrets to the right profile.
- Long messages are unreadable — keep chat outputs concise and link to a file, email, Notion page, or GitHub issue for longer reports.
Keep building the workflow
FAQ
Can Hermes run from WhatsApp?
Yes, when the WhatsApp gateway adapter is configured and the Hermes gateway is running under the intended profile.
Should I enable groups immediately?
No. Start with a private or allowlisted test, verify one harmless response, then add group access and free-response behavior deliberately.
Can this channel trigger tools and automation?
Yes, but tool access comes from the active Hermes profile. Keep sensitive tools behind approval or a narrower profile.
What is the safest first prompt?
Ask Hermes to reply with the active profile/platform and no external action. Save file edits, deploys, sends, and purchases for later tests.