Client onboarding failure
Customer start event exists; onboarding completion is not proven.
The customer signs up, but the downstream onboarding step remains unproven.
What this demo is / is not
- Simulated example: static scenario data for reading the proof loop.
- Safe demo data: no customer data, provider calls, or live workflow inspection.
- Not connected: it does not inspect your workflows.
- Real proof: real proof requires connecting or configuring Make, n8n, or Zapier.
Observed trigger to missing proof
This static demo stops at the missing-proof state and names the safest next check.
Observed trigger
Signup or payment event exists with expected onboarding workflow target.
Missing downstream proof
Quiet failure boundary
No task ID, folder creation timestamp, or welcome email delivery marker is present.
Exact next action
Proof / next action
Inspect the first onboarding creation step and confirm whether the task/folder/email branch received the customer payload.
Missing proof
This scenario has no downstream evidence yet.
Proof found
Not claimed in this static demo.
Observed evidence
Signup or payment event exists with expected onboarding workflow target.
Missing proof
No task ID, folder creation timestamp, or welcome email delivery marker is present.
Inferred risk: A new customer may be waiting without internal setup, files, or first instructions.
Next action
Inspect the first onboarding creation step and confirm whether the task/folder/email branch received the customer payload.
Recovery should only be treated as proven after downstream evidence exists.
Technical demo assets
Optional repo docs for operators who want the sample workflow spec and JSON payloads. These are demo assets, not hosted provider proof or required reading.
Repo path: docs/demo-workflows/client-onboarding-failure/README.md
Sample JSON and workflow files
workflow.mdsource-event.sample.jsonobserved-evidence.sample.jsonmissing-proof.sample.jsonexpected-diagnosis.sample.json
Diagnosis loop details
- Diagnosis
- Customer start event exists; onboarding completion is not proven.
- Proof
- Observed signup/payment evidence exists; task/folder/email proof is missing.
- Next action
- Verify the task or folder branch before sending any follow-up manually.
Provider-specific note
The same proof pattern can be modeled for Make, n8n, or Zapier. Provider capability levels differ, so this page avoids provider-parity and automatic recovery claims.