ServiceNow connector
Connect ServiceNow to Enterpret Agent using an approved ServiceNow OAuth application and the account you intend Agent to use. Application setup and each user's authorization are separate steps.
| Who | What they do |
|---|---|
| ServiceNow administrator | Register and configure the approved public-client OAuth application for the intended instance, and check the account's roles and access controls. |
| First permitted Enterpret user connecting ServiceNow | Supply the instance subdomain and the administrator-provided Client ID, then authorize the intended ServiceNow account. |
| Later Enterpret users | Supply the instance subdomain and authorize their own approved account using the saved workspace client configuration. |
The saved Client ID is workspace configuration, while each connection belongs to the Enterpret user who creates it. Do not assume that one saved configuration supports multiple ServiceNow instances. Contact your Enterpret team before changing instances or replacing the workspace Client ID.
1. Prepare the ServiceNow application
A ServiceNow administrator should use the OAuth application setup supported by your instance's release. Follow ServiceNow's authorization-code application guide; navigation can differ between the Application Registry and newer administration screens.
Create or select an active authorization-code application approved for Enterpret. Configure it as a public client compatible with PKCE; use the public-client option documented for your ServiceNow release.
Register this exact redirect URL:
https://api-v2.enterpret.com/connectors/oauth/oauth/callback. Keep the repeated/oauth/segment.Review the requested
useraccountOAuth scope and the intended API access with your ServiceNow administrator. The current connector requests this scope; choosing a different scope set requires compatibility review.Copy the application's Client ID for the first connection in Enterpret.
Enterpret's ServiceNow setup requests a Client ID and uses the public-client authorization flow; it does not ask you to provide a ServiceNow client secret. Leaving a secret field blank is not a reliable way to establish that the application is configured as a public client. Follow the public-client settings for your release.
2. Check the account and permissions
Choose the ServiceNow account your organization authorizes for this work. A dedicated automation account is an organizational choice, not a prerequisite for every person connecting. The connector acts using the account authorized in ServiceNow.
Have your ServiceNow administrator check the roles and access controls needed for the intended tables and fields. Read access, incident creation, updates, custom fields, and allowed choice values can have different requirements. Verify the returned field values when testing an approved write workflow; successful authorization alone does not confirm write access.
Use your organization's approved sign-in method, including SSO where configured. You complete sign-in on ServiceNow's authorization page, rather than entering a ServiceNow username or password in Enterpret's connection form.
3. Connect in Enterpret
Open the Agent composer's + → Connectors menu and choose Manage connectors when needed to open the catalog.
Find ServiceNow and choose Connect.
For the instance, enter only its subdomain. If the URL is
https://acme.service-now.com, enteracme, without the protocol, domain suffix, or trailing slash.If Client ID is requested, use the administrator-provided ID for the approved application. Later connections normally reuse the saved workspace client configuration and only request the subdomain.
Choose Continue when offered. In ServiceNow, confirm the instance and signed-in account, then review and authorize the request.
Return to Enterpret and check the connection status and available tools. Discovery can continue after authorization. Follow any discovering, reconnect, or error message shown.
If Client ID appears again after setup, confirm the existing application with your administrator or Enterpret team. Do not create or replace an organization app just to make the form disappear.
4. Verify with a read-only task
Enable ServiceNow for your Enterpret user in the Connectors menu. This toggle affects your connector availability across Sessions and is not isolated to the current conversation.
Start with a read-only request, for example: “Find a ServiceNow incident I am allowed to read and show its number and short description. Do not create or update anything.” Review any approval prompt and confirm that the result comes from the intended instance and account.
The available tools depend on discovery and configuration; do not rely on a fixed tool count. Review Agent's permission mode and saved tool permissions before delegating a write action.
Troubleshoot authentication
Redirect mismatch: compare the registered URL with the exact callback above.
Client or scope error: ask your administrator to check the active public-client application, Client ID, requested scope, and instance compatibility.
Connected but tools are unavailable: check the discovery/status message and account access before treating authorization as complete setup.
Missing or unchanged fields: have the ServiceNow administrator check the relevant permissions, field definitions, and valid choice values.
For general setup and permission concepts, see Connectors. If you need help, share the instance subdomain, setup step, and error message with your Enterpret team; do not include passwords, client secrets, or tokens.
Use connectors with Enterpret Agent and automations
Use this connector with Enterpret Agent when your task needs external context or a supported action. For recurring reporting, daily reports, weekly digests, or scheduled follow-up work, attach an available connector to scheduled Agent automations and review the automation's own account access and tool permissions. Test the automation before enabling it; an interactive Session's approval does not automatically authorize unattended actions.