01
Webhook receipt
Record the signed Liulum callback from the customer-configured Zap step.
Zapier · Outcome monitoring
Catch the missing outcome after the Zap.
Liulum receives the configured webhook evidence and verifies the downstream result your Zap is supposed to create.
02
Correlation window
Match the trigger and expected outcome using a tenant-scoped identifier and time window.
03
One incident
Group missing callbacks and downstream gaps into one evidence-backed incident.
Evidence contract
A state changes only when a configured check records proof.
Best for Zaps whose downstream customer or revenue outcome matters more than the task count. Missing data remains unavailable; an execution signal alone never proves the customer or business outcome happened.
- 01
Test the webhook connection before it becomes active.
- 02
Keep the trigger and downstream result at the same customer-defined grain.
- 03
Escalate with evidence when Zapier does not expose a safe recovery control.
Start with one path