Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: link and put in data placement excerpt


  1. Search for the connection you created and click New Source.

  2. Edit the appropriate fields.


Specify the kind of object that you want to transfer from Zendesk: tickets, ticket_fields, ticket_forms, ticket_events, ticket_metrics, users, organizations, scores, recipients, object_records, relationship_records, user_events, and chat

  • object_records and relationship_records provide information about Zendesk custom objects

  • scores and recipients provide information about Zendesk NPS

  • Chat Limitations:

    • Only an administrator or owner has the permissions to retrieve chat data.

    • No support for "Include Subresources" and "De-duplicate records" options


Allows the connector to run in incremental mode, which enables Start time and End time can be used.

Start time

Enables you to select only objects, which have been updated since the 'start_time'

  • If Start time is not specified, all the objects are retrieved from the beginning.

End time

Enables you to select only objects, which have been updated up to the 'end_time'.

  • If End time is not specified, all the objects up to now are retrieved.

  • Start time and End time can combined to select only objects that have been updated within a specific period, from'start_time' until 'end_time'

Source Preview

  1. Preview your data. To make changes, click Advanced Settings.

  2. Select Next.


  1. After selecting Advanced Settings, the following dialog opens.

  2. Edit the parameters. Select Save and Next.



Include Subresources

Enables you to fetch sub-resource along with the main object. Click Add to add more sub resource by name and Add a correspondence column as well. The sub resource is considered as an JSON object, presented in a column, with the same name .

  • In Zendesk, this endpoint is supported: GET /api/v2/users/{user_id}/organizations.json That means we can consider organizations as a sub-resource of users. We can get all the information of organizations that a users belong to.

  • To configure it, you must add 'organizations' as a sub-resource and also add one more column with the same name. The data type should be JSON.

  • Include Subresources is not supported for Chat.

De-duplicated Records

Enables you to avoid duplicated records when running in incremental mode because the Zendesk API doesn't prevent duplication.

  • Deduplication is not supported for Chat.

Retry Limit

Indicates how many times the job should retry when error occurs.

Initial retry interval seconds

Indicates the first waiting time before a retry. Measured in seconds.

Data Transfer


Select a database and a table where you want to transfer your data.


Specify the schedule of the data transfer using the following dialog and click Next.


Name your source and click Done:


Excerpt Include
Data Placement
Data Placement

Use Command Line

Install ‘td’ Command


For more details on available out modes, see Appendix.

Guess Fields (Generate load.yml)


If the system detects your column name or type unexpectedly, modify the load.yml directly and preview again.

The Data Connector supports parsing of "boolean", "long", "double", "string", and "timestamp" types.

Execute Load Job

Submit the load job. It may take a couple of hours depending on the data size. Users need to specify the database and table where their data is stored.