Thinking about switching platforms and need to convert your n8n workflow to Make? Whether you're seeking better UI, increased reliability, or tighter integration with third-party apps, migrating automation between tools can be a game-changer — if done correctly. In this post, we’ll walk you through a practical, step-by-step process to help you move your automation from n8n to Make (formerly Integromat) without breaking anything.
Why Convert from n8n to Make.com?
Before we get into the "how," let’s explore the "why." While both n8n and Make are powerful automation platforms, they have different strengths:
| Feature | n8n | Make.com |
|---|---|---|
| Hosting Model | Mostly self-hosted (or via partners) | Cloud-based SaaS |
| Learning Curve | Slightly higher (due to higher flexibility) | Beginner-friendly UI |
| Native Integrations | Good, but sometimes requires custom nodes | Extensive and ready-to-use |
| Cost | Free to self-host, usage-based for Cloud | Tier-based pricing |
You might decide to switch if:
- You want a more visual, beginner-friendly environment
- Your team prefers non-self-hosted SaaS tools
- You're hitting scaling or plugin limitations in n8n
If you’re still unsure which tool suits you better, check out n8n vs Make.com: Which One Wins the Workflow Automation War? for a more detailed breakdown.
Understand the Key Differences First
To successfully convert an n8n workflow to Make, it’s crucial to recognize that the two platforms structure automations differently:
n8n Workflow Basics
- Node-based with horizontal flow
- Triggers are often independent of the flow
- Uses JavaScript-friendly expressions like
{{$json["field"]}} - Environment variables & webhooks are flexible but require more configuration
Make.com Scenario Basics
- Vertical flow structure
- Triggers and webhooks are tied directly into the scenario’s start
- Uses different syntax for variable referencing (like
{{1.field_name}}) - Built-in filters and routers offer controlled branching
This means that direct 1:1 copying won’t work—you’ll need to translate logic and expressions.
Step-by-Step: How to Convert Your n8n Workflow to Make
Below is a step-by-step guide to help you convert your n8n workflow to Make without errors:
Step 1: Map Your Current n8n Workflow Structure
Start by analyzing your existing n8n flow:
- Identify your trigger node and its configuration
- List all action/process nodes, their name, position, and logic
- Take note of expressions, conditions, and webhook endpoints
You can do this visually or export the JSON of your workflow and document it in a spreadsheet.
Step 2: Prepare Your New Scenario in Make
- Log in to your Make account (or sign up here to explore Make alternatives if n8n isn’t meeting your needs).
- Create a new Scenario
- Choose the corresponding trigger module (e.g., Webhook, Scheduler, etc.)
- Replicate the trigger conditions from n8n
For example, if your n8n flow starts with a webhook listening for a POST request, set up Make’s Webhook module the same way by copying the webhook path and test payload.
Step 3: Translate Action Nodes Module-by-Module
Every n8n node has a module equivalent in Make, although they may differ slightly in naming or configuration:
- HTTP Request (n8n) → HTTP Module (Make)
- Email (SMTP) → Email (Make)
- Code Node → JavaScript/Function Module (Make or Webhooks Tools)
Adjust your variable/data references!
| n8n Expression | Make Equivalent |
|---|---|
{{$json["name"]}} |
{{1.name}} (if from module 1) |
{{$now}} |
{{now}} |
| Custom JS formatting | Use built-in Make functions |
Make has a function editor with things like formatDate() or sum(). You may need to re-write n8n’s JavaScript logic using Make’s tools.
Step 4: Recreate Filters, Conditions, and Routers
Any IF nodes or branching in n8n should be replicated using:
- Routers in Make to split logic
- Filters between modules to apply conditions (e.g.,
status = 'approved') - Multiple routes to execute different outcomes
This reduces errors by isolating conditions clearly.
Step 5: Handle Webhooks, Tokens, and Auth
In n8n, you might've used OAuth2 via built-in credentials. In Make, you choose or configure connections when adding a module. Double-check:
- Webhook test payloads (use Make’s “Run once” to test values)
- OAuth2 tokens (regenerate if needed)
- API base URLs and authentication headers
Tip: Make's “Hook” testing means delays can occur unless responses are set up exactly right. Use POSTMAN or curl to verify endpoint behavior.
Step 6: Test the Scenario and Debug
Once everything is set:
- Run the scenario in "Run once" mode
- Send a test input through the trigger (webhook, schedule, or data module)
- Watch each module’s output
- Fix broken references, missing fields, or type mismatches (especially date/time)
Don’t forget to activate your scenario once done!
Real-World Use Case: Simple Contact Form Submission
Let’s say you had this flow in n8n:
- Webhook receives contact form
- Format name and email
- Send via SMTP
- Save to Google Sheets
Here’s how it converts to Make:
- Webhooks → Webhooks module
- Data mapping → Text tools (like Split, Replace)
- Email → Gmail or SMTP module
- Google Sheets → Google Sheets (Insert Row)
This 1:1 mapping becomes easier once you're familiar with the Make interface.
Tips to Avoid Common Migration Errors
- Variable mismatch – pay close attention to how dynamic data is referenced
- Authentication issues – remove and re-add API keys or OAuth2 where needed
- Timezone conflicts – don’t rely on
{{$now}}, use Make’snow()and set scenario timezone - Unknown module differences – not all n8n community nodes exist in Make, use alternatives like HTTP or custom apps
You can always use custom nodes in n8n before deciding to migrate if Make lacks that integration.
Final Thoughts
Converting your n8n workflow to Make doesn’t have to be daunting. It’s more about translation than duplication. By understanding the differences in structure, expression logic, and module behavior, you can successfully migrate without data loss or downtime.
Keep in mind that n8n still offers the flexibility of self-hosting and custom logic, so switching back remains an option if needed.
FAQ
How long does it take to convert an n8n workflow to Make?
For simple workflows, 30 minutes to 1 hour is typical. More complex logic with conditions, code, or custom APIs may take several hours.
Can I import my n8n JSON file into Make directly?
No, there is no direct import/export compatibility. You’ll need to rebuild the logic manually in Make.
What happens if Make doesn’t have the same module as n8n?
You can usually replicate the behavior using HTTP requests or Make’s built-in utilities. Alternatively, consider staying with n8n and enhancing flows with community packages.
Is Make more reliable than n8n?
Make offers a managed cloud environment, which can provide greater reliability and uptime, especially for non-technical users. However, n8n gives you full control and is ideal if you prefer to self-host.
Can I go back from Make to n8n later?
Yes, but like this conversion, it will need to be manual. Fortunately, n8n’s flexibility makes it easy to rebuild workflows, especially with templates and backups.
Ready to explore Make? Try building your first scenario here: Explore Make’s automation platform and see how it compares.