Automated recruitment status updates via Slack notifications
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Function (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 3 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.
- 2. Extract & Prepare Data (Function): runs custom JavaScript (legacy Function node)
- 3. Send Slack Notification (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Function (legacy) in 2. Extract & Prepare Data: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) 2. Extract & Prepare Data | Code node, mode 'Run Once for All Items' |
Nodes used (3)
- Webhook
n8n-nodes-base.webhook - Function
n8n-nodes-base.function - Slack
n8n-nodes-base.slack
From the author
How It Works ⚙️ This workflow acts as a communication bridge for your candidate pipeline: 1. Webhook Trigger (Status Update): 🚀 The workflow activates when it receives data indicating a candidate's status has changed. This data could come from an internal…