Ops pager — Slack alert on failure
FAILURE-ALERT PRESET: the Error Trigger's recovery lane posts straight to Slack — import, point the Slack node at your channel credential, done. The demo fails on purpose so the lane fires; the console mirrors what the Slack message would say. Pair with meta.autoreplay for retry-then-page.
What’s inside
5 nodes — every type links to its full reference page.
| Step | Node | Type |
|---|---|---|
| Nightly export | Inject | input.inject |
| Export (fails) | Stop and Error | error-handling.stop-and-error |
| On failure | Error Trigger | error-handling.error |
| Slack #oncall | Slack | output.slack |
| Alert mirror | Console | utility.console |
Import it
- Studio → Import — paste the JSON below (or the URL
/docs/templates/ops-pager-slack-alert-on-failure.json). - Or ask the AI Copilot with the JSON pasted after the phrase:
import this workflow json into a new workflow named "Ops pager — Slack alert on failure" - Any credentials the nodes need are
${credential.…}references — add them once in Admin → Credentials and the template picks them up. Nothing secret ships in a template.
The workflow document (flowdrome.workflow.v1, 5 node types)
{
"schemaVersion": "flowdrome.workflow.v1",
"id": "",
"name": "Ops pager — Slack alert on failure",
"version": "0",
"status": "draft",
"nodes": [
{
"id": "seed",
"type": "input.inject",
"label": "Nightly export",
"category": "trigger",
"config": {
"contentType": "application/json",
"payload": {
"export": "daily-ledger"
}
},
"position": {
"x": 0,
"y": 0
}
},
{
"id": "boom",
"type": "error-handling.stop-and-error",
"label": "Export (fails)",
"category": "utility",
"config": {
"message": "export path \\\\vault\\ledger is unreachable",
"errorCode": "EXPORT_UNREACHABLE"
},
"position": {
"x": 530,
"y": 0
}
},
{
"id": "onerr",
"type": "error-handling.error",
"label": "On failure",
"category": "trigger",
"config": {
"includeNodeErrors": true
},
"position": {
"x": 0,
"y": 228
}
},
{
"id": "slack",
"type": "output.slack",
"label": "Slack #oncall",
"category": "output",
"config": {
"text": "🚨 {{ $json.workflowName }} failed: {{ $json.error.message }}",
"channel": "#oncall",
"botToken": "${credential.slack.botToken}"
},
"position": {
"x": 530,
"y": 228
}
},
{
"id": "mirror",
"type": "utility.console",
"label": "Alert mirror",
"category": "utility",
"config": {
"message": "would post to Slack: 🚨 {{ $json.workflowName }} failed"
},
"position": {
"x": 530,
"y": 406
}
}
],
"edges": [
{
"id": "e0",
"sourceNodeId": "seed",
"sourcePort": "output",
"targetNodeId": "boom",
"targetPort": "input"
},
{
"id": "e1",
"sourceNodeId": "onerr",
"sourcePort": "output",
"targetNodeId": "slack",
"targetPort": "input"
},
{
"id": "e2",
"sourceNodeId": "onerr",
"sourcePort": "output",
"targetNodeId": "mirror",
"targetPort": "input"
}
],
"triggers": [
{
"id": "t0",
"nodeId": "seed"
}
],
"meta": {
"snippets": [],
"source": "template-gallery",
"description": "FAILURE-ALERT PRESET: the Error Trigger's recovery lane posts straight to Slack — import, point the Slack node at your channel credential, done. The demo fails on purpose so the lane fires; the console mirrors what the Slack message would say. Pair with meta.autoreplay for retry-then-page."
}
} Generated from the verified demo corpus — this exact document seeds and runs on a fresh Flowdrome. Raw JSON: ops-pager-slack-alert-on-failure.json.