On This Page
You can load the data of your Zendesk tickets and user information into the Destination of your choice using Hevo Pipelines.
For creating Pipelines using this Source, Hevo provides you a fully managed BigQuery data warehouse as a possible Destination. This option remains available till the time you set up your first BigQuery Destination irrespective of any other Destinations that you may have. With the managed warehouse, you are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery.
- You are an Administrator in Zendesk to access your data through APIs.
Configuring Zendesk as a Source
Perform the following steps to configure Zendesk as a Source in your Pipeline:
Click PIPELINES in the Asset Palette.
Click + CREATE in the Pipelines List View.
In the Select Source Type page, select Zendesk as the Source.
In the Configure your Zendesk Source page, provide the following information:
Pipeline Name: A unique name for your Pipeline.
Sub Domain: Your Zendesk sub-domain.
Email: Your login email ID for Zendesk.
Token: The Zendesk token which you generated.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.
Generating a Zendesk API Token
Go to your Zendesk dashboard.
In the left navigation bar, click the gear () icon.
In the page that is displayed, select Channels > API.
Click on the settings tab and enable Token Access.
Click on the + button and generate a new API Token.
Copy the API Token and save it in a secure location. For more details please go through the Zendesk documentation.
|Default Pipeline Frequency||Minimum Pipeline Frequency||Maximum Pipeline Frequency|
|5 Mins||5 Mins||3 Hrs|
Hevo fetches data for the objects,
users, using Zendesk’s Incremental Export API.
The data returned by this API includes the field,
id, which is unique for every object. For example, the
id field in the
tickets object uniquely identifies a ticket, while the
id field in the
users object uniquely identifies a user. Hevo recommends that you use
id as your primary key while creating a table in your Destination.
Historical Data: In the first run of the Pipeline, Hevo ingests the data for the last one year for all the objects in your Zendesk account.
Incremental Data: All new and updated Events are synchronized with your Destination as per your selected ingestion frequency.
Refer to the following table for the list of key updates made to this page:
|Date||Release||Description of Change|
|Oct-25-2021||NA||Added the Pipeline frequency information in the Data Replication section.|
|Oct-25-2021||1.74||Updated the Data Replication section with information about the list of objects that Hevo fetches and the historical and incremental data load.|