Receive Slack Webhook Slash Command
Configured with Respond To Webhook, Service Now, Switch, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Transform
- Integration
- Web / API
- Routing
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Webhook | Trigger | Webhook | See node parameters |
| Extract Incident ID from Response | Transform | Edit Fields | See node parameters |
| Search For Incident in ServiceNow | Integration | Service Now | incident / getAll |
| Send Incident Details to Slack | Web / API | Respond To Webhook | See node parameters |
| Notify User no Incident was Found | Web / API | Respond To Webhook | See node parameters |
| Notify User of Error with ServiceNow | Web / API | Respond To Webhook | See node parameters |
| Parse ServiceNow Response | Routing | Switch | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
serviceNowBasicApi
Workflow notes
Receive Slack Webhook Slash Command
Receive Slack Webhook Slash Command
This section begins with the Webhook node, which listens for incoming Slack Slash Command requests. When triggered, it extracts the incident ID from the request payload using the Extract Incident ID from Response node. The incident ID is then passed forward for further processing. This setup allows users to initiate ServiceNow incident lookups directly from Slack.
Search ServiceNow for Incident
Search ServiceNow for Incident
In this section, the Search For Incident in ServiceNow node queries the ServiceNow platform using the extracted incident ID. If the query returns a valid incident, the details are prepared for the Slack response. If no incident is found, the workflow routes this outcome for a corresponding Slack notification. The Parse ServiceNow Response node evaluates the outcome of the ServiceNow query. This ensures accurate and responsive communication with ServiceNow.
Respond to Slack Webhook
Respond to Slack Webhook
Based on the ServiceNow result:
- The
Send Incident Details to Slacknode formats and sends detailed incident information to Slack. - The
Notify User no Incident was Foundnode sends a user-friendly notification indicating the incident ID was invalid. - The
Notify User of Error with ServiceNownode alerts the user if the ServiceNow connection fails. This ensures users receive the right response for every scenario, enabling seamless incident management directly from Slack.
Receive Slack Webhook Slash Command
Receive Slack Webhook Slash Command
Purpose and structure
This folder contains the Receive Slack Webhook Slash Command workflow. Its executable nodes use respondToWebhook, serviceNow, set, switch, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Webhook
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Stickynote/0684_Stickynote_Respondtowebhook_Send_Webhook.json MIT; preserve source notices.