---
sourceDocument: Australia Sales Customer Relationship Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/order-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# ServiceNow Quote Experience Integrations

# ServiceNow Quote Experience Integrations {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of ServiceNow Quote Experience Integrations

ServiceNow Quote Experience Integrations enable administrators to connect ServiceNow Quote Experience with third-party systems such as Salesforce.
These integrations facilitate data exchange by allowing ServiceNow to extract data from external sources or send data to them.
This capability helps streamline quoting processes by integrating external information directly into ServiceNow Quote Experience.
Show full answer Show less  

## Creating Connections

Before defining an integration, an admin must create a connection to the third-party environment via the Admin UI's Utilities section. Connections specify how ServiceNow communicates with external systems. Administrators choose the integration type---either Salesforce or External---and configure authentication accordingly:

* **Salesforce connections:** Require no additional fields since ServiceNow CPQ has built-in authentication and endpoint knowledge.
* **External connections:** Support authentication methods including None, Bearer Token, or OAuth, with relevant credentials such as tokens or client secrets provided.

Connection setup includes specifying the target host URL, endpoint path, and any additional headers needed for successful communication.

## Defining Integrations

After creating a connection, admins add new integrations to specify how data is exchanged. Key configuration settings include:

* **HTTP Method:** Select appropriate HTTP operations like GET, POST, PATCH, PUT, or DELETE based on the endpoint's requirements.
* **Line Item Details:** Define which line items are included---selected, modified, or deleted.
* **Additional Path:** Specify query commands such as SOQL for Salesforce or SQL-like queries for other platforms.
* **Timeout and Async:** Set request timeout and choose whether queries run asynchronously to avoid blocking user activity.
* **Headers:** Configure static or dynamic headers using handlebars syntax to customize requests.
* **Connection Selection:** Choose from previously created connections to link the integration to the correct third-party environment.
* **Transformation Template:** Map data between ServiceNow CPQ and external fields using JSON formatted templates with Mustache syntax, enabling precise data extraction and insertion.

## Testing and Troubleshooting

Admins can test integrations by pasting sample response data into ServiceNow's Sample Response Data area and running the transformation template. This process helps verify that data mappings work correctly and facilitates troubleshooting when integrations do not behave as expected.  
Use integrations to exchange data with third-party sources, including Salesforce.
To gather information from external sources like Salesforce, admins create integrations. These integrations define how to connect to a data source, extract information, and map it into ServiceNow Quote Experience. Integrations can also send data from ServiceNow Quote Experience to be mapped in a third-party environment

Before an integration can be defined for ServiceNow Quote Experience, the admin must first create a connection to the third-party environment, much like an external connection in the configuration environment. Connections are defined in the Utilities section of the
Admin UI.

## Creating a connection {#transaction-manager-integrations__Creating-a-Connection}

Before an integration is defined, the admin must define a connection to the third-party source for the data the integration uses.

To create a new connection, in the Utilities area of the Admin UI, click Connections. Then click + New to display the New Connection page.

On the New Connection page, name the new connection and assign a variable name. Next, choose the integration type: Salesforce or External.

If you are creating a connection to Salesforce, none of the other fields are required. ServiceNow CPQ knows how to authenticate and knows the required endpoints to use when communicating with Salesforce.

If you are creating an external integration, choose the authentication type. Supported authentication methods are None, Bearer Token, and OAuth. If you choose Bearer Token, use the Authentication Token field to provide the bearer
token for the site with which you are communicating. If you choose OAuth, use the Client ID, Client Secret, and Token URL fields to provide the required OAuth information.

In the Host field, enter the URL to the third-party site with which you will be communicating.

In the Path field, enter the path to the endpoint that you are trying to access on the third-party site.

Use the Additional Headers field to add any additional header information that is required by the third-party site in order to execute the desired endpoint.

## Creating an integration {#transaction-manager-integrations__Creating-an-Integration}

To create a new integration, click + Add Integration. The New Integration window appears. Give the new Integration a name and a variable name, and click Save.

The Integration Editor page opens. Continue defining the new integration by configuring the following settings:

* HTTP Method: You can perform either a GET, POST, PATCH, PUT, or DELETE operation, depending on the endpoint that you are using on the third-party site.
* Line Item Details to Include: Define which type of line items you will work with in the integration. Options are Selected Lines, Modified Lines, and Deleted Lines.
* Additional Path: Enter the query command to execute on the third-party site. If you are connecting to Salesforce, this will probably be a SOQL query. On other platforms, it may be a standard SQL query.
* Timeout: Defines the amount of time (in milliseconds) that the request will wait for a response before declaring an error.
* Async: This toggle allows you to run the query asynchronously in the background so that the user can continue working.
* Headers: You can use static text in header-level ServiceNow Quote Experience fields by using simple handlebar syntax, you can set key-value pairs for headers, or you can combine both these methods.`{{txn.fieldname}}`

{#transaction-manager-integrations__ul_hb1_y1d_hhc}


Next, you need to define the connection to the endpoint. Here you choose from a list of the connections that you previously created in the Utilities area to define which third-party site to connect to for this integration.

Finally, you need to define the transformation template, which lets you map third-party data to ServiceNow CPQ fields or map ServiceNow CPQ data to third-party data source fields.

JSON is used to define the mapping, as in the following example.

    {
      "fields": [
        {
          "variableName": "txn.custom.tXNNumber",
          "value": "{{#each records}}{{Name}}{{/each}}"
        },
        {
          "variableName": "txn.opportunity.id",
          "value": "{{#eachrecords}}{{LGK__OpportunityId__c}} {{/each}}"
        },
        {
          "variableName": "txn.custom.primaryContact",
          "value": "{{#eachrecords}}{{Contact.FirstName}}{{/each}}"
        }
      ]
    }

This example uses Mustache syntax for the Salesforce data that was extracted from the Salesforce site. Each field mapping includes the variable name of the ServiceNow CPQ field that receives the extracted data, followed by the value that identifies the Salesforce field where the data was extracted. The `#eachredords` and `/each` nomenclature
denote that each record in the query response is searched for each of the three field values in the template.

You can use the Sample Return Data area and the Transformation Result area to troubleshoot an Integration that is not working. If you perform the query in a tool like Postman, where you can see and copy the query response, you can
paste the query response in the Sample Response Data area and then click Run Transformation below the Transformation Template area. The query response data runs through the defined transformation template, and
the results of the Transformation is displayed in the Transformation Result area.