n8n Handoff Pack — Help Center

Getting started

1. Open the app. No sign-up, no install. Go to n8n-handoff-pack.pages.dev.
2. Load a workflow. Click Choose an n8n workflow export (.json) and pick the JSON file you exported from n8n (Workflow menu → Download). Or click Try a sample workflow to see the tool in action without a file of your own.
3. Read the result. You get three blocks, in seconds, entirely in your browser:
   • Dependency inventory — credentials to create, community nodes to install, sub-workflows referenced, environment/instance variables, and webhooks to reconfigure.
   • Handoff risks — a deterministic scan for likely secrets in plain text, hardcoded environment values, and things that need to change before the client gets the file.
   • Delivery pack preview — the Markdown checklist you're about to export.
4. Export. Click Export Markdown to download a single .md file (Lite), or, with Pro and more than one file loaded, Export ZIP to get a .md per workflow plus a combined index.md.
5. Fill in the blanks by hand. The exported checklist has empty cells for real values (credential owners, actual variable values, sign-off names). The tool never invents or stores those — you or your client fill them in outside the app.

That's the whole flow. There's nothing to configure, connect, or install first.

What each section of the delivery pack means

• Credentials to create — every credential type your client needs to set up in their own n8n instance, grouped by type and showing which node(s) use it. The tool only ever sees credential references (id/name) — n8n's export format never includes the credential's actual secret value.
• Community nodes to install — any node whose type isn't one of n8n's core namespaces. Your client needs to install these packages before importing the workflow, or it will fail to load.
• Sub-workflows required — workflows referenced via an "Execute Workflow" node. These live in separate files and need to be exported and delivered alongside the main workflow.
• Environment & instance variables — every $vars.* and $env.* reference found in node parameters, deduplicated, with the nodes that use each one. Your client needs to set these in their own instance.
• Webhooks to reconfigure — any webhook or trigger node, with its path if set. The production URL is unique per n8n instance, so this always needs to be regenerated or confirmed in the client's environment.
• Handoff risks found — findings from the deterministic scan: likely tokens, hardcoded URLs pointing at your machine or staging environment, literal resource IDs, custom webhook paths, or embedded emails. Each finding shows a masked snippet (never the full value), the rule that caught it, and a suggested action.
• Smoke test checklist — steps to verify the workflow after import, generated from the trigger type(s) it uses, plus blank checkboxes for anything specific to that workflow.

Lite vs. Pro

Lite is not a trial — it's a genuinely useful free tool. Pro is for people handing off more than one workflow at a time or who want the complete risk scan and a polished, batch-ready delivery pack.

FAQ

Can it auto-deploy the workflow or connect to my n8n instance?

No, and this won't change. n8n Handoff Pack never connects to any n8n instance and never touches real credentials. It only reads a JSON file you already exported, in your browser. This is a deliberate, permanent scope decision — not something on a roadmap.

What happens to my data? Does anything leave my browser?

No. The workflow file is read and analyzed entirely client-side. The one network call this tool ever makes is verifying a Pro license key with Gumroad, which sends only the license key, never your workflow's contents.

How do I activate Pro?

Buy the license on Gumroad, then paste the license key into the "Gumroad license key" field in the app and click Unlock Pro. It's verified once against Gumroad and then stored in your browser's localStorage.

My n8n export isn't recognized.

The tool requires a valid JSON object with nodes (array) and connections (object) — the minimum n8n always includes. If your file has those and still isn't recognized, it may be an export shape from a newer n8n version we haven't seen yet. Email us a sample export with any real values replaced by dummy ones and we'll add support for it.

How do I uninstall, and what happens to my data?

There's nothing to uninstall — it's a web page, not an app with permissions. The only thing ever stored is your Pro license key in localStorage. Clearing your browser data removes it. Nothing about the content of any workflow you've analyzed is ever stored.

Does the risk scan look at my credentials?

No — n8n's export format never puts a credential's actual value in the JSON, only a reference (id/name). The risk scan looks at parameters and notes on each node, where hardcoded secrets and environment details sometimes end up by accident.

Will it modify or "fix" my original workflow file?

No. The tool only reads the file you give it and produces a separate Markdown (or ZIP) report. Your original JSON is untouched.

Is the risk scan exhaustive?

No. The R1–R6 rules are deterministic pattern matches — fast, private, and reliable for common cases, but not a substitute for your own read-through of the workflow before handoff.

Does it work offline?

Yes, fully, except for the one-time Pro license check, which needs a connection to reach Gumroad.

Can I analyze workflows for more than one client at once?

Lite analyzes one file at a time. Pro adds batch mode — load several JSON files and get one combined delivery pack.

Do I need a Gumroad account to buy or use Pro?

No account needed to use the tool. Gumroad handles the purchase and emails you the license key.

Troubleshooting

• "This does not look like an n8n workflow export." Your file is missing nodes or connections at the top level, or isn't valid JSON. Make sure you exported the whole workflow from n8n (Workflow menu → Download), not a partial copy-paste.
• No credentials or risks show up on a workflow I know has secrets in it. The scan only reads parameters and notes — n8n's export never includes real credential values, so those are never at risk of leaking via this tool. If a secret is hardcoded somewhere the scan doesn't cover, or doesn't match rules R1–R6, it won't be flagged. Always do a final manual read of sensitive workflows before handoff.
• My Pro license key won't activate. Check your internet connection — the key is verified against Gumroad on first use. Then check the key was copied in full, with no extra spaces or a missing character at the start/end.
• I can't select more than one file. Multi-file upload is a Pro feature. In Lite, the file picker takes one file at a time.
• My exported checklist has empty cells. That's intentional — the tool never has access to real values (credential owners, variable contents, sign-off names) and won't invent them. Fill them in by hand or hand the file to your client to complete.