Make → n8n
Move your Make scenarios to n8n
Drop your scenario blueprints and see which scenarios convert to n8n automatically, what needs a check and how long the move takes. The report runs in your browser and is free. Routers, filters, iterators, aggregators, HTTP, JSON, data stores and Make formulas convert by rule, and converted workflows are validated before you download them.
Add your Make blueprints
Drag and drop it anywhere in this box, or choose it from your computer.
One blueprint.json per scenario, from Export blueprint in the scenario editor. Drop several files, or a ZIP or folder with them.
Have a folder of blueprints?
See a full report on four demo scenarios and convert one of them. Free, no signup.
Everything runs in your browser. The blueprints are not uploaded to generate the report.
How to get your scenarios out of Make
- Open a scenario in Make's editor.
- Click ⋯ (More) in the toolbar at the bottom and choose Export Blueprint. Make downloads a
<scenario name>.blueprint.jsonfile. - Repeat for each scenario, then drop all the files above at once.
- Create an API token in your Make profile (API access) with the
scenarios:readscope. - List your scenarios with
GET /api/v2/scenarios?teamId=…and save eachGET /api/v2/scenarios/{id}/blueprintresponse as a JSON file. - Drop the files above: API responses work as they are.
- Connections: reconnect each app as an n8n credential.
- Webhook URLs: point every sender at the new n8n webhook URL.
- Data store records, keys and the scenario schedule: copy or set them again.
- 01 Your report appears on this page. It's free and your blueprints aren't uploaded.
- 02 Convert one workflow free, or pay once to convert them all.
- 03 Download a ZIP with n8n workflow files and a checklist. In n8n, open the workflow menu and choose Import from File, or use the included bulk import script.
What becomes what
| Make | n8n | Notes |
|---|---|---|
| Webhooks (custom webhook) | Webhook | The URL changes; point senders at the n8n URL. |
| Webhook response | Respond to Webhook | Same status, headers and body. |
| Scenario schedule | Schedule Trigger | Kept from Make API exports. Export Blueprint files leave it out: set it once in n8n. |
| Filter | If | Same operators: text (with or without case), numbers, dates, arrays, exists, AND/OR groups. |
| Router | If per route | Every route whose filter passes runs, in order, as in Make. |
| Iterator | Loop Over Items | The modules up to the aggregator run once per item. |
| Array aggregator, Text aggregator, Aggregate to JSON | Code | Collects the loop's items into one array or text. |
| Set variable(s), Compose a string, Switch | Edit Fields | Same names and values as n8n expressions. |
| Parse JSON, Create JSON | Code, Edit Fields | One line each. |
| HTTP: Make a request | HTTP Request | Same method, URL, headers, query string and body. |
| Data store | Code + static data | Records live in the workflow's own storage. |
| Sleep | Wait | Same delay. |
| Code module (JavaScript) | Code | input and the returned result keep working. |
| Code module (Python) | Code | Ported to JavaScript by the AI rewrite: n8n Cloud's Python can't import modules. |
| Formulas: formatDate, parseDate, if, ifempty, get, map, … | n8n expressions | Translated to JavaScript and Luxon, with Make's 1-based array indexes. |
| Other apps | The app's n8n node | Added with your Make settings in its notes; the AI rewrite fills it in. |
Error handlers (Resume, Ignore, Break, Rollback) have no one-to-one n8n twin: the report lists them, and you set the node's On Error option or an error workflow. Calls to Make's own API and subscenarios are flagged too.
Why teams move scenarios to n8n
- n8n Cloud bills one execution per workflow run, however many steps it has. Make uses up credits for each module that runs, for every bundle.
- Self-host n8n for free (Community Edition) and keep the data on your own server.
- Code runs in a regular Code node, branches can rejoin, and AI agents and LangChain nodes are built in.
How it works
- Export the blueprint of each scenario and drop the files above.
- Read the free report: each scenario gets a traffic light, an effort estimate and the accounts to reconnect.
- Convert one scenario free, or all of them with a one-time plan (pricing). Import the files into n8n, connect your accounts and test.
Questions
Can n8n import Make scenarios directly?
No. n8n imports only its own workflow JSON and has no Make importer. This tool turns Make's scenario blueprints into n8n workflow files that you import with Import from File or through the n8n API.
How do I export my scenarios from Make?
Open a scenario, click the More (⋯) button in the editor's bottom toolbar and choose Export Blueprint. Make downloads a <scenario name>.blueprint.json file, one scenario at a time. On paid plans the Make API returns the same blueprint for many scenarios (GET /api/v2/scenarios/{id}/blueprint), and its responses also carry the schedule.
Do routers behave the same in n8n?
Yes. Make runs a router's routes one after another, and each route runs when its filter passes. The converter gives each route its own If node in the same order, and joins them after the router.
What about my connections, webhooks and data stores?
Blueprints don't carry connections, so you connect each app once as an n8n credential. Webhook URLs change: point every sender at the new n8n URL. Data store records are not in the blueprint either: copy the ones you still need. Secrets typed straight into fields are listed in the report so you can move them to credentials.
Is my export uploaded?
Not for the report: it is built in your browser. Converting sends the scenario definitions to our server, which processes them in memory and keeps nothing.
How much does it cost?
The report is free, and so is converting one workflow. Converting them all is a one-time payment: Starter $49 for up to 25 workflows, Team $149 for up to 100 workflows, Agency $399 for up to 500 workflows.
Moving from Zapier too? See the Zapier to n8n converter. Leaving Pipedream? Pipedream Workflows shut down on March 31, 2027: see the Pipedream to n8n guide.