Search for the connection you created and click New Source.
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
Allows the connector to run in incremental mode, which enables Start time and End time can be used.
Enables you to select only objects, which have been updated since the 'start_time'
Enables you to select only objects, which have been updated up to the 'end_time'.
Preview your data. To make changes, click Advanced Settings.
After selecting Advanced Settings, the following dialog opens.
Edit the parameters. Select Save and Next.
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 .
Enables you to avoid duplicated records when running in incremental mode because the Zendesk API doesn't prevent duplication.
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.
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:
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.