How to Connect 
Make + 
n8n: Step-by-Step Integration & Automation Guide (2026)
A complete blueprint for automating workflows between Make and n8n using native connectors, Webhooks, or Zapier/Make.
- Connection
- Middleware
- Webhook / API
- Setup time
- Varies
- Difficulty
- Medium
When & why to run Make with n8n
Visual cloud automation vs. self-hostable and code-first.
Make and n8n both offer powerful, visual multi-step automation, but Make is a polished hosted SaaS while n8n is source-available and self-hostable with real code steps. Choose Make for a slick visual builder and broad app coverage without infrastructure; choose n8n to self-host, write JavaScript/Python, and control your data and AI workflows.
Automation Blueprints — make them work together
The real payoff is the stack. These are concrete Make ↔ n8n workflows worth building.
Hand off from Make to n8n
Scenario Complete
Needs custom code
Webhook Node
Combine Make's app coverage with n8n's custom code steps.
Hand off from n8n to Make
Workflow Complete
Needs a Make-only app
Custom Webhook
Hand off to Make when you need an app n8n doesn't natively support.
Setup steps
The Zapier/Make path, start to finish.
- 1
Create a Zapier or Make account and connect both Make and n8n (authorize each via OAuth).
- 2
Create a new Zap/Scenario with the trigger — Make: Scenario Complete.
- 3
Add a filter for the condition (Needs custom code) so the workflow only fires when it should.
- 4
Add the action in n8n (Webhook Node) and map the fields from the trigger data.
- 5
Test with a live record, verify the result, then turn the automation on and repeat for the other workflows.
Edge cases & rate limits
What breaks in production — plan for these before you scale.
- Field mapping: Make and n8n fields rarely map 1:1 — normalize dates, currencies, and dropdown/picklist values explicitly.
- Pick a source of truth per field to avoid two-way syncs overwriting each other in a loop.
- Make: The powerful visual builder has a steeper learning curve than Zapier for beginners.
- n8n: Cloud plans meter by workflow executions — exceeding limits pauses workflows or forces a costly upgrade.
- Watch API rate limits on bulk backfills — throttle or batch to stay under each tool's per-second/per-minute caps.