n8n is the self-hosted, open-source alternative to Zapier and Make. If your team is already running n8n on your own infrastructure, connecting it to OpenClaw is a natural pairing — both are self-hosted, both live on your servers, and the integration is more direct than cloud-based alternatives.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like n8n — it's considerably more involved.
Connecting OpenClaw with n8n: Step by Step
Step 1: Create a Webhook Node in n8n
In your n8n instance, create a new workflow and add a Webhook node as the trigger. Set the HTTP method to POST and note the webhook URL (it will be something like https://your-n8n.domain.com/webhook/your-path). Test it with a curl command to confirm it's reachable from your OpenClaw instance — since both are self-hosted, network routing matters.
Step 2: Use the n8n REST API for Workflow Management
n8n has a built-in REST API (enable it in Settings → API) that lets you list workflows, activate/deactivate them, and view execution history. Create an API key in n8n's settings. Use GET /api/v1/workflows to list workflows and GET /api/v1/executions to check recent run history.
Step 3: Build the Proxy and Skill File
Since both OpenClaw and n8n are on the same server (or same network), your "proxy" can be minimal — just a lightweight mapping from clean OpenClaw endpoint names to n8n webhook and API URLs. Write ~/.openclaw/skills/n8n.md with your workflow names, what each does, and whether it's triggerable from OpenClaw.
Challenges and Caveats
Self-Hosted Means Self-Managed
Running n8n yourself means you're responsible for uptime, updates, and security. If your n8n instance is down or a workflow is broken, OpenClaw can trigger it but nothing will happen. Good monitoring of both systems is essential.
n8n API Is Only Available in n8n v0.187+
The n8n REST API for workflow management was added in version 0.187. If you're running an older self-hosted version, you'll need to upgrade before using the management API. Webhook triggers work in all recent versions.
Skip All of This — Use Cody Instead
Cody provides built-in integrations that don't require n8n as a middleware layer. For teams who want managed AI assistance without self-hosting complexity, Cody is the simpler path.
Related Guides
- Connecting OpenClaw with Zapier: A Practical Guide
- Connecting OpenClaw with Make: A Practical Guide
- Connecting OpenClaw with Github: A Practical Guide
Need the model-flexible version? See: How to Connect n8n to OpenClaw: Setup, Models, and Workflow Guide.