Zendesk Support
Zendesk builds software for better customer service, bringing companies and their customers closer together.
Last updated
Zendesk builds software for better customer service, bringing companies and their customers closer together.
Last updated
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://'||t.value:host::varchar||'/oauth/complete-secret' as URI from table(flatten(input => parse_json(system$allowlist()))) as t where t.value:host::varchar LIKE 'apps-api%';
The Client name and Secret are used in the Omnata connection creation.
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.
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)
Tickets
Users
Organizations
Custom Objects
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.
