Zendesk Support

Sync data from Zendesk Support to your warehouse destination via RudderStack.

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.

warning
All the Cloud Extract sources support sending data only to a data warehouse destination.

Getting started

To set up Zendesk Support as a source in RudderStack, follow these steps:

  1. Log in to your RudderStack dashboard.
  2. Go to Collect > Sources > New Source > Cloud Extract. From the list of sources, select Zendesk Support.
  3. Assign a name to your source and click Continue.

Connection 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.
warning
If you do not specify the start date, RudderStack will replicate all your data by default.
  • Subdomain: Enter the subdomain from your Zendesk account’s URL. For example, if your Zendesk account URL is sample.zendesk.com, the subdomain would be sample.
  • 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. See Zendesk documentation 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 connected 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.
info
For more information on the schedule types, refer to the Common Settings guide.

Select data to import

You can import specific Marketo data by selecting the required resources:

ResourceSync type
audit_logsSemi-Incremental
automationsSemi-Incremental
brandsFull Refresh
custom_rolesFull Refresh
group_membershipsSemi-Incremental
groupsFull Refresh, Incremental
macrosFull Refresh, Incremental
organizationsFull Refresh, Incremental
organization_membershipsSemi-Incremental
satisfaction_ratingsFull Refresh, Incremental
schedulesFull Refresh
sla_policiesFull Refresh
tagsFull Refresh
ticket_auditsSemi-Incremental
ticket_commentsFull Refresh, Incremental
ticket_eventsIncremental
ticket_fieldsFull Refresh, Incremental
ticket_formsSemi-Incremental
ticket_metric_eventsFull Refresh, Incremental
ticket_metricsSemi-Incremental
ticketsFull Refresh, Incremental
triggersSemi-Incremental
usersFull Refresh, Incremental
viewsSemi-Incremental
info
For more information on the Full Refresh, Incremental, and Semi-Incremental sync modes, see Common Settings.
warning
There are some rate limits while sending requests to the Zendesk Support API. See Zendesk documentation for more details on these limits.

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.

How does RudderStack count the events for Cloud Extract sources?

RudderStack counts the number of records returned by the source APIs when queried during each sync. It considers each record as an event.

Questions? Contact us by email or on Slack