Third-party data integration for CSM

  • Release version: Zurich
  • Updated July 31, 2025
  • 3 minutes to read
    • Summarize
    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 Third-party data integration for CSM

    The third-party data integration feature in Customer Service Management (CSM) enables agents to retrieve and view data from external applications directly within Agent Workspace, without storing that data in the ServiceNow instance. This integration addresses the challenge of fragmented agent experiences caused by the use of multiple systems, enhancing agent productivity and reducing customer wait times.

    Show full answer Show less

    A common use case is integrating ServiceNow with Salesforce, where Salesforce manages pre-sales activities and ServiceNow handles post-sales service assurance. This integration allows agents to access real-time Salesforce data, such as customer opportunities, directly in Agent Workspace to gain a complete customer context.

    Key Features

    • Real-time data retrieval: Uses remote tables to fetch and display third-party data on demand, keeping information current without storing it locally.
    • Seamless user interface: Agents can view third-party data in lists, forms, pop-up windows, sub-tabs, and related items using iframes within Agent Workspace.
    • Direct linking: Enables opening of third-party application records through links in ServiceNow forms.
    • Domain separation: Remote table script definitions respect domain separation, restricting data access based on user domain permissions.

    Activation and Configuration

    To enable this integration, the following plugins are required:

    • Remote Tables (for in-memory storage of third-party data)
    • OAuth 2.0 (for secure JWT Bearer grant type authentication)
    • IntegrationHub (for building reusable integrations and calling third-party APIs; requires appropriate subscription)
    • Customer Service plugin

    System administrators configure the integration by:

    • Setting up OAuth 2.0 JWT Bearer authentication between ServiceNow and the third-party system.
    • Creating aliases to manage connection credentials securely.
    • Defining remote tables and script definitions to map external data into ServiceNow.
    • Configuring access controls (ACLs) to secure data visibility.
    • Customizing lists and forms to present third-party data effectively in Agent Workspace.

    Benefits for ServiceNow Customers

    • Improves agent efficiency by consolidating customer data from multiple systems into a single workspace.
    • Provides real-time, read-only access to external data, eliminating data duplication and synchronization issues.
    • Supports integration with widely used enterprise systems like Salesforce, helping bridge pre- and post-sales workflows.
    • Maintains security and compliance through domain separation and controlled access.

    The third-party data integration feature enables you to retrieve data from third-party applications and display the data in Agent Workspace for CSM without having to store it in your ServiceNow instance.

    Many enterprise customers use ServiceNow applications as part of their IT ecosystems. In these environments, ServiceNow applications coexist with other applications and exchange data through different types of integrations. For customer service agents who typically use a wide variety of applications, this can create a fragmented experience that impacts agent productivity and increases customer wait time.

    A frequent integration takes place between ServiceNow and Salesforce applications. In this integration, customers use Salesforce to manage pre-sales activities and ServiceNow to manage post-sales activities. These post-sales activities represent service assurance.

    To provide high quality service, agents using the Customer Service Management (CSM) application need a complete understanding of the customer's context, and this includes access to customer data maintained in other systems. A common example of this integration is enriching a CSM customer profile by providing a list of opportunities related to the customer's account. These opportunities are retrieved from Salesforce in real time and are presented in Agent Workspace for CSM.

    Using the third-party data integration feature, data from third-party applications can be retrieved as needed. Agents can view the data in lists and forms. This feature uses remote tables to store the third-party data in memory on the application server. Remote tables are useful for data that changes frequently because the data is retrieved in real-time when a user accesses the data from the ServiceNow AI Platform.

    Activating third-party data integration

    The following plugins are required to implement third-party data integration:
    • Remote Tables (com.glide.script.vtable): Adds the Remote Table Script Definition table (sys_script_vtable) and adds the Remote Table flag to the Tables (sys_db_object) table. Active on the base instance.
    • OAuth 2.0 (com.snc.platform.security.oauth): Adds the OAuth-related tables and extension points needed to support OAuth 2.0 –JWT Bearer grant type. Active on the base instance.
    • IntegrationHub (com.glide.hub.integrations): Provides the ability to build reusable integrations with third-party systems and call them from anywhere in the platform. IntegrationHub requires subscription and is available in several subscription packages. Different packages allow for different levels of automation and provide different subsets of predefined third-party integrations, or spokes. For more information, see Request IntegrationHub and IntegrationHub available spokes.
    • Customer Service (com.sn_customerservice)

    Configuring third-party data integration

    Users with the system administrator role can configure the necessary components to enable third-party data integration for Agent Workspace for CSM. At a high level, the configuration steps include:
    • Setting up the OAuth 2.0 – JWT Bearer grant type, which provides the connection between the ServiceNow instance and the third-party application.
    • Setting up aliases to manage connection information and credentials when integrating with external systems and providing alias reference to the IntegrationHub action.
    • Creating a remote table to store the third-party data.
    • Creating a remote table script definition that maps the data from the third-party application table to the remote table.
    • Configuring ACLs for the remote table to provide user access to the third-party data.
    • Configuring the lists and forms that display data from the remote table.
    For more information, see Configure third-party data integration for CSM.

    Using third-party data integration

    Within Agent Workspace for CSM, agents can use this feature to:
    • View read-only data from third-party applications in lists and forms.
    • View data from multiple third-party applications in one browser tab.
    • View data from third-party applications in pop-up windows, sub tabs, and related items using iframes.
    • Open links to third-party application records from forms.

    Domain separation

    Remote table script definitions are domain separated. If users do not have access to the same domain as the remote table script definition record, they cannot access records from the remote table specified in the script definition.

    The data within the remote table is not domain separated.

    For more information, see Domain separation and remote tables.

    Related documentation