free checklist
n8n client handoff checklist.
A good handoff does not explain every node. It gives the client the operating map: what starts the workflow, where data moves, what they can safely edit, and what to check when something stops working.
1. Start with the outcome
- Business result: one sentence explaining what the workflow does for the client.
- Trigger: webhook, schedule, form submission, incoming email, app event, or manual run.
- Inputs: required fields, optional fields, and what happens when fields are missing.
2. Map systems and ownership
- Systems touched: CRM, spreadsheet, email, Slack, payment platform, database, or custom API.
- Credentials: which account owns each connection and who can re-authenticate it.
- Data destination: where records are created, updated, notified, or archived.
3. Name safe edits clearly
- Usually safe: email copy, notification recipients, wait times, labels, and client-facing wording.
- Test first: field names, expressions, credentials, HTTP URLs, branch conditions, and code nodes.
- Never leave this implied. Most support problems start when a client changes one field that feeds five later nodes.
4. Include break-fix checks
- Check the latest execution and identify the first failed node.
- Confirm credentials are still connected.
- Compare a failed input against the documented required fields.
- Run a known-good test record and save the result.
- Record what changed before the failure started.
5. Attach acceptance evidence
- Timestamp of the last successful test.
- Sample input used for the test.
- Expected output and where the client can verify it.
- Known limitations, rate limits, or manual fallback steps.
Generate the handoff automatically
n8n Handoff Kit reads exported workflow JSON and drafts this structure as Markdown: summary, triggers, systems touched, credentials, workflow map, node inventory, safe edits, break-fix checklist, and acceptance checks.