Sprinklr administrator prerequisites for Zapier connection

This guide is for Sprinklr administrators. This one-time setup is required before your users can connect Sprinklr to Zapier.

Prerequisites

• A Sprinklr account with API access. Sprinklr states that customers with Enterprise licenses are entitled to use its APIs. If you are not sure your license includes API access, check with your Sprinklr account team. For background, refer to Sprinklr's APIs overview.
• The Configure Developer Apps permission in Sprinklr, to create a Developer App in Developer Tools.

1. Create a Developer App for Zapier

1. Sign in to Sprinklr and go to Developer Tools.
2. Create a new Developer App for Zapier. Developer Apps created at legacy-dev.sprinklr.com are not synchronized with Developer Tools, so create the app here.

3. Set the app's callback URL to the following value. It must match exactly:

   https://zapier.com/dashboard/auth/oauth/return/App243474CLIAPI/

2. Generate an API key and secret

A Developer App can have several API keys. To generate one:

1. In Developer Tools, find your Developer App, click the vertical ellipsis, and select Manage API Key/Token.
2. Click + API Key.
3. Copy the API key and secret from the window that opens, then click Close. Sprinklr masks the secret afterward, so store it securely.

Repeat these steps for each Zapier connection that needs its own key. For more detail, refer to Sprinklr's Developer Tools guide and Sprinklr's API key and token guide.

Note

Sprinklr's guide states that only one token can exist per API key, and that generating a new token invalidates the previous token and refresh token for that key. Use a separate API key for each Zapier connection, and do not use that key in other tools. Otherwise they disconnect each other.

3. Choose the Sprinklr user who authorizes the connection

The user who signs in during the Zapier connection must have the Generate Token permission. Sprinklr recommends a service user, so the token is not tied to an individual who may leave your organization. Give that user access to every workspace Zapier should read.

4. Find your environment

Production accounts, which sign in at app.sprinklr.com, leave the Environment field blank in Zapier. For other accounts, open the page source of your Sprinklr account in your browser and search for sentry-environment. The value, for example prod0 or prod2, is your environment. An API key and token are environment-specific, so a key generated for one environment cannot be used in another.

Credentials for the Zapier connection

Each API key holds one active token, so each Zapier connection to Sprinklr needs its own API key and secret. Generating or refreshing a token for one key does not affect the token for another key, even in the same Developer App. Choose one of these approaches:

• One shared connection: One person connects Sprinklr to Zapier with one API key and secret, then shares the connection with teammates on a Team or Enterprise account. Only that person needs the API key and secret.
• One API key per connection: Generate a separate API key and secret in the Developer App for each person or team that needs its own connection.

Do not give the same API key and secret to several users who each create their own connection. Each new connection replaces the previous token for that key and disconnects the other connections.

Give the person who creates the connection these values:

• API Key
• API Secret
• Environment (leave blank for production)

Treat the API secret like a password. Share it only with the person who creates the connection, and use a secure method.

Additional Sprinklr resources

• Sprinklr's Developer Portal
• Sprinklr's API v3 overview
• Sprinklr's API key and token guide