n8n Migration Metadata Preflight — Preview

Compare workflow dependencies before a migration or handover. This independent tool checks sanitized credential references and node versions against an explicit target inventory. It is not affiliated with n8n.

Preview scope and price

Use synthetic metadata only during this preview. No creator event fee is charged. Apify platform usage is billed to the running user under their plan; this is not a promise of a zero-cost run. Suggested run settings: 128–1024 MB, timeout 60 seconds, maximum run cost $0.02. No live instance connection, automatic remapping or migration is performed.

A paid release is planned at $0.25 per completed report after billing, support and payout checks. That price is a proposal, not an active checkout or a promise that this preview will remain available unchanged.

Try the synthetic example

Paste this in the JSON input editor:

{"nodes":[{"name":"Fetch","type":"example.fetch","typeVersion":1,"credentials":{"exampleApi":{"id":"source-id","name":"service-alias"}}}],"targetCredentials":[{"id":"target-id","name":"service-alias","type":"exampleApi"}],"targetNodeTypes":[{"type":"example.fetch","supportedVersions":[1,2]}]}

The result identifies target-id as a candidate requiring explicit confirmation, not an automatic fix. Change the target ID to source-id to see an exact ID/type match. Add a second same-name/type target credential to see ambiguity. Remove the target type to see node_type_not_listed.

What the report tells you

• Credential ID/type matches, missing references and ambiguous aliases.
• Node types and versions absent from the inventory you supplied.
• Candidate target IDs for your own mapping review.

The default dataset contains one result per source node. The run key-value store OUTPUT contains the full assessment. A successful platform run can still contain a rejected input report: check OUTPUT.status and the dataset, not just the green run badge. The current preview wrapper retains mode=private_validation_no_billing; this is a development label, not a privacy guarantee.

Limits and data

Maximum 100 nodes, 100 target credentials and 100 node types; total input 1 MiB. Every node needs name, type, typeVersion and credentials (use {} if none). Credential references require id and name. Target credentials require id, name and type. Target node types require type and supportedVersions. Unknown fields are rejected, including parameters, pinData and connections.

Do not upload raw workflow exports, execution data, personal information, tokens, passwords or credentials. Names and IDs can themselves contain secrets; a field allowlist cannot detect that. Apify stores run input, output and logs under its storage and retention settings. Do not assume this tool immediately deletes them. Use only invented sample values in the preview.

The tool cannot verify inventory completeness, credentials, authentication, project permissions or runtime compatibility. An unlisted item means absent from your supplied inventory, not necessarily absent from the real instance. It does not alter inputs, apply mappings or contact n8n.

Feedback and support

Use this Actor’s Issues tab for a synthetic reproduction and expected/observed result. Never post secrets or real workflow exports. Operator Labs is operated with AI assistance. There is no guaranteed support response time during the preview. Refund handling for a future paid version is still being verified; no paid report orders are accepted now.

Validation

16 local tests pass. Two private cloud tests verified an expected candidate result and rejection of an extra parameters field. These are development tests, not customer sales or evidence of production compatibility.