Block 1 - Parse Webhook
- Type / Role
- n8n-nodes-base.set - set
- Config choices
- Version 3.3
This workflow is provided as-is. Please review and test before using in production.
Who is this for? This workflow is designed for IT teams, service desk personnel, and incident management professionals who need a streamlined way to monitor and report on recent ServiceNow incident...
n8n-nodes-base.set, n8n-nodes-base.respondtowebhook, n8n-nodes-base.switch, n8n-nodes-base.httprequest, n8n-nodes-base.webhook, n8n-nodes-base.servicenow, n8n-nodes-base.slack, n8n-nodes-base.if
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Angel Menendez.
Original n8n.io sourceThis workflow is designed for IT teams, service desk personnel, and incident management professionals who need a streamlined way to monitor and report on recent ServiceNow incidents directly within Slack.
Manually monitoring incidents in ServiceNow can be time-consuming, and keeping teams updated about new or specific incidents often involves additional manual effort. This workflow automates the process of querying recent incidents from ServiceNow based on user-defined parameters and delivering formatted results directly to Slack. It ensures faster response times and improved incident visibility.
This workflow integrates Slack and ServiceNow to provide an automated system for retrieving and presenting incident details.
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.
Showing the first 24 of 29 workflow blocks. Download the JSON for the full node graph.
| Workflow | List recent ServiceNow incidents in Slack using pop up modal |
|---|---|
| Complexity | advanced |
| Nodes | 29 |
| Categories | Ticket Management |
| Author | Angel Menendez |
| Published | 15 Jan 2025 |
Use the JSON export at /data/workflows/2728/2728.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.
Who is this for? This workflow is designed for IT teams, service desk personnel, and incident management professionals who need a streamlined way to monitor and report on recent ServiceNow incident...
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 Ticket Management use case.