Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Incident Notification and Response Workflow

Incident Notification and Response Workflow is a 21-node automation blueprint connecting ServiceNow, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

ServiceNowSlack

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

21

Nodes

21

Links

1

Run groups

Connected tools

2 integrations

  • ServiceNow
  • Slack

Canvas controls

Fit wide systems, then zoom into any run group.

Incident Notification and Response Workflow execution lanes1 run groups containing 21 workflow nodes and 21 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Webhook. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTParse Webhook. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Parse WebhookTRANSFORMSET1 IN / 1 OUTRoute Message. decision node, switch. 1 incoming and 3 outgoing connections.STEP 03Route MessageDECISIONSWITCH1 IN / 3 OUTRespond to Slack Webhook. Slack node, respondToWebhook. 1 incoming and 1 outgoing connections.STEP 04Respond to Slack WebhookSLACKRESPONDTOWEBHOOK1 IN / 1 OUTClose Modal Popup. trigger node, respondToWebhook. 1 incoming and 1 outgoing connections.STEP 04Close Modal PopupTRIGGERRESPONDTOWEBHOOK1 IN / 1 OUTSend 200. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 04Send 200TRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTServiceNow Modal. integration node, httpRequest. 1 incoming and 0 outgoing connections.STEP 05ServiceNow ModalINTEGRATIONHTTPREQUEST1 IN / 0 OUTServiceNow. integration node, serviceNow. 1 incoming and 1 outgoing connections.STEP 05ServiceNowINTEGRATIONSERVICENOW1 IN / 1 OUTWere Incidents Found?. decision node, if. 1 incoming and 2 outgoing connections.STEP 06Were Incidents Found?DECISIONIF1 IN / 2 OUTSort by Most Recent. integration node, sort. 1 incoming and 1 outgoing connections.STEP 07Sort by Most RecentINTEGRATIONSORT1 IN / 1 OUTNo Matches - Was a Channel Selected?. decision node, if. 1 incoming and 2 outgoing connections.STEP 07No Matches - Was a Channe…DECISIONIF1 IN / 2 OUTRetain First 5 Incidents. integration node, limit. 1 incoming and 1 outgoing connections.STEP 08Retain First 5 IncidentsINTEGRATIONLIMIT1 IN / 1 OUTChannel - Notify User no Incidents Matched. Slack node, slack. 1 incoming and 0 outgoing connections.STEP 08Channel - Notify User no …SLACKSLACK1 IN / 0 OUTDM - Notify User no Incidents Matched. Slack node, slack. 1 incoming and 0 outgoing connections.STEP 08DM - Notify User no Incid…SLACKSLACK1 IN / 0 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 2 outgoing connections.STEP 09Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 2 OUTConcatenate Incident Details. transform node, summarize. 1 incoming and 1 outgoing connections.STEP 10Concatenate Incident Deta…TRANSFORMSUMMARIZE1 IN / 1 OUTFormat Incident Details. transform node, set. 1 incoming and 1 outgoing connections.STEP 11Format Incident DetailsTRANSFORMSET1 IN / 1 OUTFormat Slack Message. Slack node, set. 1 incoming and 1 outgoing connections.STEP 12Format Slack MessageSLACKSET1 IN / 1 OUTWas a Channel Selected?. decision node, if. 1 incoming and 2 outgoing connections.STEP 13Was a Channel Selected?DECISIONIF1 IN / 2 OUTChannel - Send Matching Incidents. Slack node, slack. 1 incoming and 0 outgoing connections.STEP 14Channel - Send Matching I…SLACKSLACK1 IN / 0 OUTDM - Send Matching Incidents. Slack node, slack. 1 incoming and 0 outgoing connections.OUTCOMEDM - Send Matching Incide…SLACKSLACK1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.21 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

Respond to Slack Webhook

21 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Parse Webhook

    Transform

  3. Step 3

    Route Message

    Decision

  4. Step 4

    Respond to Slack Webhook

    Trigger

    Close Modal Popup

    Trigger

    Send 200

    Trigger

  5. Step 5

    ServiceNow Modal

    Integration

    ServiceNow

    Integration

  6. Step 6

    Were Incidents Found?

    Decision

  7. Step 7

    Sort by Most Recent

    Integration

    No Matches - Was a Channel Selected?

    Decision

  8. Step 8

    Retain First 5 Incidents

    Integration

    Channel - Notify User no Incidents Matched

    Integration

    DM - Notify User no Incidents Matched

    Integration

  9. Step 9

    Loop Over Items

    Integration

  10. Step 10

    Concatenate Incident Details

    Transform

  11. Step 11

    Format Incident Details

    Transform

  12. Step 12

    Format Slack Message

    Transform

  13. Step 13

    Was a Channel Selected?

    Decision

  14. Step 14

    Channel - Send Matching Incidents

    Integration

  15. Outcome

    DM - Send Matching Incidents

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas