Release Status | Released | Availability | Premium |
Status Page | Zendesk Status Page | Default Historical Sync | 1 year |
Whitelist Tables/Columns | Unsupported/Unsupported | Default Replication Frequency | 30 minutes |
Full Table Endpoints | 3 | Incremental Endpoints | 7 |
Destination Incompatibilities | Possible incompatibilities. Learn more. |
Connecting Zendesk
Connecting your Zendesk data to Stitch is a four-step process:
- Retrieve your Zendesk API token
- Add Zendesk as a Stitch data source
- Define the Historical Sync
- Define the Replication Frequency
Retrieve Your Zendesk API Token
- Sign into your Zendesk account.
- Click the Settings (gear) icon in the left sidebar.
- When the Settings menu displays, locate the Channels section.
- Click the API link in this section.
- Verify that the Token Access setting is enabled.
- Click the + button in the Active API Tokens section to create a new token.
- When prompted, enter a description for the token. We recommend using ‘Stitch,’ so you will know, at a glance, what application is using the token.
- Copy the token into a text file. Do NOT click Save until you’ve copied the token, as Zendesk only displays API tokens once for security reasons. If you save before copying the token, you’ll have to create another token.
- After you’ve copied the token, click Save.
Add Zendesk as a Stitch Data Source
- On the Stitch Dashboard page, click the Add an Integration button.
-
Click the Zendesk icon.
-
Enter a name for the integration. This is the name that will display on the for the integration; it’ll also be used to create the schema in your data warehouse.
For example, the name “Stitch Zendesk” would create a schema called
stitch_zendesk
in the data warehouse. This schema is where all the tables for this integration will be stored. - Enter your Zendesk site prefix. For example, if your full Zendesk URL was
stitchdata.zendesk.com
, you’d only need to enter the prefix, orstitch
, into this field. - Enter your Zendesk login email.
- Paste your Zendesk API token into the API Token field.
Defining the Historical Sync
The Sync Historical Data setting will define the starting date for your Zendesk integration. This means that data equal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to sync data beyond Zendesk’s default setting of 1 year. For a detailed look at historical syncs, check out the Syncing Historical SaaS Data article.
Define the Replication Frequency
The Replication Frequency controls how often Stitch will attempt to replicate data from your Zendesk integration. By default the frequency is set to 30 minutes, but you can change it to better suit your needs.
Before setting the Replication Frequency, note that:
- The more often Zendesk is set to replicate, the higher the number of replicated rows.
-
The number of rows in the source may not equal the number of rows replicated by Stitch. Tables that use Full Table Replication will result in a higher number of replicated rows.
- If you’re using a data warehouses that doesn’t natively support nested structures, you’ll see a higher number of replicated rows due to the de-nesting Stitch performs.
To help prevent overages, we recommend setting the Replication Frequency to something less frequent - like 6 hours instead of 30 minutes. For tips on reducing your row count, check out the Reducing Your Row Count section of our Billing Guide.
After selecting a Replication Frequency, click Save Integration.
Zendesk’s Intial Sync
After you finish setting up Zendesk, you might see its Sync Status show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial sync for the integration. This may take some time to complete.
Zendesk Schema
Stitch's Zendesk integration includes these tables:
- audits
- zendesk_group_memberships
- zendesk_groups
- zendesk_macros
- organizations
- zendesk_tags
- zendesk_tickets
- ticket_fields
- zendesk_ticket_metrics
- users
audits
Replication Method: Incremental
Primary Key: id
Contains Nested Structures?:
Yes
audits
table contains info about the activity associated with a ticket. This table contains the history of a ticket, with each audit event representing a single update to the ticket.audits & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
Event Types
For event types, see Zendesk’s documentation.
audits Attributes
While we try to include everything Zendesk has here, this may not be a full list of attributes. Refer to Zendesk's documentation for a full list and description of each attribute.
Audit ID (
id
)ticket_id
metadata
via
created_at
author_id
events
*
: If a subtable, this will contain the event ID (id
),type
,body
,public
, and data about attachments.
zendesk_group_memberships
Replication Method: Full Table
Primary Key: id
Contains Nested Structures?:
No
zendesk_group_memberships
table contains info about the groups your Zendesk agents are members of.Group Membership Record Deletes
As Zendesk’s API doesn’t currently provide a method for identifying deleted records, we recommend periodically dropping this table and allowing Stitch to re-create it. Currently, dropping and re-populating the table is the only way to detect deletions.
zendesk_group_memberships Attributes
While we try to include everything Zendesk has here, this may not be a full list of attributes. Refer to Zendesk's documentation for a full list and description of each attribute.
Group Membership ID (
id
)user_id
group_id
default
created_at
updated_at
zendesk_groups
Replication Method: Incremental
Primary Key: id
Contains Nested Structures?:
No
zendesk_groups
table contains info about the groups - which is how agents are organized - in your Zendesk account.Group Deletes
This table includes a field (deleted
) to identify groups that have been deleted.
zendesk_groups Attributes
While we try to include everything Zendesk has here, this may not be a full list of attributes. Refer to Zendesk's documentation for a full list and description of each attribute.
Group ID (
id
)url
name
deleted
created_at
updated_at
zendesk_macros
Replication Method: Incremental
Primary Key: id
Contains Nested Structures?:
Yes
zendesk_macros
table contains info about the macros in your Zendesk account. Macros are actions defined by you that modify the values of a ticket’s fields.zendesk_macros & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
zendesk_macros Attributes
While we try to include everything Zendesk has here, this may not be a full list of attributes. Refer to Zendesk's documentation for a full list and description of each attribute.
Macro ID (
id
)actions
*
active
description
position
restriction
title
created_at
updated_at
organizations
Replication Method: Incremental
Primary Key: id
Contains Nested Structures?:
Yes
organizations
table contains company information about your end-users.organizations & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
organizations Attributes
While we try to include everything Zendesk has here, this may not be a full list of attributes. Refer to Zendesk's documentation for a full list and description of each attribute.
Organization ID (
id
)url
external_id
name
created_at
updated_at
domain_names
*
details
notes
group_id
shared_tickets
shared_comments
tags
*
organization_fields
zendesk_tags
Replication Method: Full Table
Primary Key: name
Contains Nested Structures?:
No
zendesk_tags
table contains a list of tags in your Zendesk account.zendesk_tickets
Replication Method: Incremental
Primary Key: id
Contains Nested Structures?:
Yes
zendesk_tickets
table contains info about the tickets in your Zendesk account.zendesk_tickets & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
zendesk_tickets Attributes
While we try to include everything Zendesk has here, this may not be a full list of attributes. Refer to Zendesk's documentation for a full list and description of each attribute.
Ticket ID (
id
)url
external_id
type
subject
raw_subject
priority
status
recipient
requester_id
submitter_id
assignee_id
organization_id
group_id
collaborator_ids
*
forum_topic_id
problem_id
has_incidents
due_at
tags
*
via
custom_fields
*
satisfaction_rating
sharing_agreement_ids
*
followup_ids
ticket_form_id
brand_id
allow_channelback
is_public
created_at
updated_at
ticket_fields
Replication Method: Incremental
Primary Key: id
Contains Nested Structures?:
Yes
ticket_fields
table contains info about the basic text and custom ticket fields in your Zendesk account.ticket_fields & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
ticket_fields Attributes
While we try to include everything Zendesk has here, this may not be a full list of attributes. Refer to Zendesk's documentation for a full list and description of each attribute.
Ticket Field ID (
id
)url
type
title
raw_title
description
raw_description
position
active
required
collapsed_for_agents
regxp_for_validation
title_in_portal
raw_title_in_portal
visible_in_portal
editable_in_portal
required_in_portal
tag
created_at
updated_at
system_field_options
*
custom_field_options
*
removable
zendesk_ticket_metrics
Replication Method: Full Table
Primary Key: id
Contains Nested Structures?:
No
zendesk_ticket_metrics
table contains info about the metrics associated with Zendesk tickets. Note that this table will NOT include records for archived tickets - see the Table Info section for details.Archived Ticket Metrics
As Zendesk’s API doesn’t currently support returning metrics for archived tickets, this table will not contain any metrics for archived tickets.
If you believe you’re missing records, check in your Zendesk account to see if the missing records are for archived tickets.
For more info on how Zendesk handles archiving tickets, check out their documentation.
zendesk_ticket_metrics Attributes
While we try to include everything Zendesk has here, this may not be a full list of attributes. Refer to Zendesk's documentation for a full list and description of each attribute.
Ticket Metric ID (
id
)ticket_id
url
group_stations
assignee_stations
reopens
replies
assignee_updated_at
requester_updated_at
status_updated_at
intitially_updated_at
assigned_at
solved_at
latest_comment_added_at
first_resolution_time_in_minutes
reply_time_in_minutes
full_resolution_time_in_minutes
agent_wait_time_in_minutes
requester_wait_time_in_minutes
created_at
updated_at
users
Replication Method: Incremental
Primary Key: id
Contains Nested Structures?:
Yes
users
table contains info about all the users - end-users, agents, and administrators - in your Zendesk account.users & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
users Attributes
While we try to include everything Zendesk has here, this may not be a full list of attributes. Refer to Zendesk's documentation for a full list and description of each attribute.
User ID (
id
)email
name
active
alias
chat_only
created_at
custom_role_id
details
external_id
last_login_at
locale_id
moderator
notes
only_private_comments
organization_id
phone
photo
restricted_agent
role
shared
shared_agent
signature
suspended
tags
*
ticket_restriction
time_zone
two_factor_auth_enabled
updated_at
url
user_fields
verified
Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, please reach out to us.