Integration
Hermes Agent Email Integration: IMAP/SMTP Setup and Safe Agent Inbox
Set up Hermes Agent as an email-based assistant using the Email gateway, IMAP, SMTP, allowed senders, and safe reply-in-thread workflows.
Quick answer
Hermes can receive and reply to email through the Email gateway. Use a dedicated inbox, IMAP/SMTP credentials, app passwords for providers like Gmail, and allowed-sender rules so the agent only responds to people you trust.
Managed cloud · API costs included · No gateway maintenance
Best for
Operators who want a practical agent workflow, not only a chat demo.
Teams that need a clear setup path, smoke test, and permission boundary.
Workflows that should connect Hermes to other tools such as GitHub, Linear, Notion, Telegram, Slack, or email.
Self-hosted users who need to understand what runs locally and what credentials are required.
Features
- ✓Email gateway adapter using standard IMAP and SMTP
- ✓Reply-in-thread behavior from a dedicated agent mailbox
- ✓Gmail, Outlook, Fastmail, Yahoo, or any IMAP/SMTP provider
- ✓Allowed-sender controls so random inbound email does not trigger the agent
- ✓Separate from the Himalaya email skill, which is for mailbox management through terminal tools
- ✓Works with cron reports, support triage, and inbox-to-ticket workflows
Setup path
- 1Create a dedicated email account for Hermes instead of using a personal inbox.
- 2Enable IMAP and create an app password if your provider uses 2FA.
- 3Run
hermes gateway setupand choose Email, or add the IMAP/SMTP values to the Hermes environment. - 4Configure allowed senders before turning on automatic replies.
- 5Send one test email from an allowed account and confirm Hermes replies in the same thread.
- 6Only after the smoke test, connect email summaries to Linear, GitHub, Notion, or Telegram workflows.
Gateway email vs mailbox management
The Email gateway is for receiving messages sent to the agent and replying through SMTP. It is not the same as giving the agent full control over your personal mailbox. If you want Hermes to search, move, or compose messages from a mailbox, use a dedicated email skill and command-line mail client setup instead.
- •Gateway path: people email Hermes and get replies.
- •Mailbox-management path: Hermes uses a configured mail CLI to inspect and organize messages.
- •Keep the two paths separate so the public-facing agent inbox does not accidentally inherit personal-mail permissions.
Good email workflows
Email is slower than chat but useful for long-form handoffs and external users who will not join your Telegram, Discord, or Slack. The best workflows turn inbound email into structured action, not endless back-and-forth.
- •Turn customer bug reports into Linear or GitHub issues with reproduction steps.
- •Send daily or weekly reports from cron jobs to an email alias.
- •Use email for vendors, clients, or partners who need a normal inbox rather than a bot UI.
Common setup issues
- The integration appears enabled but nothing happens — restart the Hermes gateway or start a fresh Hermes session after config changes.
- Credentials work in one shell but not in the gateway — check the active Hermes profile and where the gateway process reads its environment.
- The workflow is too broad — split it into smaller routes, skills, or prompts with one expected outcome each.
Keep building the workflow
FAQ
Should Hermes use my personal email account?
No. Use a dedicated account so allowed senders, app passwords, logs, and automated replies are isolated from your private inbox.
Does Email require an external service?
No. The gateway path uses standard IMAP and SMTP. You only need an email provider account and the right host, port, username, and app-password settings.
Can Hermes reply to anyone who emails it?
It can, but you should not launch that way. Restrict allowed senders first, then expand only when you know the agent behavior is safe.