Block 1 - 1. Webhook Trigger (Status Update)
- Type / Role
- n8n-nodes-base.webhook - webhook
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
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'...
n8n-nodes-base.webhook, n8n-nodes-base.function, n8n-nodes-base.slack, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Marth.
Original n8n.io sourceThis workflow acts as a communication bridge for your candidate pipeline:
#recruitment-updates). This provides instant, real-time updates to your team, ensuring everyone is on the same page.Follow these steps carefully to get your "Automated Candidate Status Notifier" workflow up and running:
functionCode inside this node. You MUST adjust the variable assignments (e.g., inputData.candidateName, inputData.position) to accurately match the exact field names your sending system uses for candidate name, position, new status, old status, and notes. Use the 'Test Workflow' feature after sending a test webhook to inspect the incoming items[0].json.body data structure.YOUR_SLACK_CREDENTIAL_ID with the actual ID or name of your credential from your n8n credentials.YOUR_SLACK_CHANNEL_ID_OR_NAME with the exact ID or name of the Slack channel where you want to receive notifications (e.g., #recruitment-updates).[email protected]).={{ $json.emailSubject }}.={{ $json.emailBody }}.YOUR_...) are replaced and settings are correct.This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Automated recruitment status updates via Slack notifications |
|---|---|
| Complexity | intermediate |
| Nodes | 5 |
| Categories | HR |
| Author | Marth |
| Published | 24 Jul 2025 |
Use the JSON export at /data/workflows/6360/6360.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
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'...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your HR use case.