Integrating conversations in Admin Center

Note: You must have a Zendesk Suite Professional plan or above to create conversations integrations. Learn about Sunshine Conversations pricing or Contact Sales for more information.

Conversations integrations help businesses unify messages from every channel, chatbot, or third-party app into a single conversation and build interactive experiences everywhere.

Conversations integrations are a bidirectional interaction between your business and Sunshine Conversations. The integration consists of:

• A webhook.
• (optional) A set of API keys to interact with the public API with a scope of integration. For information on creating the API keys, see Using Conversations API keys.

You can create conversations integrations through the Conversations Integrations page in Admin Center.

You can also create your integration using curl or Postman.

This article includes the following sections:

• Creating and configuring conversations in Admin Center
• Other integration methods

Creating and configuring conversations in Admin Center

From the Conversations Integrations page, you can:

• Create a new integration
• Add an API key
• View, edit, or delete an integration

Creating a new conversation integration

To create a conversations integration in Admin Center

1. In Admin Center, click Apps and integrations in the sidebar, then select Integrations > Conversations. The Conversations Integrations page opens. Any previously-created conversations appear in the list.

   If this is your first time creating an integration in Admin Center, click Create integration to view the Conversations Integrations page.

2. Click Create integration. The Create Integration page opens.
3. Enter a unique name to identify the integration.
4. In the Webhook section, enter the following information:
   • Webhook endpoint URL: The target URL. When a trigger event occurs, the webhook sees the event and sends the data to the target URL. The target URL uses the following format: https://www.yourdomain.com/path.
   • Webhook body data: Use the checkboxes to indicate whether you want to include the user schema and client and device information in the webhook data.
   • Webhook subscriptions: Select the events that you want to be notified on.
5. Click Save. The Copy shared secret window opens.
6. (Optional) Copy the Webhook ID and Shared secret. These are used by developers to add another layer of authentication and are not required.
7. Click Next. The integration’s configuration page opens. From here you can add an API key, if necessary.

Adding an API key

On the API key tab, you can configure authentication for the integration. An API key identifies and authenticates an application or user and is composed of three pieces:

• The App ID identifies your Zendesk account.
• The Key ID when used together with the secret key are the credentials used to authenticate JWTs and API calls.
• The secret key is the authentication password.

Note: API keys configured in the Conversations Integrations edit page are for custom integrations. They are scoped to a specific custom integration and cannot modify other integrations. For app-level API keys, see the Sunshine Conversations Authentication page.

To create and share an API key

1. In Admin Center, click Apps and integrations in the sidebar, then select Integrations > Conversations. The Conversations Integrations page opens.
2. Click the API key tab.
3. Click Create API key. If you are creating your first key, this button appears at the bottom of the page; if you have previously created a key, it appears in the top-right corner.
4. Enter an identifying name for the key in the Create new key dialog, then click Next.
5. In the Copy shared secret dialog, click Copy for each ID and secret key to save it to your clipboard, then click Next. You're returned to the API window, where the new key appears in the list.

If you generate a new key but have reached your 10-key limit, a notification appears, asking you to delete any unused keys.

To delete an unused key

1. In Admin Center, click Apps and integrations in the sidebar, then select Integrations > Conversations.
2. Click the API key tab.
3. Hover your mouse pointer over the key you want to delete, then click the options menu () and select Delete.

Confirm the action by clicking Delete.

Viewing, editing, or deleting an integration

To work with an existing integration

1. In Admin Center, click Apps and integrations in the sidebar, then select Integrations > Conversations. The Conversations Integrations page opens.
2. Hover over the integration you want to update and click the Options icon (), then select an option:
   • View details: Displays the integration's details page, where you can view the App, Integration, and Webhook IDs, as well as information on shared secrets, webhook details, and API keys.
   • Edit: Opens the Create Integrations page, where you can update the integration's name and webhook details.
   • Delete: Launches a deletion wizard. You can cancel and exit the wizard at any time.

Other integration methods

These methods are available only to users with a separate Sunshine Conversations license, not the license that comes with Zendesk Suite Professional or above.

To create a conversations integration using curl

1. Create an integration using the Create Integration API and set type to custom.
2. Provide the necessary parameters as specified in the API. The target is the URL of your server and the list of triggers determines which events to receive.

To create a conversations integration using Postman

1. Create an integration using the Create Integration API and set type to custom.
2. Download and install the Postman application.
3. Download the Sunshine Conversations Postman collection and set up your environment.
4. In Postman, select Smooch > Integrations > Create Integrations.
5. Provide the necessary parameters as specified by your integration type.

For more information on the Sunshine Conversations APIs, see Integrations.

Also see the guides on sending and receiving messages. You will want to configure webhooks using REST APIs.