Skip to main content
This is an updated and improved version of the Zendesk connector!If you’re setting up Zendesk with C1 for the first time, you’re in the right place.

Capabilities

The Zendesk connector supports automatic account provisioning and deprovisioning.
Role provisioning scope. Granting and revoking custom roles (Enterprise plan) is fully supported and switches a user between Zendesk custom roles. Revoke clears the user’s custom role and reverts them to the base agent role. The built-in agent and admin role entitlements cannot be revoked directly — to downgrade a user, assign them a lower role instead.
Organization entitlements. Every organization exposes the same agent and admin access-level entitlements. These are defined once as shared templates rather than per organization, so an entitlement appears as e.g. Organization Admin instead of being prefixed with each organization’s name. This lets the connector scale to tenants with very large numbers of organizations without a per-organization entitlement fetch.
Account entitlements. Accounts carry no entitlements of their own — a user’s organization access is expressed as grants against Organizations. When Organizations are excluded from the sync, the connector skips the account grant pass as well, since the organizations those grants point at wouldn’t be present.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

External ticketing

C1 can create and track Zendesk tickets as part of access request workflows (external ticket provisioning). To enable this capability, turn on Enable external ticket provisioning in the connector’s settings, or pass --ticketing to a self-hosted connector.
  • Each active Zendesk ticket form is exposed as a ticket schema containing that form’s active custom fields, plus Priority and Type selectors.
  • On Zendesk plans without ticket forms support, a single default schema containing all active custom fields is used instead.
  • A ticket is considered complete when its status reaches solved or closed.
Ticketing limitations. Number-type (integer and decimal) custom fields are not exposed as schema fields, and Zendesk custom ticket statuses are not supported — the six system statuses are used. The credential must be able to read ticket fields and ticket forms and create and read tickets.

Gather Zendesk credentials

Configuring the connector requires you to pass in credentials generated in Zendesk. Gather these credentials before you move on. The connector can authenticate with Zendesk in two ways:
  • OAuth client credentials (recommended): you create an OAuth client in Zendesk and give C1 its identifier and secret. C1 then obtains and renews access automatically.
  • API token (deprecated): Zendesk is retiring API tokens. Use this option only for existing connections until you switch to OAuth.
Zendesk is removing API tokens. Accounts created on or after July 28, 2026 can’t create or use API tokens. From October 27, 2026, no Zendesk account can create new API tokens. On April 30, 2027, all remaining API tokens stop working. Set up new connections with OAuth client credentials, and switch existing connections before April 30, 2027.
A user with System Admin access and the permission to create and delete users in Zendesk must perform this task.

Locate the subdomain for your Zendesk account

1
In your Zendesk account, navigate to the Admin page by clicking the gear icon in the left menu bar.
2
Locate your Zendesk subdomain in the top right corner of the page. Your subdomain is whatever precedes zendesk.com.
3
Make a note of your subdomain.
Zendesk records every change C1 makes (such as user, membership, and ticket updates) as made by the admin who created the OAuth client, and the connector has the same permissions as that admin. If that admin loses their admin role or is deactivated, the connector stops working. We recommend creating the client from a dedicated admin account that won’t be deprovisioned.
The scopes you allow on the OAuth client decide what C1 can do in Zendesk. Choose one of these access levels:
Use the same scopes in the connector’s OAuth Scopes setting when you configure it below. If the connector asks for scopes the OAuth client doesn’t allow, Zendesk rejects the connection.
1
Log in to your Zendesk account at yoursubdomain.zendesk.com as an admin, then go to the Admin Center module.
2
On the left sidebar click on Apps and integrations > APIs > OAuth clients and click Add OAuth client.
3
Enter a Name and Description (for example, “C1 Integration”), and set Client kind to Confidential.If the form asks for a redirect URL, enter any HTTPS URL your organization controls. The connector doesn’t use it.
4
If the form lets you choose which scopes the client can use, allow read for read-only access, or read and write for read and write access.
5
Copy the value in the Identifier field. This is your OAuth client ID.
6
Click Save, then copy the Secret right away. Zendesk shows it only once.

Option 2 (deprecated): Create an API token

1
Log in to your Zendesk account at yoursubdomain.zendesk.com, then click the gear icon (⚙️) in the left sidebar and click Go to Admin Center.
2
Navigate to Apps and integrations > APIs > API configuration.
3
Make sure both Token Access and Password Access are toggled on.
Password Access is required to list group memberships. Without it, the connector will return authentication errors when syncing groups.
4
Navigate to Apps and integrations > APIs > API tokens and click Add API token.
5
Optionally add a description, then copy the token immediately — it won’t be shown again.
6
Click Save.
Done. Next, move on to the connector configuration instructions.

Configure the Zendesk connector

To complete this task, you’ll need:
  • The Connector Administrator or Super Administrator role in C1
  • Access to the set of Zendesk credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Zendesk v2 and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
In the Subdomain field, enter the subdomain.
9
Choose how the connector authenticates with Zendesk:
  • OAuth client credentials (recommended): paste the client identifier into the OAuth Client ID field and the secret into the OAuth Client Secret field. In OAuth Scopes, enter the same scopes you allowed on the OAuth client: read for read-only access, or read and write (the default) for read and write access.
  • API token (deprecated): in the Email field, enter the email address associated with your System Admin account in Zendesk, then paste the token into the API Token field.
10
Optional. Enter a comma-separated list of the organizations you want to sync in the Organizations field. If this field is left blank C1 will sync all available organizations.
11
Click Save.
12
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your Zendesk connector is now pulling access data into C1.