Zendesk Support

Setup Zendesk Support with DinMo's ingestion capabilities.

Sync overview

The Zendesk Support connector supports multithreading. DinMo Ingest uses multiple parallel API requests to sync data from Zendesk systems to your destination. Your connection’s sync speed depends on your Zendesk API quota.

DinMo Ingest also syncs the following tables by registering a webhook endpoint with Zendesk.

  • AGENT_CHANNEL_HISTORY

  • AGENT_MAX_CAPACITY_HISTORY

  • AGENT_STATUS_HISTORY

  • AGENT_UNIFIED_STATUS_HISTORY

Historical sync time frame

You can configure the Historical sync time frame when setting up your connection to speed up both the initial sync and subsequent re-syncs. Historical sync time frame limits the amount of data synced for the following tables:

  • SATISFACTION_RATING

  • TICKET

  • TICKET_TAG

  • TICKET_FIELD

We apply the selected start date only to these tables, as they contain data that you are less likely to referenced much later.

For example, you might still refer a Zendesk agent created two years ago today if they are still with the company, so we do not apply the start date to the USER table. However, you are unlikely to refer to a ticket created 10 years ago , which is why we apply the start date to the TICKET table.

You can modify the Historical sync time frame at any time. If you change it to an earlier date, we perform a full historical sync, syncing data back to that new date. If you set it to a later date, we do not delete any existing data. Instead, we apply the new time frame only to subsequent re-syncs.

Schema Information

Syncing empty tables and columns

The Zendesk Support connector doesn't support the creation of empty tables and columns in your destination.

We create a table in the destination only if we can retrieve the table data from the source. If Zendesk doesn’t return data for the source table, we don’t create the table in your destination.

Last updated