ServiceNow
ServiceNow is an enterprise IT service management platform. The Willow connector calls the REST APIs on your own instance: the Table API for records, the Aggregate API for counts and totals, and the Attachment API for file metadata. An agent can triage incidents, review changes, look up knowledge articles and configuration items, and query any other table the connected user can read.
ServiceNow appears twice
ServiceNow shows up as two cards in the catalog:
- ServiceNow with a By Willow badge — this page. Willow's connector for the instance's REST APIs, with a fixed set of 36 tools.
- ServiceNow with an Official badge — ServiceNow's own MCP server, built into your instance (MCP Server Console, Zurich release and later). It needs an OAuth app created on the instance and the name of the MCP server to connect to.
| If you need | Use |
|---|---|
| Incident, problem, change, catalog, approval, knowledge, and CMDB tools without configuring anything in ServiceNow beyond an OAuth app or integration user | By Willow connector |
| Reads and writes on any table, plus counts and totals, through one set of generic tools | By Willow connector |
| ServiceNow's own MCP server and the tools it exposes | Official server |
Running both is fine.
Authentication
The default is OAuth, where each person connects with their own ServiceNow account. The connector also supports an API key, which is HTTP Basic authentication with an integration user's credentials. With either method, ServiceNow enforces the connected user's roles and access controls, so the agent can only reach what that user can.
OAuth
ServiceNow acts as the OAuth server. You register Willow as an external client in the instance, and each user then approves access from their own ServiceNow login. Willow uses the authorization code grant. The access token lasts 30 minutes by default and the refresh token 100 days, and Willow refreshes the access token automatically until the refresh token expires.
- Log in to your instance as a user with the
adminrole. - Go to All → System OAuth → Application Registry and click New.
- Click Create an OAuth API endpoint for external clients.
- Fill in the form:
- Name: for example
Willow. - Client Secret: leave blank to have the instance generate one.
- Redirect URL: copy it from the Willow setup step for this connector and paste it exactly as shown.
- Active: checked.
- Refresh Token Lifespan and Access Token Lifespan: the defaults are 8640000 seconds (100 days) and 1800 seconds (30 minutes).
- Name: for example
- Click Submit, then reopen the record and copy the Client ID and Client Secret. Click the lock icon next to the secret to reveal it.
Some releases also show a Client Type field with the options Iframe Embedded, Integration as a User, and Integration as a Service. ServiceNow describes them in Configure client type for OAuth and SSO records.
The connector sends the user to /oauth_auth.do on your instance and exchanges the code at /oauth_token.do. It requests no scopes. What a token can do is decided by the user's roles and ACLs.
API key (Basic authentication)
Use this when you want one shared integration user instead of per-person OAuth.
- In ServiceNow, go to User Administration → Users and create or choose an integration user. Make sure it is active.
- Give it the roles the tools need. ServiceNow's Table API requires the calling user to have sufficient roles for the table, for example
itilfor incident records. - In Willow, enter the credential as
username:password. Willow sends it asAuthorization: Basic <base64 of username:password>.
Everything the agent does is attributed to this user. Use a dedicated account with the fewest roles that work, not a personal or admin account.
Instance URL
The connector asks for your ServiceNow Instance URL, for example https://yourcompany.service-now.com. Enter the address without a trailing slash or any path after the host.
Configure in Willow
- In Willow, go to MCP Servers → + Add MCP server and find the ServiceNow card with the By Willow badge.
- Click + Use.
- Enter your ServiceNow Instance URL.
- Choose the authentication type:
- OAuth: paste the Client ID and Client Secret, save, then click Connect and approve access on the ServiceNow page. You must be logged in to the instance to approve.
- API Key: paste
username:password.
- To check the connection, run List Incidents with
limitset to1. A record, or an empty list on an instance with no incidents, means the URL and credentials work.
Available Tools
The connector has 36 tools. Most groups cover one area of ServiceNow. Any table works on tables that have no dedicated tool.
Incidents (5 tools)
- List Incidents — filter with an encoded query by state, priority, assignee, or number.
- Get Incident — read one incident by sys_id, including its description and resolution fields.
- Create Incident — open an incident with a short description, caller, category, impact and urgency, and assignment.
- Update Incident — change fields, reassign, or resolve an incident.
- Add Incident Comment — add a customer-visible comment or an internal work note.
Problems (4 tools)
- List Problems — filter problem records.
- Get Problem — read one problem by sys_id.
- Create Problem — open a problem record.
- Update Problem — change fields on a problem.
Change requests (4 tools)
- List Change Requests — filter by type, state, risk, planned dates, or number.
- Get Change Request — read one change with its justification and plans.
- Create Change Request — create a change with schedule and implementation, backout, and test plans.
- Update Change Request — change schedule, plans, assignee, or state.
Service catalog (4 tools)
- List Catalog Items — find items users can request.
- List Requested Items — list ordered items (RITMs) by requester, state, or number.
- List Catalog Tasks — list fulfillment tasks (SCTASKs).
- Update Catalog Task — assign, comment on, or close a catalog task.
Approvals (2 tools)
- List Approvals — find approvals waiting on a user or attached to a record.
- Update Approval — approve or reject. Willow rates this tool high risk because a decision can move a change or request forward.
Knowledge (3 tools)
- Search Knowledge Articles — search titles and bodies, published articles by default.
- Get Knowledge Article — read one article including its body.
- Create Knowledge Article — add an article to a knowledge base.
Users and groups (3 tools)
- List Users — find a user's sys_id for callers and assignees.
- List Groups — find an assignment group's sys_id.
- List Group Members — see which users belong to which groups.
Configuration items (2 tools)
- List Configuration Items — search the CMDB across all classes.
- Get Configuration Item — read one CI.
Any table (6 tools)
- List Table Records, Get Table Record, Create Table Record, Update Table Record — work with any table the user can access, including custom
u_*tables. - Delete Table Record — permanently delete a record.
- Get Table Stats — count records or sum, average, and take the minimum and maximum of fields, optionally grouped.
Attachments (3 tools)
- List Attachments — list file metadata, for example for one record.
- Get Attachment — read one attachment's metadata and download link.
- Delete Attachment — permanently delete an attachment.
The connector reads attachment metadata only. It does not upload or download file contents.
Filtering with encoded queries
The list tools take a query argument written in ServiceNow's encoded query syntax:
=,!=,LIKE,STARTSWITH, andENDSWITHcompare a field to a value.^joins conditions with AND, and^ORadds an alternative to the condition before it.ORDERBY<field>andORDERBYDESC<field>sort the results.
For example, active=true^priority=1^ORDERBYDESCopened_at returns open priority 1 records, newest first. Column names, operators, and values are case-sensitive.
List and get tools return display values by default, such as In Progress instead of 2 and a person's name instead of a sys_id. Set display_value to false to get raw values. When you create or update a record, reference fields such as assigned_to take a sys_id, which you can find with List Users or List Groups.
Troubleshooting
401 Unauthorized
Cause: The credentials are wrong or expired, or the integration user is inactive or locked out.
Solution:
- For OAuth, check that the Client ID and Client Secret match the Application Registry record and that the record is Active.
- If the refresh token has expired, disconnect and connect again. Refresh tokens last 100 days unless you changed Refresh Token Lifespan.
- For an API key, check the
username:passwordvalue and that the user is active in ServiceNow.
Redirect URL error when connecting
Cause: The Redirect URL in the Application Registry record does not match the one Willow uses.
Solution: Copy the redirect URL from the Willow setup step and paste it into the record's Redirect URL field exactly as shown.
403 Forbidden or an empty list
Cause: The connected user lacks the roles or access controls for the table or record.
Solution:
- Check the user's roles under User Administration → Users.
- Compare with what the same user sees in the ServiceNow UI. The connector can only return what that user can read.
- If a list comes back empty even though records exist, note that ServiceNow applies
limitbefore access controls. Add a more specificquery, or order the results so records the user can access come first.
404 on Get or Update
Cause: The sys_id does not exist in that table, or the user cannot access the record.
Solution: Use the 32-character sys_id, not the number such as INC0010001. To find a record from its number, run the list tool with query set to number=INC0010001.
A filter seems to be ignored
Cause: By default, ServiceNow drops invalid parts of a query, such as a misspelled field name, and returns rows for the rest.
Solution: Check field names and operators, which are case-sensitive. A property named glide.invalid_query.returns_no_rows makes the instance return no rows for invalid queries instead.
Instance URL not reachable
Cause: The Instance URL is wrong, has a trailing slash or a path, or the instance is offline.
Solution: Use the form https://yourcompany.service-now.com with no path, and check that you can open it in a browser.