Skip to main content

ServiceNow incident notifications to Slack workflow

Workflow preview

Workflow preview
100%
ServiceNow incident notifications to Slack workflow preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Who is this for? This workflow is ideal for IT operations teams or system administrators who use ServiceNow to track incidents and Slack for team communication. It provides real time updates on new...

Best for

  • Ticket Management automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.scheduletrigger, n8n-nodes-base.datetime, n8n-nodes-base.servicenow, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.sort, n8n-nodes-base.noop

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Angel Menendez.

Original n8n.io source

1.1 Workflow description

Title
ServiceNow incident notifications to Slack workflow
Workflow name
ServiceNow incident notifications to Slack workflow

Who is this for?

This workflow is ideal for IT operations teams or system administrators who use ServiceNow to track incidents and Slack for team communication. It provides real-time updates on new ServiceNow incidents directly in a designated Slack channel, ensuring timely response and collaboration.

What problem is this workflow solving? / Use case

Manually monitoring ServiceNow for new incidents can be time-consuming and prone to delays. This workflow automates the process, ensuring that team members are instantly notified of new incidents, complete with all relevant details, in a Slack channel. It enhances operational efficiency and incident response time.

What this workflow does

  1. Schedule or Manual Trigger: The workflow can be triggered manually or set to run automatically every 5 minutes.
  2. Retrieve New Incidents: Fetches incidents created in ServiceNow within the last 5 minutes.
  3. Error Handling: Posts an error message in Slack if there are issues connecting to ServiceNow.
  4. Incident Processing:
    • If new incidents are found, they are sorted in ascending order by their number.
    • Detailed incident information is formatted and sent to a specified Slack channel.
  5. No Incidents: If no new incidents are found, the workflow does nothing.

Setup

  1. ServiceNow API Credentials: Configure ServiceNow Basic Authentication in the workflow to connect to your ServiceNow instance.
  2. Slack API Credentials: Add your Slack API credentials to enable message posting.
  3. Slack Channel Configuration:
    • Define the Slack channel where notifications should be sent.
    • Ensure the channel ID is correctly set in the Slack node.
  4. Adjust the Schedule: Modify the schedule in the Schedule Trigger node to suit your requirements.

How to customize this workflow to your needs

  1. Notification Format:
    • Customize the Slack message format to include additional or fewer details.
    • Update the Blocks section in the Slack node for personalized messages.
  2. Incident Query Parameters:
    • Adjust the sysparm_query parameter in the ServiceNow node to filter incidents based on specific criteria.
  3. Error Handling:
    • Modify the error message in the Slack node for more detailed troubleshooting information.

Features

  • Real-Time Notifications: Immediate updates on new ServiceNow incidents.
  • Error Handling: Alerts in Slack if the workflow encounters issues connecting to ServiceNow.
  • Customizable Notifications: Flexibility to modify incident details sent to Slack.

This workflow streamlines incident management and fosters collaboration by delivering actionable updates directly to your team.

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - When clicking ‘Test workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Run Every 5 Minutes

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 3 - Get 5 Minute Ago Timestamp

Type / Role
n8n-nodes-base.dateTime - dateTime
Config choices
Version 2

Block 4 - Get Incidents from ServiceNow

Type / Role
n8n-nodes-base.serviceNow - serviceNow
Config choices
Version 1

Block 5 - Check if New Incidents

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 6 - Post Error Message if Error with ServiceNow

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.2

Block 7 - Sort Incidents in Ascending Order

Type / Role
n8n-nodes-base.sort - sort
Config choices
Version 1

Block 8 - Post Incident Details to Slack Channel

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.2

Block 9 - No Incidents, Do Nothing

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

Block 10 - Sticky Note11

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Sticky Note12

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow ServiceNow incident notifications to Slack workflow
Complexity intermediate
Nodes 14
Categories Ticket Management
Author Angel Menendez
Published 07 Jan 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/2704/2704.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does ServiceNow incident notifications to Slack workflow do?

Who is this for? This workflow is ideal for IT operations teams or system administrators who use ServiceNow to track incidents and Slack for team communication. It provides real time updates on new...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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.