Handover is complete when the client can own, operate, stop, recover, update, and remove the system without the original builder. A workflow export alone is not a handover.
Deliver the Operations Packet
Include:
- architecture/data-flow and systems of record;
- workflow/sub-workflow inventory and versions;
- trigger schedule/webhook/provider references;
- credential names, owners, scopes, rotation—never secret values in documents;
- normal states, error classes, dashboards, alerts, and service targets;
- daily/weekly/monthly operator tasks;
- backup/restore/update/rollback runbooks;
- consent, retention, deletion, and incident paths;
- dependency/license/cost inventory;
- vendor/builder access removal and emergency contacts.
Use screenshots sparingly and pair them with searchable steps. Version the packet with the released workflow.
Train by Scenario
Ask the client operator to perform, while you observe:
- find a failed execution and explain its safe fields;
- pause a workflow;
- reprocess an idempotent test event;
- rotate a sandbox credential;
- restore in staging;
- roll back a version;
- opt out/delete a synthetic contact;
- remove builder access.
Record competency gaps and retest. Do not retain administrator access “just in case” without a support contract and authorized identity.
Worked Example
A Rawalpindi clinic’s low-risk appointment-reminder workflow is handed to two authorized operators. Training uses synthetic patients. Operators can pause reminders, inspect safe errors, update service hours, rotate the messaging test token, and trigger the incident path.
The clinic owns hosting, domain, database, provider apps, billing, backups, and recovery email. The agency’s access is reduced to a named support role, then removed at stabilization end. Health-data handling receives appropriate professional/legal review outside the automation tutorial.
Failure Cases to Diagnose
- Only one client employee trained: add alternate owner.
- Secrets pasted into PDF: use credential inventory and secure entry.
- Runbook assumes builder memory: clean-room test.
- No stop button: document safe pause/cancel.
- Exports lack dependencies/config: include full inventory.
- Freelancer remains account owner: transfer before acceptance.
🇵🇰 Pakistan Angle
Provide plain English and, where useful and accurately maintained, Roman Urdu operator notes. Keep technical identifiers unchanged so support can match them. Show PKT hours and escalation.
Connectivity should not prevent emergency pause. Arrange an alternate authorized operator and provider-level revocation route. Never send production passwords or OTPs through WhatsApp during handover.
Hands-On Exercise
- Build the packet.
- run scenario training with a second person.
- perform restore/rollback/rotation.
- remove builder access.
- obtain signed acceptance with open risks.
Completion Rubric
- Client owns all production systems/recovery.
- Packet covers architecture through removal.
- Two operators can run scenarios.
- Secrets are handed over securely.
- Restore/rollback/pause are demonstrated.
- Builder access and open risks are explicit.
Sources
- n8n Docs — Workflow export/import
- n8n Docs — User management and access
- n8n Docs — Hosting configuration and database settings
Key takeaway: handover succeeds when client-owned people and accounts can operate, recover, and remove the system using tested documentation, without secret dependence on the builder.