Skip to main content
ServiceNow The ServiceNow app exposes the ServiceNow ITSM platform through its Table API. It can be consumed two ways: as a remote MCP server that Agent Factory agents call as tools, or as a Builder app whose instructions you call directly from DSUL. It covers incidents, change requests, problems, the service catalog, requests, attachments, users and groups — plus a generic table accessor for any other ServiceNow table. Authentication is a per-workspace credential resolved server-side: either Basic Auth (a ServiceNow user with the right roles) or an OAuth2 client (client_credentials grant). Agents are identified by the capability Scope context_id,agent_id,user_id; the credential is never passed through the agent.

ITSM Tickets

Create, read, update and transition incidents, change requests and problems with work notes and close codes.

Service Catalog

List and inspect catalog items, then order them with their variables — creating a request and request item.

Generic Table Access

Query any ServiceNow table with encoded queries, fetch records by sys_id, and compute aggregate statistics.

Who is this for?

This connector is used by three different roles. Jump to the section that matches yours — each one is self-contained.

Agent builder

You build agents in Agent Factory and want them to manage ServiceNow tickets. → Agent builder tab.

Platform admin

You run the platform and want to publish ServiceNow as a reusable capability. → Platform admin setup accordion below.

Workspace builder

You write Builder automations (DSUL) that call ServiceNow operations directly. → Workspace builder tab.

Prerequisites (ServiceNow side)

  • A ServiceNow instance — its URL has the form https://<instance>.service-now.com.
  • A credential, one of:
    • Basic Auth — a ServiceNow user (username + password) holding the roles needed for the tables you target.
    • OAuth2 client (client_credentials grant) — create an Application Registry in ServiceNow under System OAuth > Application Registry and note its Client ID / Client Secret.
  • The roles for the tables you intend to use: itil for incidents, change_manager for change requests, problem_manager for problems, sn_request_write for catalog requests, and a table-specific role for anything else. The generic table tools are ACL-filtered by the account’s effective roles.
Goal: ServiceNow is a per-workspace connector — each workspace pastes its own ServiceNow credential (see the Workspace builder tab), so there is no platform-wide credential to provision. The only optional platform task is to publish ServiceNow as a reusable capability in AI Governance so agent builders can enable it from the catalog instead of pasting a raw MCP endpoint.
There is no shared ServiceNow credential and no central OAuth client for this connector. The ServiceNow instance URL and credentials (Basic or OAuth2) always live in the consuming workspace. A Governance capability you publish here points at a specific workspace’s MCP endpoint; that workspace still owns the credential.

Declare the capability in AI Governance (optional)

1

Open AI Governance > Capabilities

Create (or edit) the ServiceNow capability.
2

Point it at the MCP endpoint

Set the capability’s MCP server URL to the connector’s MCP Endpoint (the workspace running the connector), and set its Scope to:
The agent_id in the scope is what lets the connector identify the calling agent.
3

Make it available to agent builders

Once created, the capability appears in the capability picker for agent builders in your organization, who enable it on their agents. Access to the catalog follows your organization’s existing roles; there is no per-capability role grant.
Declaring the capability makes the connector available; it does not by itself authorize a specific agent against a ServiceNow instance. The ServiceNow credential is resolved server-side from the workspace running the connector, and ServiceNow ACLs (the account’s effective roles) are the final authorization boundary. There is no OAuth auth-config JSON to attach in Governance: authentication is a server-side Basic or client_credentials credential, not a per-user OAuth flow.

Agent builder

Goal: let an agent you build in Agent Factory manage ServiceNow tickets through MCP tools.
Before an agent can call the connector, a Workspace builder must have installed and configured the ServiceNow app in a workspace (see the Workspace builder tab). Optionally, a Platform admin may have published a ServiceNow capability in AI Governance (see the Platform admin setup accordion above).
The ServiceNow credential (Basic or OAuth2) is resolved server-side from the workspace’s app configuration — it is never exposed to the agent. Your agent is identified by the agent_id that Agent Factory injects through the capability Scope.
1

Install and configure the connector in a workspace

Follow the Workspace builder tab: install ServiceNow in a workspace, then fill in the instance URL and credentials (Basic or OAuth2).
2

Add the MCP capability to your agent

In your agent, add a capability pointing at the workspace’s MCP Endpoint URL, and set its Scope to:
The agent_id is what lets the connector identify your agent. The server URL is the connector’s MCP Endpoint, auto-populated when the app is installed.
3

Save

The agent now has access to every ServiceNow tool exposed by the MCP server.

Brief the agent in its system prompt

Wiring the capability is not enough — the agent also needs to know the tools exist and when to use them. Add a short paragraph to the agent’s system prompt. Copy-pasteable starter:
Refine the trigger keywords (assignment groups, ticket prefixes, catalog item names) so the agent reliably picks up the right intent in your context.
Legacy AI Knowledge agents (no native MCP picker): add the connector under Advanced > Tools > MCP and paste the MCP Endpoint URL. The agent’s identity is still propagated so the connector can read its agent_id.

Available Tools

Generic Table Access

Incidents

Change Requests

Problems

Service Catalog

Requests & Request Items

Attachments, Users & Groups

Output Formats

Tools return the underlying ServiceNow Table API JSON. Most list and get operations accept a displayValue argument that controls how reference and choice fields are rendered:
  • false — raw sys_id values (the default for most fields).
  • true — human-readable labels.
  • all — both, under value and display_value.
List operations also accept limit, offset and fields (comma-separated) to control the response size and shape.

Tool Details

queryRecords

Query any ServiceNow table using the encoded query syntax.

createIncident

updateIncident

transitionChange

Call getChangeTransitions first to discover which target states are legal for a given change, then transition:

orderCatalogItem

uploadAttachment

Max attachment size is set by the instance (default 1 GB via com.glide.attachment.max_size, but most instances restrict it further).

Error Handling

Common Issues

“ServiceNow not configured”instanceUrl is missing from the app config. Paste the full URL with scheme (https://acme.service-now.com). “Basic Auth requires username and password”authType is basic but one credential is empty. Either fill both or switch to oauth2. “OAuth2 requires clientId and clientSecret”authType is oauth2 but the client credentials are missing. Create an Application Registry in ServiceNow (System OAuth > Application Registry) with the client_credentials grant and paste its Client ID / Client Secret. Empty results with a seemingly valid query — encoded queries are case-sensitive and ACL-filtered. Try displayValue: all and verify the effective roles of the account; a record outside the account’s domain is silently excluded.

External Resources

ServiceNow Table API

Official Table API reference

Encoded Query Strings

Operators and syntax for the query argument

OAuth Inbound Setup

Create an OAuth Application Registry

Tool Agents

Learn how Agent Factory agents consume MCP tools in Prisme.ai.