Skip to main content

n8n Integration

The n8n integration allows you to connect your Hatz AI workspace to your n8n instance using the Model Context Protocol (MCP). This enables Hatz AI to interact with your n8n workflows and automation tools.

Updated today

Who this is for

This integration is for Hatz AI users who:

  • Have an active n8n instance

  • Want to connect their automation workflows with Hatz AI

  • Have administrative access to both their Hatz workspace and n8n instance

Prerequisites

Before setting up the n8n integration, ensure you have:

  • Access to a Hatz AI workspace

  • An active n8n instance

  • Administrative permissions in your n8n instance to enable MCP access

  • The ability to access Settings in your n8n instance

  • Workflows in n8n that are published and have one of webhook, form, schedule or chat trigger nodes can be enabled for MCP access. Read more

Integration Setup Instructions

Step 1: Access the n8n Integration in Hatz

  1. Navigate to your Hatz workspace

  2. Go to the Integrations tab

  3. Click View All under Available Integrations

  4. Find and select n8n from the list

Step 2: Enable MCP Access in n8n

  1. Log into your n8n instance

  2. Navigate to Settings

  3. Go to Instance Level MCP

  4. Click Enable MCP access

5. Click Connection Details

6. Toggle the view to Access token

7. Copy the following credentials:

  • MCP Server URL (formatted as: https://your-instance.app.n8n.cloud/mcp-server/http)

  • Access Token

Step 3: Complete the Connection in Hatz

  1. Return to the n8n integration page in Hatz

  2. In the Authentication section, enter:

    • MCP Server URL: Paste the server URL from n8n (Settings > Instance-level MCP > Connection details)

    • Access Token: Paste the access token from n8n (Settings > Instance-level MCP > Access token)

  3. Click Connect

Expected Results

Once successfully connected:

  • The integration status will change from "Not connected" to "Connected"

  • Hatz AI will have access to interact with your n8n instance via MCP

  • Your credentials are stored securely within Hatz

Controlling Workflow Access

Important: Hatz can only access workflows that you explicitly enable in your n8n instance-level MCP configuration. By default, no workflows are visible to MCP clients like Hatz.

Workflow Eligibility Requirements

For a workflow to be available to Hatz through MCP, it must meet all of the following criteria:

  • Be published - Only the published version of a workflow is evaluated for MCP access

  • Contain a supported trigger node - The workflow must include at least one of these trigger types:

    • Webhook

    • Schedule

    • Chat

    • Form

Workflows that have a supported trigger added only in a draft version will not be considered eligible until that version is published.

Enabling Workflows for MCP Access

After connecting Hatz to your n8n instance:

  1. In n8n, go to Settings > Instance Level MCP

  2. Review the list of eligible workflows

  3. Explicitly enable access for each workflow you want Hatz to interact with

Only workflows that meet the eligibility criteria and are explicitly enabled will be accessible to Hatz.

Troubleshooting

Connection fails:

  • Verify that MCP access is enabled in your n8n instance

  • Confirm you've copied the complete MCP Server URL and Access Token

  • Check that your n8n instance is accessible and running

  • Ensure you're using the Access Token view (not other credential types) in n8n

Limitations

  • This integration is currently in Beta and functionality may change

  • Requires n8n instance with MCP support enabled

  • Requires administrative access to n8n Settings to generate credentials

  • Connection requires instance-level MCP access

  • The integration connects to a single n8n instance per configuration

  • If your n8n instance URL changes, you'll need to update the connection in Hatz

  • Access tokens must remain valid in n8n for the integration to continue working

Did this answer your question?