Resources · n8n integration

ServiceNow n8n integrationAutomate ServiceNow with n8n.

Every incident, user and table record in your instance can be driven from a workflow. The ServiceNow n8n integration ships 25 operations spread over 10 resources, and the catalog holds no trigger node, so the run starts elsewhere. Written for service desk and ops teams who already live in n8n.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the ServiceNow n8n integration actually do?

It links a ServiceNow instance to an n8n workflow through one credential, then puts the platform on the canvas as 25 operations grouped into 10 resources. You open, read, change and remove incidents, users and table records, you pull reference lists such as departments or configuration items, and you move attachments in both directions. The node ships with n8n, so there is nothing to install and nothing extra to pay on the n8n side, on n8n Cloud or on a self-hosted instance.

Start at the service desk. A message posted in Slack or a row dropped by a form becomes a ticket through incident.create, with Short Description filled from the message text and the rest of the ticket set through Additional Fields. An expression, meaning a short snippet in double braces that n8n evaluates while the workflow runs, carries the value across from the previous node.

Reporting is the second obvious job. Run incident.getAll with Return All switched on and n8n walks every page of the API rather than stopping at Limit, then the items land in Google Sheets for a weekly review. Filter takes an encoded query, and Field Names or IDs trims the payload down to the columns the report really needs.

People management is the third. A joiner arrives, user.create opens the account, user.update keeps it current when the department or the manager changes, and userGroup.getAll feeds the workflow the reference list it needs to route the rest. Teams that plan delivery in Jira Software often drive both sides from a single workflow.

The catalog stops at 25 operations across 10 resources. For anything outside it, the HTTP Request node calls any endpoint of the ServiceNow API and reuses the very same credential through predefined authentication, so you never leave the workflow. Worth knowing before you build: ServiceNow has no trigger node in n8n, a trigger being the node that starts a run. The workflow opens with a Schedule Trigger on a fixed interval, with the n8n Webhook node, a URL a third party calls, or with the trigger of another tool.

New to the platform? The n8n review lays out how it compares, and the n8n training takes it further.

Connect

How do you connect ServiceNow to n8n?

  1. 01

    Create the basic auth credential

    A credential in n8n is a saved set of connection details you create once under Credentials and reuse in every workflow. For basic auth, ServiceNow asks for three things: a User name, a Password, and a Subdomain. The subdomain sits inside the instance URL https://<subdomain>.service-now.com/. A developer account on the ServiceNow developer site is the prerequisite.

  2. 02

    Or register an OAuth2 app instead

    OAuth2 needs a Client ID, a Client Secret and the same Subdomain. Generate the first two in ServiceNow under System OAuth, then Application Registry, then New, then Create an OAuth API endpoint for external clients. Copy the Client ID into n8n, either type a Client Secret or leave it blank to have a random one generated, and paste the n8n OAuth Redirect URL into the app as a Redirect URL.

  3. 03

    Pick the credential, then the resource

    Drop the ServiceNow node onto the canvas and choose the saved credential from the dropdown. Next comes the resource, one of the 10 on offer, and then the operation inside it. A field marked required stops the node from running while it is empty, which is the fastest way to spot a missing Table Name or a missing record identifier before you ever hit Execute.

Actions

What can the ServiceNow node do?

The ServiceNow node exposes 25 operations across 10 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDeleteUpload
Attachment✓✓✓✓
Business Service✓
Configuration Item✓
Department✓
Dictionary✓
Incident✓✓✓✓✓
Table Record✓✓✓✓✓
User✓✓✓✓✓
User Group✓
User Role✓

Attachment

4 operations
01

Upload an attachment

attachment.upload

What you see in n8n

Notes & use cases

Pushes a binary file carried by the workflow onto a record that already exists, so a document built two nodes earlier ends up sitting on the right ticket.

Key parameters

  • Table Name or ID: chosen from the list, or set with an expression when the table varies per item.
  • Table Record ID: the sys_id of the record the file attaches to, commonly {{ $json.field }} from the node before.
  • Input Data Field Name: the name of the binary property that holds the data to upload.
  • File Name for the Attachment: optional, sets the name the attachment is given.
Use cases
a signed quote generated inside the run lands on the record that asked for it, instead of travelling by email.
02

Delete an attachment

attachment.delete

What you see in n8n

Notes & use cases

Removes one attachment from the instance, addressed by its own identifier rather than by the record it hangs on.

Key parameters

  • Attachment ID: the sys_id value of the attachment to delete, the single required field of the operation.
Use cases
a retention routine runs on a schedule, reads the attachments it needs to clear, and passes each identifier into this operation one item at a time. Pair it with an IF node upstream so only the files that match your rule reach the delete step.
03

Get an attachment

attachment.get

What you see in n8n

Notes & use cases

Reads a single attachment and, when you ask for it, brings the file itself back into the run as binary data.

Key parameters

  • Attachment ID: the sys_id value identifying the attachment.
  • Download Attachments: a required boolean that decides whether the file content comes along.
  • Output Field: the field name where the downloaded data is placed.
  • Filter: an encoded query string, written as <col_name><operator><value> and case-sensitive throughout.
Use cases
a screenshot left on a ticket is fetched and forwarded to a review tool without anyone opening the portal.
04

Get many attachments

attachment.getAll

What you see in n8n

Notes & use cases

Lists the attachments held on one table, with the option of downloading each file in the same pass.

Key parameters

  • Table Name or ID: the table whose attachments you want, from the list or via an expression.
  • Download Attachments: required boolean; combined with Output Field it decides where the binary data lands.
  • Return All: on, n8n walks every page; off, it stops at Limit.
  • Filter: an encoded query, and note that parameters here are case-sensitive.
Use cases
an audit run collects every file attached to a table over a period and archives the lot in one go.

Business Service

1 operation
05

Get many business services

businessService.getAll

What you see in n8n

Notes & use cases

Returns the business services declared in the instance, the reference list a workflow reads when it needs to know which service a request belongs to.

Key parameters

  • Return All and Limit: either the complete list or a capped slice of it.
  • Field Names or IDs: the columns to bring back, picked from the list or set as comma separated values in an expression.
  • Return Values: Actual Values, Display Values, or Both.
Use cases
a nightly sync keeps a lookup table fresh so later steps can resolve a service name without a human checking the portal.

Configuration Item

1 operation
06

Get many configuration items

configurationItems.getAll

What you see in n8n

Notes & use cases

Configuration items come back as workflow items, which makes this the entry point for anything built on the instance inventory.

Key parameters

  • Return All: switched on for a full inventory pass, left off with Limit for a quick sample.
  • Filter: an encoded query string that narrows the set before it reaches n8n.
  • Exclude Reference Link: on, the Table API links attached to reference fields are left out of the payload.
Use cases
a weekly reconciliation compares the inventory against an asset spreadsheet and flags what only exists on one side.

Department

1 operation
07

Get many departments

department.getAll

What you see in n8n

Notes & use cases

Pulls the department list so a workflow can route, group or label work by organizational unit rather than by a hardcoded string.

Key parameters

  • Limit: the maximum number of results when Return All stays off.
  • Field Names or IDs: a short list of columns keeps the run light when you only need names.
  • Return Values: pick Display Values when the output is headed for a human, Actual Values when it feeds another node.
Use cases
a monthly report groups closed work per department without anyone maintaining the list by hand.

Dictionary

1 operation
08

Get many dictionaries

dictionary.getAll

What you see in n8n

Notes & use cases

Dictionary entries describe the columns of the instance, which is what you read before writing to a table you did not design yourself.

Key parameters

  • Filter: an encoded query string, handy for narrowing to one area of the instance.
  • Field Names or IDs: the columns of the dictionary entry itself that you want back.
  • Return All: on, every page is fetched; off, Limit caps the output.
Use cases
before a bulk import, a check step reads the dictionary and confirms the field names the mapping is about to use.

Incident

5 operations
09

Create an incident

incident.create

What you see in n8n

Notes & use cases

Opens a new incident from whatever the workflow just received, whether that came from a form, a mailbox or another system.

Key parameters

  • Short Description: the short description of the incident, and the only required field.
  • Caller ID: the unique identifier of the caller, typically resolved a step earlier and passed as {{ $json.field }}.
  • Assignment Group Name or ID: the group the incident goes to; selecting one is what allows Assignee Name or ID to be set.
  • Impact and Urgency: each offers Low, Medium or High.
Use cases
a monitoring alert opens a ticket already routed to the right group, with Contact Type set to Email.
10

Delete an incident

incident.delete

What you see in n8n

Notes & use cases

Deletes the incident whose identifier you hand it, one item per execution.

Key parameters

  • Incident ID: the unique identifier of the incident, required, and the only field the operation asks for.
Use cases
cleaning up after a test campaign or after a faulty integration flooded the desk with duplicates. Put a filter node in front of it and feed only the identifiers you have checked, because there is no second confirmation once the node runs.
11

Get an incident

incident.get

What you see in n8n

Notes & use cases

Fetches one incident by identifier, which is the usual step between receiving a reference and deciding what to do with it.

Key parameters

  • Incident ID: the unique identifier of the incident, required.
  • Field Names or IDs: restricts the response to the columns you actually read.
  • Return Values: Display Values reads naturally in a message, Actual Values suits a comparison.
  • Exclude Reference Link: drops the Table API links on reference fields.
Use cases
a chat command answers with the current state of a ticket someone just mentioned by reference.
12

Get many incidents

incident.getAll

What you see in n8n

Notes & use cases

Queries several incidents in one node, which is how most reporting and escalation workflows begin.

Key parameters

  • Return All: on for a complete export, off to stop at Limit.
  • Filter: an encoded query string applied before the data leaves ServiceNow.
  • Field Names or IDs: the shortlist of columns to return.
  • Return Values: Actual Values, Display Values or Both.
Use cases
a Monday morning run collects the open backlog, groups it, and posts one digest instead of ten separate alerts.
13

Update an incident

incident.update

What you see in n8n

Notes & use cases

Writes new values onto an incident that already exists, leaving the fields you did not touch alone.

Key parameters

  • Incident ID: required, often {{ $json.field }} from a lookup step.
  • Update Fields: a collection of 16 entries, from State Name or ID to Close Notes.
  • Work Notes: work notes for the incident, the natural place for an automated comment, whether it records what the workflow did or what the requester answered.
  • On Hold Reason Name or ID: applies when the state is On Hold.
Use cases
a reply detected in a mailbox appends the message as work notes and moves the ticket forward.

Table Record

5 operations
14

Create a table record

tableRecord.create

What you see in n8n

Notes & use cases

Any table exposed by the instance can receive a new row here, which is the escape hatch when the object you work with is not one of the named resources.

Key parameters

  • Table Name or ID: required, chosen from the list or set with an expression.
  • Data to Send: Auto-Map Input Data to Columns when the input names already match the destination fields, Define Below for Each Column to set them yourself, or Nothing to send no column data.
  • Inputs to Ignore: comma separated input properties to leave out when auto-mapping.
Use cases
a custom request form writes straight into the table the team built for it.
15

Delete a table record

tableRecord.delete

What you see in n8n

Notes & use cases

Drops a single row from the table you name, addressed by the record identifier.

Key parameters

  • Table Name or ID: the table in which the record exists, from the list or via an expression.
  • Table Record ID: the unique identifier of the record, required, often {{ $json.field }} carried from a previous search.
Use cases
a housekeeping workflow clears rows a sync created in error, table by table, with the identifiers collected in the same run rather than typed in by hand.
16

Get a table record

tableRecord.get

What you see in n8n

Notes & use cases

Retrieves one row when the identifier is already known, without pulling the rest of the table along with it.

Key parameters

  • Table Name or ID: the table in which the record exists.
  • Table Record ID: the unique identifier of the record, required.
  • Field Names or IDs: keeps the response to the columns you read.
  • Exclude Reference Link: leaves out the Table API links on reference fields.
Use cases
an approval step re-reads the row just before acting, so the decision uses the current values rather than a stale copy.
17

Get many table records

tableRecord.getAll

What you see in n8n

Notes & use cases

Reads a slice of a table, or the whole of it, depending on how Return All is set.

Key parameters

  • Table Name or ID: required, the table to read.
  • Return All: on, n8n chains the API pages; off, Limit sets the maximum number of results.
  • Filter: an encoded query string that does the narrowing server side.
  • Return Values: Actual Values, Display Values or Both.
Use cases
a nightly export copies a custom table into a reporting sheet so analysts stop asking for access to the instance.
18

Update a table record

tableRecord.update

What you see in n8n

Notes & use cases

Edits a row in place on any table, with the same mapping choices as the create operation.

Key parameters

  • Table Name or ID and Table Record ID: both required, the second being the unique identifier of the record.
  • Data to Send: Auto-Map Input Data to Columns, Define Below for Each Column, or Nothing.
  • Fields to Send: the fixed collection where each destination column gets its value.
Use cases
an enrichment step adds the values found elsewhere back onto the row that was missing them.

User

5 operations
19

Create a user

user.create

What you see in n8n

Notes & use cases

Adds a user to the instance, with a collection of 24 optional fields covering identity, contact details and access.

Key parameters

  • Short Description: the short description of the user, and the only required field of the operation.
  • Username, First Name, Last Name, Email: the identity block most workflows fill.
  • Role Names or IDs: the roles of the user, from the list or as identifiers in an expression.
  • Password Needs Reset: requires a password reset when the user logs in.
Use cases
a new hire row in the HR system opens the account before the first day.
20

Delete a user

user.delete

What you see in n8n

Notes & use cases

Takes a user out of the instance, identified by nothing more than an identifier.

Key parameters

  • User ID: the unique identifier of the user, required.
Use cases
the tail end of an offboarding workflow, once the tickets have been reassigned and the manager has signed off. Keep the identifier from the lookup step in the same run rather than rebuilding it later, and gate the node behind an approval so a mistyped value never reaches it.
21

Get a user

user.get

What you see in n8n

Notes & use cases

Looks up one person, and unusually it lets you choose which key you search on.

Key parameters

  • Retrieve Identifier: required, set to ID or to Username.
  • User ID or Username: the value matching the choice above.
  • Field Names or IDs: the columns to return.
  • Return Values: Display Values for readable output, Actual Values for machine use.
Use cases
an intake workflow resolves the person who wrote in, using the username it already has, before it opens anything in their name.
22

Get many users

user.getAll

What you see in n8n

Notes & use cases

Walks the whole user directory, one workflow item per person.

Key parameters

  • Return All: on for the full directory, off to stop at Limit.
  • Filter: an encoded query string, the right place to narrow a large directory.
  • Field Names or IDs: a short column list keeps the payload sensible at scale.
  • Exclude Reference Link: removes the Table API links on reference fields.
Use cases
a quarterly access review needs the full picture, so it exports the directory in one pass and checks it against the identity provider by hand afterward.
23

Update a user

user.update

What you see in n8n

Notes & use cases

Changes what the instance knows about someone already recorded in it, one field or twenty at a time.

Key parameters

  • User ID: the unique identifier of the user, required.
  • Update Fields: the same collection of 24 entries offered at creation, so nothing has to be relearned between the two operations.
  • Department, Manager, Location: the three that move most often when someone changes team.
  • Active: whether the user is activated.
Use cases
an internal move updates department and manager the day the transfer takes effect, with no ticket in between.

User Group

1 operation
24

Get many user groups

userGroup.getAll

What you see in n8n

Notes & use cases

Before a workflow can route anything by team, it needs the group list, and that is exactly what comes back here.

Key parameters

  • Return All and Limit: the whole set, or a capped slice of it.
  • Filter: an encoded query string to keep only the groups you care about.
  • Field Names or IDs: the columns to return, as a list or an expression.
  • Return Values: Actual Values, Display Values or Both.
Use cases
a dispatch workflow refreshes its routing table each morning so a renamed group never breaks the assignment.

User Role

1 operation
25

Get many user roles

userRole.getAll

What you see in n8n

Notes & use cases

Pulling the role list into a workflow starts here: n8n returns the user roles from your ServiceNow instance, one role per item.

Key parameters

  • Return All: on, n8n pages through the API until every role is back; off, Limit caps how many arrive.
  • Filter: an encoded query string, meaning a condition written in ServiceNow syntax, that narrows what comes back.
  • Field Names or IDs: choose the fields to keep, from the list or with an expression, so each item stays small.
Use cases
refresh a reference list of roles every morning and store it, so a later node checks a value against that list instead of calling the API again.
Need help

Need help automating ServiceNow with n8n?

A person reads every message.

FAQ

ServiceNow and n8n, the questions that come next

01Is the ServiceNow n8n integration free?
Yes, on the n8n side. The ServiceNow node ships with n8n, so there is no plugin to install and no extra cost to add: it behaves the same on n8n Cloud, the hosted offer run by n8n, and on an instance you host yourself with Docker or npm under the Community Edition and its Sustainable Use licence. A workflow built in one place runs unchanged in the other. What your ServiceNow subscription itself costs is a separate question, and one this page does not answer, since it depends entirely on your own agreement with the vendor.
02What credentials do you need to connect ServiceNow to n8n?
Two methods are supported: basic auth and OAuth2. Basic auth is the shorter path, asking only for a User name, a Password and a Subdomain, the label that sits inside the instance URL before service-now.com. OAuth2 asks for a Client ID, a Client Secret and the same Subdomain, and you generate the first two in ServiceNow under System OAuth, Application Registry, New, then Create an OAuth API endpoint for external clients. Paste the n8n OAuth Redirect URL into the app as a Redirect URL. Either way, a ServiceNow developer account is the prerequisite, and the credential is created once and reused everywhere.
03What are the limits of the ServiceNow node in n8n?
The node exposes 25 operations across 10 resources. Anything outside that catalog is handled by the HTTP Request node, which calls any endpoint of the ServiceNow API and reuses the same credential through predefined authentication, so the workflow stays in one piece. The other thing to watch is pagination. On list operations, Return All chains the pages of the API until everything has come back, while leaving it off means Limit decides the maximum number of results. Large tables are exactly where the difference shows, so set that switch deliberately rather than by default.
04Can an n8n workflow react to a new ServiceNow incident?
Not directly, because ServiceNow has no trigger node in n8n. A trigger is the node that starts a run, and here it has to come from somewhere else. Three routes work. The Schedule Trigger fires on a fixed interval and a get many operation reads what changed since the last pass. The n8n Webhook node gives you a URL that a third party service calls, which starts the workflow the moment that call arrives. Or the trigger of another tool starts the run, and the ServiceNow node acts afterwards. The third option is what most service desk workflows end up using.
05n8n or Make for ServiceNow?
It depends on four things. Hosting first: Make is a hosted platform with no self-hosting option, while n8n runs on Cloud or on your own infrastructure. Data control follows from that, and it matters when incidents carry personal or internal information. Cost model next: Make bills per operation, which is worth modelling against your volumes before committing. Visual logic last, since both build workflows on a canvas but the way branching and iteration are expressed differs, and that shapes how quickly your team maintains what it builds. Try the same workflow on both and judge on those criteria.