01
Signed callbacks
Receive tenant-scoped execution receipts with bounded payloads and replay-safe identifiers.
n8n · Execution to outcome
A successful execution is not the same as a successful business result.
Liulum receives signed n8n callbacks, watches expected schedules, and reconciles the workflow trigger with the outcome your business requires.
02
Schedule heartbeats
Detect a workflow that stopped reporting inside its configured cadence and grace window.
03
Outcome checks
Compare the run with the order, fulfilment, CRM, billing, or customer event expected downstream.
Evidence contract
A state changes only when a configured check records proof.
Best for self-hosted or cloud n8n workflows tied to revenue operations. Missing data remains unavailable; an execution signal alone never proves the customer or business outcome happened.
- 01
Test the callback secret and tenant mapping before the workflow is considered connected.
- 02
Record the execution and required downstream result at the same correlation key.
- 03
Retry only an idempotent customer-approved action, then verify the result independently.
Start with one path