Display ServiceNow incident details in Slack using slash commands
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 7 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects ServiceNow.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Extract Incident ID from Response (Edit Fields (Set)): sets 1 field: incident_id
- Search For Incident in ServiceNow (ServiceNow): get many (incident)
- Parse ServiceNow Response (Switch): routes items into 3 branches
- Notify User of Error with ServiceNow (Respond to Webhook): sends the response back to the webhook caller
- Notify User no Incident was Found (Respond to Webhook): sends the response back to the webhook caller
- Send Incident Details to Slack (Respond to Webhook): sends the response back to the webhook caller
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 (5)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - ServiceNow
n8n-nodes-base.serviceNow - Respond to Webhook
n8n-nodes-base.respondToWebhook - Switch
n8n-nodes-base.switch
From the author
Who is this for? This workflow is designed for teams using Slack for communication and ServiceNow for incident management. It simplifies incident lookup by enabling team members to fetch incident details directly within Slack via a Slash Command. What problem…