Resume failed workflow runs from checkpoints with Postgres and Slack
Ready for 3.0What this workflow does
This workflow has 48 nodes and runs manually, when you click “Execute workflow” (plus 3 other triggers). Along the way it connects Postgres and Slack.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 3 other triggers).
- Set - Mode Manual (Edit Fields (Set)): sets 1 field: entryMode
- Set - Mode Webhook (Edit Fields (Set)): sets 1 field: entryMode
- Set - Mode Sweeper (Edit Fields (Set)): sets 1 field: entryMode
- Slack: uses Slack
- Set - Checkpoint Config (Edit Fields (Set)): sets 10 fields: workflowName, maxStageAttempts, stageBackoffSeconds…
- Postgres: run a query
- Switch: routes items into 2 branches
- Postgres: run a query
- JS - Init Run (Code): runs custom JavaScript code
- JS - Build Resume Requests (Code): runs custom JavaScript code
…plus 34 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (12)
- Manual Trigger
n8n-nodes-base.manualTrigger - Webhook
n8n-nodes-base.webhook - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Postgres
n8n-nodes-base.postgres - Switch
n8n-nodes-base.switch - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Wait
n8n-nodes-base.wait - Slack
n8n-nodes-base.slack - Error Trigger
n8n-nodes-base.errorTrigger
From the author
Quick overview This workflow implements a checkpoint-and-resume system for a multi-stage pipeline, storing stage outputs in Postgres and sending failure/recovery alerts to Slack, with manual, webhook, and scheduled triggers to start runs and automatically…