Free · local-only · review before client handoff

Which n8n credentials need a second look after handoff?

An exported workflow can describe credential references without proving that the receiving n8n project has usable permissions. Map those references to an anonymous setup checklist—before asking a client to run a real workflow.

First: protect your export

n8n workflow JSON can contain credential names, IDs, or authentication values embedded directly in node parameters. Use a fictional or explicitly authorized and sanitized export. Never upload secrets or customer data. This page reads a selected file in your browser; it sends no workflow to Moruneva, has no account, and stores no result. Inspect your file yourself before sharing it anywhere.

This reviewer only recognizes exported nodes[*].credentials references. It cannot find every inline header, expression, OAuth scope, sub-workflow or dynamic authentication requirement.

Volunteer testers wanted · Open beta through November 29, 2026

We are inviting 3–5 independent n8n builders and consultants to try this free experimental checklist with the four-node fictional example and compare it against their usual free handoff method. A critical or negative assessment is welcome.

Read the 5–10 minute beta steps and give optional feedback →. No account, customer exports, payment, gift or signup form required.

A fair two-method comparison — no client files required

Use the same completely fictional four-node export with your current free approach and this tool. That lets you assess whether the anonymous checklist adds any value before handing over real access.

  1. Download the fictional workflow JSON →. This is an export-shaped test sample, not a verified executable n8n workflow. Its credential identifiers are explicit placeholders; never run it against real accounts.
  2. Use your existing no-cost method first (for example, manually reviewing the exported nodes). Privately note the credential types, affected node positions, unknowns and approximate review time. You do not need to upload the sample to another service.
  3. Then choose that same file under Review one workflow below, select Review locally, and compare the lists. An extra checklist without fewer mistakes or less work is not a demonstrated improvement.

Neutral review questions: Which method missed a credential reference? What still required a human to check in the target project? Was the second method faster? Would this matter in another handoff? You may optionally share your conclusions by email below, without attaching files or identifiable customer information.

Review one workflow

No file loaded. Try the fictional example without using any real credentials.

What to test after the map

In the receiving account, authorize the correct provider and least-privilege scopes, confirm the credential is available to the intended project, run a synthetic two-node smoke test, then verify the expected business-side outcome with the client. Preserve both successful and failed observations.

Next: create a bounded acceptance plan using Moruneva's free acceptance-card builder or read the six-case handoff guide.

Open independent comparison: Use the same fictional four-node sample first with your existing free approach and then with this checker. Read the short, voluntary research steps → or send a five-question comparison by email →. If your free method is better, tell us that. No customer exports or credentials.

Did this help an actual handoff? You can optionally tell us which step still required manual work, and which free method you already tried. No client names, workflow files, credentials or confidential records, please.

Share optional product feedback by email →

Independent free utility; not affiliated with or endorsed by n8n. No current client deployment, security audit, reliability guarantee or paid outcome is claimed.