Look up ServiceNow incident details from a Slack command

Typing a Slack command pulls the matching ServiceNow incident details straight into your chat.

How the work actually flows

It branches. Exactly one path is taken.

Pattern: Exclusive Choice (4) · Simple Merge (5)

flowchart TD trig>"slash command typed in slack"]:::trig s0["extract incident id"]:::task s1["look up incident in servicenow"]:::svc s2["post reply in slack"]:::svc trig --> s0 s0 --> s1 gx{"× incident found"}:::gate s1 --> gx p00["format incident details"]:::task gx -->|"found"| p00 p10["format not found message"]:::task gx -->|"not found"| p10 jn{"○ merge response"}:::gate p00 --> jn p10 --> jn jn --> s2 out[/"incident details posted in slack"/]:::out pay{{"faster status checks without switching tools"}}:::pay s2 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepAn outside serviceOne path onlyPaths rejoinResultPayoff
Build size
Standard

A mid-size build with several tools working together.

Business functions
Messaging & NotificationsAPI & Webhook Integration
Connects
SlackServiceNow

The problem it solves

Checking on an incident means leaving Slack, logging into ServiceNow, and searching for the ticket, which breaks your focus every time someone asks for a status update. That back-and-forth adds up over a busy day.

Who it fits

IT support or operations teams that manage incidents in ServiceNow and communicate over Slack.

How it works

  1. Starts when someone types the slash command with an incident ID in Slack
  2. Extracts the incident ID from the message
  3. Looks up the matching incident in ServiceNow
  4. Formats the incident details, or a not-found message, as a reply
  5. Posts the response back in Slack
What you get

Incident lookups that skip the tab switch

You type an incident ID in Slack and get the matching ServiceNow details posted right back to your channel.

What you get

A Slack message showing the incident's ID, description, severity, and priority.

What you need

A Slack workspace and a ServiceNow account.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Automatically escalate service tickets that are about to breach SLA

Tickets close to breaking their SLA get flagged and escalated to Slack, Teams, or an on-call engineer automatically.

Advanced

Check IP reputation and alert your SOC team automatically

When a Splunk alert flags a suspicious IP, the system checks it against VirusTotal and AlienVault and notifies your team.

Advanced

Look up ServiceNow incidents from a Slack pop-up form

Lets you pull up recent ServiceNow incidents right inside Slack, without switching to another tool.

Advanced

Notify your team in Slack the moment an incident is logged

Checks ServiceNow for new incidents and posts the details to Slack automatically, so nobody has to keep checking.

Advanced
Back to the AI Playbook