Hermes Agent + n8n Integration: Workflows, Webhooks, and Agent Handoffs

This guide covers how to connect Hermes Agent with n8n for workflow automation, covering webhook-based triggers, agent-to-n8n handoffs, and the n8n MCP catalog path. It is for operators and teams who want a practical agent workflow that combines deterministic automation steps with LLM reasoning, not just a chat demo.

What You Need

Before you start, ensure you have the following:

• A running Hermes Agent instance (self-hosted or managed cloud). The official documentation notes that self-hosted users need to understand what runs locally and what credentials are required.
• An n8n instance (self-hosted or n8n.cloud) with access to create workflows and webhooks.
• For the MCP catalog path, the n8n MCP entry must be installed and configured in Hermes. This is an optional path for managing or inspecting n8n workflows where available.
• A secret token for protecting Hermes webhook routes (recommended).
• Basic familiarity with HTTP Request nodes in n8n and webhook concepts.

Understanding the Integration: n8n vs. Hermes

The core design principle of this integration is a clear boundary between deterministic workflow steps and reasoning-heavy agent steps. According to the official documentation, n8n is excellent for predictable integrations: receive a webhook, transform fields, call an API, update a sheet, send a notification. Hermes is useful when the next step depends on interpretation: summarize the customer request, decide severity, write code, research context, or draft a reply.

Use n8n for deterministic routing and retries. Use Hermes for ambiguous tasks that require context and judgment. Keep payloads small and explicit so the agent is not guessing what the workflow meant.

What Belongs in n8n

• Receiving webhooks from external services (e.g., support forms, GitHub events)
• Field validation and data transformation
• Calling external APIs for CRUD operations
• Updating spreadsheets or databases
• Sending notifications via email, Slack, Telegram, etc.
• Orchestrating multi-step deterministic processes

What Belongs in Hermes

• Summarizing customer requests or support tickets
• Deciding severity or priority based on context
• Writing code or debugging
• Researching documentation or repository context
• Drafting replies or generating reports
• Using tools like GitHub, Linear, Notion, Telegram, Slack, or email

Setup Path: Three Integration Directions

The official documentation outlines three possible directions for the integration. You can choose one or combine them based on your workflow needs.

Direction 1: n8n Triggers Hermes (Webhook Route)

This is the most common pattern. n8n acts as the automation backbone, and when it encounters a step that requires reasoning or judgment, it sends a payload to a Hermes webhook route.

Steps:

1. Enable Hermes webhooks in your Hermes Agent configuration. The exact method depends on your setup (self-hosted or managed cloud).
2. Create a dedicated webhook route in Hermes for the specific workflow. This route will receive the payload from n8n.
3. Protect the route with a secret token. This ensures only authorized n8n workflows can trigger the agent.
4. In n8n, add an HTTP Request node that POSTs the event payload to the Hermes webhook route URL. Include the secret token in the request headers (e.g., Authorization: Bearer your-secret).
5. Test with a small payload before sending production data. This helps verify the route is working and the agent processes the input correctly.

Example n8n HTTP Request Node Configuration:

{
  "method": "POST",
  "url": "https://your-hermes-instance.com/webhooks/n8n-support-triage",
  "authentication": "genericCredentialType",
  "genericAuthType": "httpHeaderAuth",
  "sendHeaders": true,
  "headerParameters": {
    "parameters": [
      {
        "name": "Authorization",
        "value": "Bearer your-secret-token"
      }
    ]
  },
  "sendBody": true,
  "bodyParameters": {
    "parameters": [
      {
        "name": "ticket_id",
        "value": "={{ $json.ticket_id }}"
      },
      {
        "name": "customer_message",
        "value": "={{ $json.customer_message }}"
      },
      {
        "name": "priority",
        "value": "={{ $json.priority }}"
      }
    ]
  },
  "options": {}
}

Explanation:

• The url points to your Hermes webhook route. Replace with your actual instance URL.
• The Authorization header uses a bearer token. This is the secret you defined when creating the route.
• The body includes specific fields from the n8n workflow (ticket_id, customer_message, priority). Keep the payload small and explicit so the agent is not guessing what the workflow meant.

Direction 2: Hermes Calls n8n (Agent-to-n8n Handoff)

In this direction, Hermes initiates an action that requires n8n to execute a deterministic workflow. For example, after Hermes analyzes a support ticket, it might ask n8n to update a CRM record or send a notification.

Steps:

1. In n8n, create a webhook workflow that listens for incoming requests. The webhook URL will be the endpoint Hermes calls.
2. Document the payload shape that n8n expects. This is critical because Hermes needs to send the correct fields.
3. In Hermes, create a skill that describes the n8n webhook URL and the expected payload format. The skill acts as a tool that the agent can invoke.
4. When the agent decides to use this skill, it sends an HTTP request to the n8n webhook URL with the appropriate payload.

Example Hermes Skill Definition (Conceptual):

name: update_crm_record
description: Updates a CRM record via n8n workflow. Use when you need to change a customer's status or add notes.
parameters:
  type: object
  properties:
    customer_id:
      type: string
      description: The unique ID of the customer in the CRM.
    status:
      type: string
      enum: [active, inactive, lead, churned]
      description: The new status for the customer.
    notes:
      type: string
      description: Additional notes to append to the customer record.
  required: [customer_id, status]
url: https://your-n8n-instance.com/webhook/update-crm
method: POST
headers:
  Content-Type: application/json

Explanation:

• The skill defines the parameters Hermes must collect from the user or context before calling n8n.
• The url is the n8n webhook endpoint. Ensure this is accessible from your Hermes instance.
• The method is POST, and the headers specify JSON content type.
• The agent will automatically fill the parameters based on the conversation or task.

Direction 3: Using the n8n MCP Catalog Path

If you have the n8n MCP entry installed and configured in Hermes, you can use it for managing or inspecting n8n workflows directly. This is an alternative to webhooks for certain use cases.

Steps:

1. Install the n8n MCP entry in your Hermes Agent. The exact installation method depends on your Hermes setup (e.g., via the MCP catalog or manual configuration).
2. Configure the MCP entry with the necessary credentials (e.g., n8n API key, instance URL).
3. Select only the tools you need. The official documentation advises against exposing all n8n capabilities to the agent; instead, choose specific actions like listing workflows, getting workflow status, or triggering a workflow.
4. The agent can then use these tools to inspect or control n8n workflows as part of a larger task.

When to use MCP vs. Webhooks:

According to the FAQ in the official documentation, use webhooks for event triggers (e.g., n8n triggers Hermes when a form is submitted). Use MCP when you want Hermes to inspect or operate n8n itself (e.g., check if a workflow is running, or start a workflow from a Hermes decision).