Use Connections Manager to create and authorize a Zendesk connection that Sprinklr modules can use (for example, External API, Unified Data Connector, or Knowledge Base).

Prerequisites

• Make sure you have the required permissions to create connections in Sprinklr.

• Confirm you know your Zendesk subdomain (for example, mycompany in https://mycompany.zendesk.com).

Step 1: Create the Connection

1. From the Sprinklr Launchpad, open Connections Manager.

2. Select + Create Connection (top-right).

3. On the Select Connection Type screen, select Zendesk.

You are redirected to the Zendesk Connection Details page.

Step 2: Enter Connection Details

On the Zendesk Connection Details page, configure the following fields:

• Connection Name: Enter a unique, descriptive name (for example, Zendesk – Support Prod).

• Description (optional): Add a short description of the connection purpose (for example, “Used for UDC case imports and KB sync”).

• Module Types: Select the Sprinklr modules that will use this Zendesk connection. This selection determines which permissions (scopes) may be required.

  Supported values:

  • External API

  • Unified Data Connector

  • Knowledge Base

• Scopes: Scopes define the permissions required for the selected modules to integrate with Zendesk.

  • The system populates scopes based on the Module Types you select.

  • You can edit scopes to match your integration requirements.

• Sub Domain: Enter your Zendesk subdomain to enable authorization (for example, mycompany).

Select Save.

After the connection is validated, you are redirected to the User Configuration screen.

Step 3: Add a Zendesk User (Authorize)

1. Select + Add User.

2. When redirected to your Zendesk instance, sign in with your Zendesk credentials.

3. Complete the authorization flow (if prompted).

After successful authorization, the user is linked to the Zendesk connection and the connection is ready for use by the selected module types.

Notes and Tips

• If your integration supports multiple environments (Dev/Test/Prod), create separate connections for each environment to avoid cross-environment access.

• If you change Module Types later, review and update Scopes to ensure required permissions are still granted.