Docs
Business events
Send your own KPIs from a workflow and alert on them, so "the sync ran" and "the sync was right" are different questions.
Run health tells you the workflow finished. It does not tell you whether the number it produced was sensible. Business events let a workflow report its own metrics — orders synced, invoices created, leads scored — so you can alert on the number rather than on the exit status.
Events are sent with the n8n-nodes-obsevo community node, or by posting to /ingest/events with an
event key.
Thresholds
A threshold watches one event name and alerts when its value moves outside the
range you set, over the window you choose. That raises a business_threshold
incident, which routes through the same channels, quiet
hours and escalation as everything else.
This is how you catch the case where every run is green, every log is clean, and the number is simply wrong.
Retention
Business events are kept far longer than raw run history — the default is 400 days against 30 for runs — because a KPI series is only useful if you can compare this month against last year.