Make (formerly Integromat) is a visual automation platform used for complex multi-step workflows. Connecting OpenClaw to Make works similarly to Zapier — primarily through webhook triggers — but Make's API also provides deeper visibility into scenario execution history.
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 Make — it's considerably more involved.
Connecting OpenClaw with Make: Step by Step
Step 1: Create a Webhook in a Make Scenario
In Make, add a Webhooks module as the trigger for a new scenario. Copy the webhook URL. In your OpenClaw skill file, document this URL and the expected payload structure. When Claude triggers the webhook, Make's scenario executes the subsequent modules.
Step 2: Use the Make API for Scenario Management
Make's Management API (https://eu1.make.com/api/v2/ or us1.make.com depending on your region) lets you list scenarios, activate/deactivate them, and view execution history. Authentication uses an API token from your Make profile settings. Add these endpoints to your proxy for monitoring queries.
Step 3: Build the Proxy and Skill File
Wrap the webhook trigger URLs and the Management API in your proxy. Write ~/.openclaw/skills/make.md with your scenario names and what they do, the webhook URLs for triggerable scenarios, and what execution data is available from the API.
Challenges and Caveats
API Region Varies
Make has separate API servers for EU and US regions (eu1.make.com vs us1.make.com). Using the wrong region returns authentication errors. Check your Make workspace URL to determine which region you're on.
Webhook Execution Is Asynchronous
Like Zapier, Make scenarios triggered by webhook run asynchronously. OpenClaw can confirm the trigger but can't wait for scenario completion. For feedback on results, design your scenario to POST a callback to OpenClaw's endpoint (if you have one exposed).
Skip All of This — Use Cody Instead
Cody connects natively to your tools without requiring Make as middleware. Get direct integrations without building scenario workflows.
Related Guides
- Connecting OpenClaw with Zapier: A Practical Guide
- Connecting OpenClaw with N8n: A Practical Guide
- Connecting OpenClaw with Hubspot: A Practical Guide
Need the model-flexible version? See: How to Connect Make to OpenClaw: Setup, Models, and Workflow Guide.