Skip to main content
Glama
kotiniiqq

migrate-to-n8n

by kotiniiqq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Convert a Make scenario to n8n

convert_make

Converts a Make (Integromat) scenario blueprint into an n8n workflow file, writing the workflow plus a per-step report to a local output folder so you can import and finish the migration.

Instructions

Convert one Make (Integromat) scenario blueprint (the .json from Export Blueprint) into an n8n workflow. Runs locally; nothing is sent anywhere. Writes .n8n.json (import it in n8n), plus the report as Markdown and JSON, to outputDir. Returns the report: totals (converted / to review / manual), every step with its n8n node and status, a concrete suggestion for each step to finish by hand, the credentials and webhook URLs to set up, and the paths of the files. For Zapier exports use convert_zapier instead. Afterwards, upload_to_n8n (when configured) creates the workflow in n8n, and check_n8n_workflow re-checks a file after manual edits.

Input Schema

NameRequiredDescriptionDefault
jsonNoThe full contents of the exported file, when the user pasted or attached it instead of giving a path. Give either path or json, not both.
pathNoAbsolute path of the exported file on this computer (~ is the home folder). Give either path or json, not both.
outputDirNoFolder to write the results to; created if missing; existing files are kept and the new ones get " (2)", " (3)"… in their name. Default: Documents/migrate-to-n8n in the home folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / json / description
      Previous value: -"The exported file contents, when the user pasted or attached it"New value: +"The full contents of the exported file, when the user pasted or attached it instead of giving a path. Give either path or json, not both."
    • changedInput schema / properties / outputDir / description
      Previous value: -"Folder for the results (default: Documents/migrate-to-n8n)"New value: +"Folder to write the results to; created if missing; existing files are kept and the new ones get \" (2)\", \" (3)\"… in their name. Default: Documents/migrate-to-n8n in the home folder."
    • changedInput schema / properties / path / description
      Previous value: -"Path to the exported file on this computer"New value: +"Absolute path of the exported file on this computer (~ is the home folder). Give either path or json, not both."
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial context beyond the annotations: it runs locally with nothing sent anywhere (reinforcing openWorldHint=false), writes <scenario name>.n8n.json plus Markdown and JSON report files to outputDir, and enumerates what the returned report contains. This is a file-writing tool with no output schema, and the description discloses the side effects and payload shape itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six short sentences, front-loaded with purpose, then side effects, then return value, then alternatives and follow-ups. Nothing is repeated from the schema and every sentence carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no required parameters, the description compensates fully by describing the produced files, their location, and the report's contents (totals, per-step status, suggestions, credentials, webhook URLs, paths). It also points to the follow-up tools an agent needs after conversion.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains path vs json mutual exclusivity and the outputDir default and collision behavior. The description only references outputDir in passing and adds no syntax or format detail beyond it — baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — convert a Make (Integromat) scenario blueprint exported as .json into an n8n workflow — and explicitly names the sibling it is not (convert_zapier) for the adjacent input format. An agent can distinguish it from every sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the exact input provenance ('the .json from Export Blueprint'), routes Zapier exports to convert_zapier, and describes the downstream sequence (upload_to_n8n after conversion, check_n8n_workflow after manual edits). Both when-to-use and when-not-to-use are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools