The capstone deploys one authorized, low-risk workflow with complete evidence. “Complete” includes business states, data contracts, permissions, consent, idempotency, failures, monitoring, backup, rollback, licensing, cost, and client handover.
Choose the Scope
Use a task such as form → CRM DRAFT → human queue, approved content → review → CMS DRAFT, or daily exception report. Avoid first projects that autonomously move money, submit legal/tax filings, make employment/health/credit decisions, or message unconsenting people.
Define owner, baseline, goal, systems of record, allowed/excluded actions, event volume, data class, success/safety/reliability/cost targets, and pilot limit.
Build the Release Packet
- architecture and state machine;
- normalized event/data schemas;
- client-owned identities and least scopes;
- authenticated triggers and replay protection;
- idempotent external effects and reconciliation;
- error workflow, retries, circuits, dead-letter ownership;
- AI schema/evaluation/human gate if used;
- TLS/database/retention/backups/restore;
- metrics, alerts, capacity test, and cost model;
- versioned workflows, runbooks, rollback, training, and access removal.
Acceptance Matrix
Test valid, missing, malformed, oversized, duplicate, invalid auth/signature, expired credential, 429, timeout before/after effect, upstream outage, cross-tenant access, STOP/consent where relevant, post-approval change, process restart, disk/database alert, backup restore, version rollback, and client-operated pause.
Critical failure means NO-GO. Save expected/actual evidence, severity, owner, fix, and retest.
Worked Example
A Lahore maintenance company deploys website enquiry → CRM draft → Sales queue. It replies on WhatsApp only to the requested service enquiry under policy; marketing stays false. Source event and message IDs deduplicate retries. After-hours expectation is explicit.
The first load test reveals CRM limits create backlog. Concurrency is reduced, bounded queue/backoff added, and p95 queue age alert created. A restore drill proves database/key recovery. The client operates pause and removes the developer’s admin role. Pilot evidence reports completion/error/response metrics without promising sales growth or 500,000-user capacity.
Failure Cases to Diagnose
- Happy path called finished: run the full matrix.
- Production credential in lab: isolate environments.
- Retry duplicates effects: add durable idempotency/reconciliation.
- Client cannot pause/recover: block handover acceptance.
- License/client-hosting unclear: verify before deployment.
- Scale inferred: publish only measured workload.
🇵🇰 Pakistan Angle
Use PKT operations, PKR cost with dated assumptions, client-owned local channel/payment accounts, and English/Roman Urdu comprehension tests where needed. Do not collect CNIC, bank, or health data without necessity and qualified review.
Sell the measured operational result and support lifecycle. No passive-income, employee-replacement, guaranteed-conversion, or “runs forever” claim belongs in the case study.
Hands-On Exercise
- Complete all ten release sections.
- run every acceptance test.
- fix/retest critical defects.
- conduct limited pilot and rollback drill.
- hand over ownership and publish evidence report.
Completion Rubric
- Scope, owners, states, and authorities are explicit.
- Triggers/effects are secure and idempotent.
- Error/recovery/restore/rollback pass.
- Capacity and cost are measured.
- Client can operate and remove builder access.
- Claims match pilot evidence only.
Sources
- n8n Docs — Hosting
- n8n Docs — Error handling
- n8n Docs — Scaling
- OWASP — Application Security Verification Standard
Key takeaway: a complete automation is a secure, recoverable, measured, client-owned operating system—not a canvas that happens to run once.