12 · triggers
Starts a dedicated workflow when another workflow fails.
When to use it
Production graphs that must not die quietly. Keep Error Trigger in its own Active workflow and link producers via Settings → Error Workflow.
Writeup
Starts a dedicated workflow when another workflow fails. Production graphs that must not die quietly. Keep Error Trigger in its own Active workflow and link producers via Settings → Error Workflow.
Step by step — how to wire it
01
New alerts workflow
Add Error Trigger → Set (summary) → Slack #ops.
02
Activate alerts
Toggle Active on the error workflow itself.
03
Link a producer
Open Form to Slack (etc.) → Settings → Error Workflow → select alerts → Save.
04
Force a test fail
Break a URL briefly, Execute, confirm #ops, then restore.
How it functions
Separate workflow
Error Trigger is usually the only start node in an alerts workflow.
Producer link
Each critical workflow points Settings → Error Workflow at this one.
Used for
Used for 1
Paging #ops on red executions
Used for 2
Central failure formatting
Used for 3
Catching silent schedule/HTTP failures
Tips
Enrich Set with execution URL from the error payload for one-click debug.
Don’t attach noisy workflows or #ops becomes wallpaper.