How to connect ServiceNow and Slack with Make in 2026

Quick answer

A ServiceNow Slack integration connects your ITSM platform to your chat workspace so incidents, requests, and approvals move between the two without anyone opening a portal.

There are three ways to build it: the native ServiceNow for Slack app, a custom build on ServiceNow's REST API, or an automation platform like Make.

The native app covers incident actions and approvals inside Slack. Make covers the same ground and adds routing, multi-app steps, and a visual record of every run.

Introduction

Support portals are the primary IT support channel for just 13% of end users, behind phone at 27% and email at 22%. Your team already answers questions in Slack, then retypes the outcome into ServiceNow.

That gap costs you twice: duplicate updates nobody fully trusts, and approvals that stall because the approver never logged in.

A ServiceNow Slack integration closes it.

This guide covers the native app, where it runs out of room, and how to build a two-way flow with Make in six steps.

What is a ServiceNow Slack integration?

It is a connection between your ITSM system of record and your chat workspace that moves records, updates, and approvals in both directions.

At minimum, it posts ServiceNow activity into Slack channels. At its most useful, it also writes Slack activity back onto the ServiceNow record.

Three approaches get you there:

Your choice comes down to how many systems the process touches. Two systems, and the native app is a fair baseline. 

More than two, and the logic needs a central home, which is what ServiceNow integrations on Make provide.

How does the native ServiceNow for Slack app work?

The ServiceNow app for Slack lets you raise and update incidents from any message, submit catalog requests, action approvals, and receive channel alerts when records change. Setup needs a ServiceNow System Administrator and runs in four stages.

1. Install ServiceNow for Slack from the Slack Marketplace and click Add to Slack

2. Click Prepare OAuth on ServiceNow in the app's Home tab, then create an OAuth API endpoint for external clients in your Application Registry

3. Click Connect ServiceNow to Slack and enter your instance URL, client ID, and client secret

4. Download the Notifications Update Set, commit it in ServiceNow, then assign the x_545827_slack_std.user role to anyone managing channel alerts

That fourth stage is where most teams stall, because committing an Update Set is a platform change rather than a Slack setting.

The app also connects two systems only, so a process touching Jira, PagerDuty, or a warehouse lives somewhere else. Routing is fixed, and the audit trail splits across two products, so visibility over the whole automation landscape is what you give up.

For teams whose process starts and ends in these two apps, that is a fair trade. For everyone else, read on.

What do you need to connect ServiceNow and Slack with Make?

One requirement catches people out. ServiceNow sits on the Make Enterprise plan while Slack carries no plan restriction, so the two halves of this build have different entry points.

How do you connect ServiceNow and Slack with Make?

Six steps, from an empty canvas to a flow that writes Slack replies back onto the ServiceNow record.

Step 1: How do you create the ServiceNow and Slack connections?

In ServiceNow, open All and search for System OAuth > Application Registry. Click New, choose Create an OAuth API endpoint for external clients, and name it Make. 

Leave the client secret blank so ServiceNow generates it, set the redirect URL to https://www.make.com/oauth/cb/servicenow2, then reopen the record to copy the client ID and secret.

 In Make, add a ServiceNow module and click Create a connection. The field that trips people up is Sub domain: for https://acme.service-now.com, you enter acme only, with no trailing dot and no service-now.com.

Then add a Slack module and create two connections, Slack (bot) and Slack (user). Name each one clearly, because you will pick between them repeatedly.

Step 2: How do you set ServiceNow as the trigger?

Add ServiceNow > Watch Records as the first module. Set Table to Incident and watch records that are created or updated, so reopened tickets fire as well as new ones.

Keep Limit at 2 while you build. ServiceNow polls rather than pushing, so open the scheduling clock and set the shortest interval your plan allows.

Run the module on its own before going further. That pulls a real bundle and gives you the field names to map downstream: number, short_description, priority, assigned_to, assignment_group, and sys_id.

Do not guess those names. ServiceNow field labels and database column names often differ, so work from the bundle rather than the form, and check the ServiceNow modules docs for the rest.

Step 3: How do you split incidents by priority?

Click the plus on the right edge of the trigger and add Router from Flow control. Give it three routes: P1 to a dedicated channel, P2 to the on-call channel, and P3 or below to a digest channel.

Here is the sequencing point most guides skip. A filter in Make lives on the connecting line between two placed modules, so you cannot filter a route with nothing on the far end of it.

Place the Router first, drop at least one module onto each route, and only then set the filters in step 4. Building in the other order leaves you clicking a connector that does not exist yet.

Step 4: How do you filter each route?

Click the wrench icon on the connector leaving the Router for route one and choose Set up a filter. Label it P1 major and set the condition to priority, Numeric: equal to, 1.

Repeat on route two with priority equal to 2, and route three with priority greater than or equal to 3.

ServiceNow returns priority as a number from 1 (Critical) to 5 (Planning), so use numeric operators rather than text ones, or every route evaluates false.

If you want only one assignment group in scope, put that condition in a single filter on the connector going into the Router. One filter to maintain beats three that drift apart.

Step 5: How do you post the incident into Slack?

On the P1 route, build a war room in three modules: Slack > Create a Channel with Name mapped to inc-{{number}} in lowercase, then Slack > Invite Users with the channel ID from the previous module, then Slack > Send a Message into that channel.

Carry the incident number, short description, priority, and assignee in the message text, plus a deep link built from your instance URL, /nav_to.do?uri=incident.do?sys_id=, and the sys_id. That link is what turns a status channel into one people can act from.

One thing to keep in mind. The Send a Message module on a bot connection returns a channel not found error unless the bot is in the channel.

The bot created this one, so it is already in. For routes two and three, invite it to the standing channels by hand, once.

Step 6: How do you send Slack replies back to ServiceNow?

This half needs its own scenario, because the trigger now sits in Slack rather than ServiceNow.

Add Slack > Watch New Events as an instant trigger. Click Create a webhook first, then attach the Slack (user) connection, set Event type to New channel message, and select the incident channel.

Add ServiceNow > Search Records on the incident table, querying number against the value parsed out of the channel name to recover the sys_id. Then ServiceNow > Update a Record, with Record ID set to that sys_id and work_notes set to the message text plus the author's name.

 Now the part that will bite you if you skip it. Filter out messages posted by your own bot, testing that the bot ID is empty, or your step 5 message triggers this scenario, which writes to ServiceNow, which fires the first scenario again.

What are the best ServiceNow Slack integration use cases?

Once records flow both ways, the same trigger, route, and post structure covers most of what an IT team wants from chat.

The last row is the one the native app cannot reach, and it usually justifies the build. Most start as two-app flows and pick up a third within a quarter, which is the case for IT automation sitting above both platforms.

How do you test and keep the integration reliable?

A scenario that works on a test incident and fails at 2 a.m. is worse than no scenario. Five habits keep this one honest.

• Run each scenario against a test incident and confirm the route you expected fired, before you activate anything

• Check the scenario history weekly, and read the input and output of any failing module rather than guessing

• Add an error handler to the Slack modules so one archived channel does not stop the whole run

• Keep pagination on for Slack Watch modules, and expect throttling on high-volume channels

• Send low-priority digests on a schedule rather than instantly, which keeps your operation count predictable

The visibility is the point: every run leaves a record you can open, which is what makes this something you can hand to someone else.

What is your next step with ServiceNow and Slack?

If your process starts and ends in ServiceNow and Slack, install the native app and get on with your week.

If your process already involves a third system, or you want branching the native app cannot express, build it on Make instead.

You get one canvas showing the whole flow, one run history covering both directions, and one place to add the next app when it arrives.

Ready to build it? Start building now and connect your first ServiceNow trigger today.

FAQs

Q1. Is the ServiceNow Slack integration free?

The ServiceNow for Slack app costs nothing to install, but you need a paid ServiceNow instance and a Slack workspace. Building it on Make instead requires a plan that includes the ServiceNow app.

Q2. Do you need a ServiceNow admin to set it up?

Yes. The native app requires a ServiceNow System Administrator, because setup creates an OAuth endpoint and commits an Update Set. The Make route also needs an admin for the application registry entry.

Q3. Can a Slack message create a ServiceNow incident automatically?

Yes. The native app does it through a message shortcut someone clicks. For hands-off creation, pair Slack Watch New Events with ServiceNow Create an Incident in a Make scenario, or start from a ready-made template. 

Q4. Which ServiceNow plan supports the Slack integration?

Any ServiceNow instance with OAuth activated supports the Slack app. Conversational Integration with Slack, the Virtual Agent version, is a separate ServiceNow Store listing with its own requirements.

Q5. Which Make plan do you need for the ServiceNow app?

ServiceNow is available on Make Enterprise. The Slack app has no plan restriction, so you can build and test the Slack half of the flow on any plan first.

Q6. Can you sync ServiceNow approvals into Slack?

Yes. The native app posts pending approvals and lets approvers act in Slack. In Make, watch the approval table with ServiceNow Watch Records, post to Slack, then write the decision back using ServiceNow Update a Record.