Lead routing failure
Lead captured, downstream handoff unproven.
The lead was captured, but CRM creation and notification proof are missing.
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
Lead captured at the source with timestamp, source name, and expected downstream handoff.
Missing downstream proof
Quiet failure boundary
No CRM record ID, Slack message, or email delivery evidence is attached to the lead handoff.
Exact next action
Proof / next action
Open the provider run for this lead, inspect the CRM create step first, then rerun or repair the notification branch and attach the resulting record/message proof.
Missing proof
This scenario has no downstream evidence yet.
Proof found
Not claimed in this static demo.
Observed evidence
Lead captured at the source with timestamp, source name, and expected downstream handoff.
Missing proof
No CRM record ID, Slack message, or email delivery evidence is attached to the lead handoff.
Inferred risk: A sales follow-up may be delayed because the lead could be trapped before the CRM or notification step.
Next action
Open the provider run for this lead, inspect the CRM create step first, then rerun or repair the notification branch and attach the resulting record/message proof.
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/lead-routing-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
- Lead captured, downstream handoff unproven.
- Proof
- Observed source event is available; CRM and notification proof are missing.
- Next action
- Check the CRM create step before changing the form, because the source event already exists.
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.