At a glance
- Availability: Experimental (how to enable).
- Authentication: OAuth 2.0 (authorization code or client credentials); legacy bearer token.
- Connection: Choose delegated OAuth, application credentials, or a legacy pasted bearer token.
Credentials
Choose one Cloud access mode. Set the variables for that mode in the target project environment; the legacy bearer token is not required for OAuth.
Client credentials access requires the separate
SERVICENOW_SERVICE_ACCOUNT_ variables below.
Cloud access modes
Hosted Cloud tools support both user-delegated OAuth 2.0 authorization code access and application/service access using the OAuth 2.0 client credentials grant. These are separate credential configurations. The local Code runtime has its own supported authentication methods. For delegated access, setSERVICENOW_CLIENT_ID, SERVICENOW_CLIENT_SECRET and SERVICENOW_INSTANCE. The SERVICENOW_ACCESS_TOKEN credential above is required only for legacy pasted-token access, not for either OAuth grant. Set every application variable below for client credentials access.
Configure application access describes provider setup, identity selection, project tool policy and supported-operation restrictions.
Tools
Verify the connection
Call a read tool such asservicenow__list_incidents with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.