Zendesk Support

Zendesk builds software for better customer service, bringing companies and their customers closer together.

Authentication methods

OAuth (User Created)

This method uses your own Zendesk App to authorize access, and is the most secure method since your own OAuth credentials are used.

You can create a OAuth client at: https://<your subdomain>.zendesk.com/admin/apps-integrations/apis/zendesk-api/oauth_clients

If you're unsure what value to set for the Redirect URLs, the following Snowflake query will construct it for your account: select 'https://'||parse_json(SYSTEM$ALLOWLIST())[0]:"host"::varchar||'/oauth/complete-secret' as REDIRECT_URL

The Unique Identifier and Secret are used in the Omnata connection creation as the Client ID and Client Secret respectively.

The Client kind must be set to "Confidential" as the credentials are securely stored in Snowflake, removing the need for PKCE.

Zendesk Plan for API Rate Limits

We will ask for your Zendesk product plan during the connection flow. This is because Zendesk apply rate-limits based on your plan and our Sync Engine will automatically throttle syncs to stay under these limits. You can always change or override these rate limits later.

You can find information on Zendesk API limits by plan on in their docs.

Inbound Syncs

The following are available as inbound streams:

• Tickets (Full Refresh or Incremental)

• Organizations (Full Refresh or Incremental)

• Users (Full Refresh or Incremental)

• Groups (Full Refresh or Incremental)

• Group Memberships (Full Refresh or Incremental)

• Ticket Fields (Full Refresh)

• Ticket Events (Full Refresh or Incremental)

Outbound Syncs

Supported Targets

• Tickets

• Users

• Organizations

• Custom Objects

Supported Sync Strategies

• Create

• Upsert

• Mirror

• Delete

Zendesk allows Users and Organizations to be identified via an external ID, which means the Upsert and Mirror sync strategies can match up with already-existing records on the first sync.

Tickets do not support this, so during the first sync every record will create a new ticket, and subsequent changes to the same record will update that ticket.