--- title: Using external connections with OAuth support description: External connections allow enrichments to retrieve data from third-party systems to enhance configurations. When security requires OAuth, you can set up an OAuth handshake using client credentials to authenticate and access external APIs. This approach ensures secure data exchange for tasks such as pricing updates or attribute population during configuration. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/order-management/encrichments-external-connections-w-oauth-support.html release: australia topic_type: concept last_updated: "2026-09-10" reading_time_minutes: 3 breadcrumb: [ServiceNow CPQ Configurator, Configure, price, quote apps, Configure, Sales Customer Relationship Management] --- # Using external connections with OAuth support External connections allow enrichments to retrieve data from third-party systems to enhance configurations. When security requires OAuth, you can set up an OAuth handshake using client credentials to authenticate and access external APIs. This approach ensures secure data exchange for tasks such as pricing updates or attribute population during configuration. Enrichments are scripts that run outside the rules engine and affect configurations in ServiceNow CPQ. There are five types of enrichments that can be enabled in a ServiceNow CPQ environment: - On configure/reconfigure - On BOM response - Validation - Picklist extension pricing - On request External connections get data for a ServiceNow CPQ configuration from something outside ServiceNow CPQ. External connections can only be called from an enrichment. Occasionally, an external connection requires an OAuth handshake for security purposes. For example, you may need to populate a field or an enrichment script with data from a third-party application, such as pricing or other attributes. To set an OAuth external connection, follow these steps: 1. Define the external connection by visiting Admin > Utilities > External Connections. \[Omitted image "cpq-enrichments-external-connections.png"\] Alt text: External connections user interface 2. Define your authentication token. - If the external connection calls an open API, no authentication token is needed. - If the external connection is Salesforce, ServiceNow CPQ takes care of the authentication token for you. - If the authentication supports a bearer token, insert the bearer token provided by the external service for the purposes of authentication. - If the authentication requires OAuth authentication: 1. Select OAuth - Client Credentials Flow 2. Insert the client ID 3. Insert the client secret 4. Insert the token URL field Required OAuth inputs:
| Field | Type | Description | Validations |
|---|---|---|---|
| Client ID \(Required\) | varchar \(unlimited\) | Holds the client ID created for ServiceNow CPQ with the authorization server | Not empty |
| Client secret \(Required\) | varchar \(unlimited\) | Holds a tokenized reference to the client secret The actual value is stored in the GCP secret store, except in dev environments, where the value is stored directly | Not empty |
| Token URL \(Required\) | varchar \(unlimited\) | The URL of the authorization server to exchange the client ID/secret with for a token | Not empty |
| Scope \(Optional\) | varchar \(unlimited\) | Optional - can be used to specify the scopes sent with the token request | None |