agentos.guide › blog

Hermes vs n8n: How To Run Hermes As The Operator And n8n As The Engine In Your Agent OS, With 5 Copy-Paste Prompts

By Julian Goldie · 5 November 2026 · agentos.guide

Hermes vs n8n inside your Agent OS isn't a contest: n8n becomes the workflow engine that moves data between your apps, and Hermes Agent becomes the operator you message, which decides when to call those workflows.

Set it up that way and you stop rebuilding the same process in two places.

This guide gives you a quick start, five prompts to paste into Hermes, and a weekly routine for a small bakery.

If you'd like my team to look over your setup with you, book a free SEO strategy session.

Who does what in the Agent OS

Neither vendor publishes a comparison, so this split is my reading of the Hermes docs and the n8n docs.

Why the two fit together so neatly

n8n is happiest when the path is known: a trigger fires, nodes run in order, and the result lands in a sheet, inbox or app.

Hermes is happiest when the path isn't known yet, because it plans its own steps, remembers context and keeps the skills it learns.

Put Hermes in front and n8n behind, and every request you send in chat can either be answered by the agent or handed to a tested workflow.

The link between them is official on the Hermes side: a catalog entry called n8n-official.

Quick start in five moves

1. Install Hermes with curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash, or use the Desktop installer, then run hermes model.
2. Run hermes gateway setup and connect Telegram or Slack so you can message it from your phone.
3. In n8n, an owner or admin opens Settings > Instance-level MCP, enables access, and copies the Server URL ending in /mcp-server/http.
4. Run hermes mcp install n8n-official, paste that URL, and approve the browser OAuth prompt from n8n.
5. Mark each workflow you want Hermes to use as Available in MCP, then type /reload-mcp in Hermes.

No n8n API key is involved; the Hermes MCP page confirms the entry signs in through the browser.

If you installed the older third-party n8n bridge in the past, it still loads as a custom entry, but it has been retired from the catalog and won't be migrated for you.

🔥 Want the full Agent OS with Hermes and n8n already wired?

The AI Profit Boardroom gives you step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members running these exact stacks.

→ Join the AI Profit Boardroom

Prompt 1: sort your jobs into two lanes

Start by letting Hermes split your task list before you build anything.

Here is a list of the jobs I do every week. For each one, say whether it
belongs in an n8n workflow (same steps every time, app to app) or with you
(needs reading, judgement or a written reply). Give one line of reasoning
per job, then list the three n8n workflows I should build first.

Save the answer as a note, because it becomes the plan for everything below.

Prompt 2: check the n8n connection and lock it down

The catalog entry warns that some n8n tools modify or run workflows, so review them before you rely on them.

List every tool you can see from the n8n-official MCP server. Group them
into read-only, run, and create-or-edit. Tell me which ones to switch off
in hermes mcp configure n8n-official so you can search and run workflows
but cannot change them. Do not run any workflow yet.

Then run hermes mcp configure n8n-official yourself and untick the editing tools.

Prompt 3: run a workflow from chat and explain the result

This is the everyday move: ask in Telegram, let Hermes trigger n8n, get a human answer back.

Search my n8n workflows for "wholesale orders". Show me the match and what
inputs it needs. Once I confirm, run the published version for tomorrow's
date, then summarise the output in five short lines I can read on my phone.

n8n's MCP server guide notes that the run tool uses the published version of a workflow by default, which keeps your drafts out of live work.

Prompt 4: give n8n a door into Hermes

Some events start in n8n and need Hermes to think, so give n8n a webhook route to call.

Create a webhook route called cafe-order using hermes webhook subscribe.
It should take the JSON n8n sends, write a short summary of the order and
any special requests, and deliver it to my Telegram chat. Then tell me the
URL n8n should POST to and which signature headers it must send.

The Hermes webhooks page puts routes at http://your-server:8644/webhooks/<route> and recommends the V2 signature: an HMAC-SHA256 of timestamp plus body, sent with a timestamp header.

Every route needs a secret, and the test-only no-auth setting only works when the gateway listens on localhost.

Prompt 5: a Monday review on a timer

Finish with a scheduled job that pulls from n8n and reports in chat.

Every Monday at 7am, run my n8n workflow "weekly orders sheet", compare it
with last week's summary in your memory, and send me a Telegram message
with the three biggest changes and one question I should ask my team.

Hermes cron accepts plain-language schedules and delivers to any connected platform; my Hermes Agent cron job guide covers the timing options in detail.

Scheduled runs default to blocking dangerous commands, because cron_mode ships set to deny, per the security docs.

The weekly workflow for a small bakery

Here's how a bakery that supplies local cafés would run the pair.

1. Every evening: n8n's Schedule Trigger collects the cafés' order forms into one sheet and posts the sheet link to Hermes's cafe-order route.
2. Straight after: Hermes summarises special requests, flags anything unusual, and messages the head baker on Telegram.
3. During the day: the owner asks Hermes in chat to rerun the orders workflow when a café changes its order, and gets a fresh summary.
4. Monday morning: the Prompt 5 job compares the week with the last one and suggests one question for the team meeting.
5. Customer replies: Hermes drafts answers to café emails, and the owner approves each one before it goes.

n8n never guesses, and Hermes never has to remember where the order sheet lives.

📞 Want my team to map your Hermes and n8n lanes?

Book a free SEO strategy session and we'll go through your weekly jobs and where each one should run.

→ Book a free strategy call

Five mistakes that break the pairing

• Pasting the editor URL. Hermes needs the MCP Server URL ending in /mcp-server/http, not the address of the n8n canvas in your browser.
• Forgetting the per-workflow switch. Enabling MCP on the instance exposes nothing until each workflow is marked available.
• Assuming per-client privacy. n8n says every connected MCP client can see every workflow you've exposed, so expose only what any of them may run.
• Testing on the wrong webhook URL. n8n's Webhook node has a test URL that only listens while you watch, and a production URL that goes live when you publish.
• Scheduling the same job twice. Decide whether n8n's Schedule Trigger or Hermes cron owns each timer, and write it in your lane list from Prompt 1.

When Hermes alone is enough

Not every job needs n8n behind it.

A morning briefing, an inbox summary or a research note is just Hermes reading, thinking and writing, so a cron job with a skill attached covers it.

For script-style checks, Hermes cron even has a no-agent mode that runs a script on a timer and delivers its output with no model call at all.

Bring n8n in when the job has to touch several business apps in a fixed order and leave a clear record of each run.

Licence and hosting notes before you scale

Hermes is MIT-licensed on GitHub.

n8n's community licence page sets out the Sustainable Use Licence, which covers your own internal business, non-commercial or personal use.

If you want to host n8n for clients, read its licence FAQ before you build the offer.

Both tools self-host, and n8n also runs as a managed n8n Cloud account if you'd rather not maintain a server.

Whichever you pick, Hermes has to reach the n8n MCP URL from wherever its backend runs.

The verdict for your Agent OS

Choose n8n for anything you'd happily draw as a flowchart.

Choose Hermes for anything that starts as a message and needs a judgement call.

Run both, joined through n8n-official and a webhook route, and your Agent OS gets a reliable engine and a thoughtful operator at once.

The setups, prompts and coaching for this live inside the AI Profit Boardroom.

FAQ

Which should sit at the front of my Agent OS, Hermes or n8n?

Hermes, because you message it and it decides whether to answer itself or run an n8n workflow through the n8n-official connection.

Can Hermes edit my n8n workflows?

It can if you leave the create and edit tools enabled. Review them with hermes mcp configure n8n-official and switch them off until you trust the setup.

How does n8n send something to Hermes?

With an HTTP POST to a Hermes webhook route on port 8644, signed with the route's HMAC secret, usually from an HTTP Request node at the end of a workflow.

Why does Hermes say it can't find my workflow?

The workflow probably isn't marked Available in MCP, or MCP access isn't enabled on the instance. Fix it in n8n, then run /reload-mcp.

Final word on Hermes vs n8n

Paste Prompt 1 tonight, connect n8n-official tomorrow, and book a free strategy session if you want help running hermes vs n8n as one stack.

Related guides on agentos.guide

→ Grok Bot vs n8n: Give Each A Job In Your Agent OS

→ Hermes vs Cursor: How To Run Both As Two Lanes In Your Agent OS, With 5 Copy-Paste Prompts

→ Hermes Agent Cron Job: Schedule, Stop And Recover Jobs In Your Agent OS With 5 Copy-Paste Prompts

→ Hermes Agent For Business: Start With One Job, Then Grow It With Five Copy-Paste Prompts In Your Agent OS

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide