All modules
Module 23 · ship · advanced
Zapier/Make to n8n Migration Kit
After this module you can turn a client's Make scenarios or Zapier zaps into draft n8n workflows in seconds, with an honest report of what's ready, what needs a check, what must be rebuilt, and what they'll save.
What it does
| Entry | What happens |
|---|---|
POST /webhook/mig/convert |
Send a Make blueprint (blueprint, or blueprints: [...]) or a Zapier export (zapfile, or one zap). Each scenario/zap becomes an importable n8n workflow: nodes from the mapping table, {{1.email}} / {{123__email}} rewritten to n8n expressions, filters → If, routers/paths → Switch (all matching outputs), unknown apps → placeholder nodes with the original settings in their notes. The report lists every step as mapped / partial / manual, credentials to create, effort hours, the current platform's monthly cost estimate, and a parallel-run checklist (also as Markdown) |
GET /webhook/mig/mappings |
The mapping table: apps, their trigger/action nodes, aliases |
Options: monthly_runs (a number, or per scenario name), create: true (create the workflows through the n8n API, inactive), dry_run. Sample exports are in samples/.
Flow
Convert API ──┐
Mappings API ─┴→ Settings (mapping table, rates) → Route ─convert→ Read Export → Convert to n8n → Build Report → Valid Export?
│ → Create in n8n? ─yes→ Workflows to Create → Create Workflow (n8n API) → Record Created → respond
│ └no→ respond report (invalid → 400)
└mappings→ List Mappings → respond
Verification status (n8n 2.43.6)
- 31 behavior checks (41 assertions) without credentials: Make and Zapier samples convert with the expected statuses, credentials and node types; expression rewriting (incl. webhook
.bodyand Zapier nested__fields); filters → If; router and paths → Switch with wired outputs; unmapped app and untranslatable function flagged; billing units and cost/effort estimates; Markdown report; stable ids; no-trigger and AND/OR edge cases; bad input → 400; all 4 generated workflows import into n8n; create failure reported. - Not verified: creating through the n8n API with a real credential (
WITH_CREDS=1), and real exports from client accounts. The Zapier export format isn't documented publicly; the samples follow the zapfile shape (zaps[].nodes{}withselected_api,action,params,parent_id). Generated workflows still need credentials and field checks before they run; that's what the report is for.
Files
| File | Tier | Purpose |
|---|---|---|
| lesson.md | Free | How the converter works, running a migration |
| workflow/starter.json | Free | Triggers, mapping table, export reader |
| workflow/learner.json | Learner | Finished workflow |
| workflow/code/ | Learner | Readable copies of the Code nodes |
| samples/ | Learner | Sample Make blueprint and Zapier export |
| exercises.md | Learner | Practice tasks |
| solutions.md | Learner | Exercise solutions |
| notes.md | Private | Learning log |
| sell/ | Private | Offer, video script, blog post |