Zendesk Support is a popular ticketing system and support platform. It lets you offer customer support through various mediums such as email, mobile, social media, and voice.
This document guides you in setting up Zendesk Support as a source in RudderStack. Once configured, RudderStack automatically ingests your Zendesk Support data and routes it to your specified data warehouse destination.
Getting started
To set up Zendesk Support as a source in RudderStack, follow these steps:
- Log into your RudderStack dashboard.
- Go to Sources > New source > Cloud Extract and select Zendesk Support from the list of sources.
- Assign a name to your source and click Continue.
Connection settings
To set up Zendesk Support as a Cloud Extract source, you need to configure the following settings:
- Start Date: Choose the start date from which you want RudderStack to ingest the Zendesk Support data. RudderStack will not replicate any data before this date.
- Subdomain: Enter the subdomain from your Zendesk account's URL. For example, if your Zendesk account URL is
sample.zendesk.com, the subdomain would besample. - Authentication: Select an authentication method from the dropdown:
- OAuth2.0: Click Connect with Zendesk Support to authenticate your account.
- API token: Enter the Email used to log in to the Zendesk account and the API token. Refer to the Zendesk documentation section for more details on obtaining the API Token.
Destination settings
The following settings specify how RudderStack sends the ingested data from Zendesk Support to the warehouse destination:
- Table prefix: RudderStack uses this prefix to create a table in your data warehouse and loads all your Zendesk Support data into it.
- Schedule Settings: RudderStack gives you three options to ingest the data from Zendesk Support:
- Basic: Runs the syncs at the specified time interval.
- CRON: Runs the syncs based on the user-defined CRON expression.
- Manual: You are required to run the syncs manually.
Selecting the data to import
You can choose the Zendesk Support data you want to ingest by selecting the required resources:
The below table lists the syncs supported by the Zendesk Support resources to your warehouse destination:
| Resource | Full Refresh sync | Incremental sync |
|---|---|---|
brands | Yes | No |
custom_roles | Yes | No |
group_memberships | Yes | Yes |
groups | Yes | Yes |
macros | Yes | Yes |
organizations | Yes | Yes |
satisfaction_ratings | Yes | Yes |
schedules | Yes | No |
sla_policies | Yes | No |
tags | Yes | No |
ticket_audits | Yes | Yes |
ticket_comments | Yes | Yes |
ticket_fields | Yes | Yes |
ticket_forms | Yes | Yes |
ticket_metric_events | Yes | Yes |
ticket_metrics | Yes | Yes |
tickets | Yes | Yes |
users | Yes | Yes |
Zendesk Support is now configured as a source. RudderStack will start ingesting data from Zendesk Support as per your specified schedule and frequency.
You can further connect this source to your data warehouse by clicking on Add Destination, as shown:
FAQ
Is it possible to have multiple Cloud Extract sources writing to the same schema?
Yes, it is.
RudderStack associates a table prefix for every Cloud Extract source writing to a warehouse schema. This way, multiple Cloud Extract sources can write to the same schema with different table prefixes.
Contact us
For more information on the topics covered on this page, email us or start a conversation in our Slack community.