Manage engineering change requests via webhooks and Slack approvals
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 16 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Slack.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- If: checks a condition and branches into true / false
- Return Response (Error) (Respond to Webhook): sends the response back to the webhook caller
- Generate Secure Token (Crypto): hashes or encrypts values
- Generate ECR Metadata (Set Node) (Edit Fields (Set)): sets 3 fields: ecr_id, token, status
- Switch: routes items into 3 branches
- Set Low (Edit Fields (Set)): sets 1 field: impact_level
- Set Medium (Edit Fields (Set)): sets 1 field: impact_level
- Set High (Edit Fields (Set)): sets 1 field: impact_level
- Set Medium (Fallback) (Edit Fields (Set)): sets 1 field: impact_level
- Return Success (Respond to Webhook) (Respond to Webhook): sends the response back to the webhook caller
…plus 5 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 (8)
- Webhook
n8n-nodes-base.webhook - If
n8n-nodes-base.if - Switch
n8n-nodes-base.switch - Edit Fields (Set)
n8n-nodes-base.set - Slack
n8n-nodes-base.slack - Wait
n8n-nodes-base.wait - Respond to Webhook
n8n-nodes-base.respondToWebhook - Crypto
n8n-nodes-base.crypto
From the author
⚙️ Manage Engineering Change Requests (ECR) via Slack 📋 Overview Streamline your engineering change management process by integrating generic webhooks with Slack interactive approvals. This workflow receives a generic design change request, categorizes its…