Skip to main content
Back to list of enterprise systems Use the ServiceNow integration to create, retrieve, update, and search records in ServiceNow tables, and to attach or find files. It also provides triggers for new or updated records.

Supported actions

Triggers

Prerequisites

  • A ServiceNow instance and an account with access to the tables and records your tools will use.
  • A ServiceNow domain and credentials for one of the authentication methods offered in Studio.

Set up the integration

1

Create a ServiceNow auth profile

In Tools, select New Tool > Action > ServiceNow > Continue > Manage profiles. On Project Auth Profiles, select New Profile > Integration Profile > ServiceNow > Continue. Choose an authentication type and enter the required credentials. For OAuth 2.0, Studio supplies the authorization and token endpoints, the useraccount scope, and a callback URL to register in ServiceNow.
2

Configure the action tool

Return to the action builder, select the ServiceNow action and auth profile, configure its inputs, and create the tool. Then assign the tool to an agent.

Action reference

The tables include required and optional inputs shown in the Studio action builder. Table and record dropdowns load values from the connected ServiceNow instance.
The table selector includes common tables such as Incident (incident), Change Request (change_request), Problem (problem), Service Request (sc_request), Requested Item (sc_req_item), Catalog Task (sc_task), Task (task), User (sys_user), Group (sys_user_group), Configuration Item (cmdb_ci), and Knowledge (kb_knowledge). It can also return other tables available in the connected instance.

Trigger reference

The optional filter uses a ServiceNow encoded query, for example: priority=1^state=1.
Triggers when a new record is created in a table
Triggers when a record is updated in a table
Find Records uses a default limit of 1,000 records. Large results may be trimmed to fit connector response limits.

File attachments

For Attach File to Record, provide either a file input or the fileBase64 parameter. The file input accepts a file from an earlier step, a link, or file content. Server file paths are not supported. If the file name or content type is omitted, the connector uses the file name and infers the content type when possible. For Find File, action_type selects whether to list attachments or download a file. You can optionally filter by file name or provide an attachment sys_id; the default accepted type is any file, and the default return format is a Base64 encoded string.

Troubleshoot common issues