- Home
- Resources
- Integrations
- ServiceNow
ServiceNow Zapier integrationAutomate ServiceNow with Zapier.
The ServiceNow Zapier integration covers 2 triggers, 4 actions and 2 searches. Records created or updated in a table can start a Zap, and a Zap can create, update, attach to or look up records for you, with every step tied to one table.
Premium app Zapier reserves this app to its paid plans.
Verified Trustpilot reviews · AI, automation & growth agency
What the ServiceNow Zapier integration actually does
The ServiceNow Zapier integration links your ServiceNow instance to the rest of your tools without code. Zapier watches a table for new or changed records, then writes back into ServiceNow, or into another app, every time something shows up. Everything it does is organised around tables.
Three results come up again and again. First, a record copied elsewhere: New Record spots a fresh entry in the table you pick, and the next step pushes it into a chat tool, a sheet or a CRM. Second, a record kept in sync: Updated Record notices a change, Find Record locates the matching entry, and Update Record writes the new values. Third, a file filed in the right place: a document arriving in another app lands on the right record through Attach a File to a Record.
What Zapier does not do here matters as much. Both triggers are checked on a timer, so nothing reaches the Zap the second it happens. There is no delete action, so removing records stays a manual job or an API call. And anything outside the menu goes through API Request (Beta), which is advanced territory.
If you are weighing other tools, the same app is covered on our ServiceNow n8n integration and ServiceNow Make integration pages.
Zapier vocabulary in one minute
Seven words cover everything on this page. Each one is explained here once, then used as is.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for it to occur.
- Action
- What the Zap does after it starts: the step that creates, updates or sends something on your behalf.
- Task
- The unit Zapier bills. One action that completes successfully is one task, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer by Zapier. An instant one is pushed by the app the moment it happens.
- Filter
- A step that lets the Zap continue only when what arrived matches your condition, and stops it quietly otherwise.
- Search step
- A step that looks up a record that already exists, so the steps after it can reuse what it found.
What a ServiceNow Zap really costs
ServiceNow is a premium app on Zapier, so the free plan is out: you need a paid plan or the free trial.
- Premium appYes, paid plan or trial
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps, no premium apps
The trigger never costs a task, and neither does Zapier checking the table, however often it looks. You pay for actions that succeed: a Zap that creates a record and then attaches a file uses two tasks per run. An action that fails is not counted. Keep in mind that adding a filter, a search or a second action turns the Zap into a multi-step Zap, which is a paid feature anyway. How fast your triggers react depends on the plan.
Connect ServiceNow to Zapier in three steps
- 01
Open your apps
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your ServiceNow account linked once, then reused by every Zap that touches it.
- 02
Pick ServiceNow
Type ServiceNow in the search box of the dialog, select it, then click Add connection. A new browser tab opens so you can sign in to ServiceNow with an existing account.
- 03
Sign in and grant access
Log in with the ServiceNow account the Zaps should act as, then allow Zapier to use it. That account needs read or write rights on every table you plan to watch or change.
Your first ServiceNow Zap
GoalCopy every new record of a table into another app, but only the ones that matter.
- 01
Create the Zap
From your Zapier dashboard, start a new Zap. The editor opens on an empty trigger step, which is where ServiceNow comes in.
- 02
Set the trigger
Pick ServiceNow, choose New Record, select your connection, then the table to watch. That table choice is mandatory, and it decides everything the Zap will see.
- 03
Test with real data
Run the trigger test. Zapier pulls the three most recent records of that table so you can build the next steps on a real one, not on a guess.
- 04
Add the filter and the action
Add a filter that keeps only the records you care about, then the step in your other app. Map the record fields into it, and test that step once too.
- 05
Publish
Click Publish to switch the Zap on. From then on, new records are picked up at each check, at the pace your plan allows.
ServiceNow triggers
2 events start a Zap when something happens in ServiceNow. Zapier checks for them at the interval your plan allows.
New Record
Polling triggerIn Zapier“Triggers when a new record is created.”
This one starts a Zap whenever a fresh entry appears in the ServiceNow table you choose. Each new record arrives with its fields, ready to be mapped into the next step.
Updated Record
Polling triggerIn Zapier“Triggers when an existing record is updated.”
Rather than waiting for something new, this trigger reacts when an existing ServiceNow record changes in the table you selected, and hands the record as it now stands to the following steps.
ServiceNow actions
ServiceNow gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Attach a File to a Record
ActionIn Zapier“Uploads and attaches a file to a record.”
Uploads a file and pins it to a record in the table you choose, so the document sits right where people will look for it.
Create Record
ActionIn Zapier“Creates a new record in a table.”
Adds a brand new entry to a ServiceNow table, filled with values coming from earlier steps.
Update Record
ActionIn Zapier“Updates an existing record in a table.”
Changes the values of a record that already lives in a ServiceNow table.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
An advanced escape hatch: it sends a raw request to ServiceNow, reusing the sign-in of your connection, for anything the menu does not offer.
ServiceNow searches
2 search steps look for data that already exists in ServiceNow, so a later step can use it.
A search step does not change anything. It finds a record or a file that already exists, so later steps can use it. In the action list, searches sit at the bottom under SEARCH. Three settings decide what happens next.
Find File
SearchIn Zapier“Finds a file by name.”
Looks up a file stored in ServiceNow by its name, and returns it for the steps that follow.
Find Record
SearchFind or createIn Zapier“Finds a record in a table.”
Locates an existing record in the table you pick, which is how a Zap finds the ticket it should update. The editor also lists Find or Create Record: that is this same search with the creation box ticked, not a separate step.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Switched on, the Zap continues empty-handed.
- Create Record if it doesn't exist yet?Ticking this box turns Find Record into a find-or-create. The setting above disappears and Zapier asks for the fields needed to create the missing record.
- If multiple search results are found?Three exits when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When a ServiceNow Zap breaks
Most failures here come from rights, tables and timing, not from Zapier itself.
Zapier lists a help article on the administrator prerequisites for a ServiceNow connection: read it with whoever runs your instance before the first Zap. The cases below cover the general limits that apply to every Zap. Our Zapier troubleshooting page goes further when a run fails.
Admin prerequisites skipped
Zapier publishes a dedicated article on what a ServiceNow administrator must set up before the connection works. If sign-in fails, start there with your admin.Old records never arrive
A Zap only reacts to what happens after you publish it. Records already in the table stay where they are, and moving that backlog is a separate job.The Zap keeps restarting itself
Updated Record watching a table that the same Zap updates will set itself off again and again, and burn through your tasks quickly.A bulk import gets held back
When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.
Need help automating ServiceNow with Zapier?
A person reads every message.



