Zendesk ETL
Zendesk ETL connector for data replication
Snapshot
Integrate Zendesk with Daton
Signin to Daton
Select Zendesk from Integrations page
Provide Integration Name, Replication Frequency, and History. Integration name would be used in creating tables for the integration and cannot be changed later
Provide Zendesk Subdomain, LoginId, and Password to authorize Daton to periodically extract data from Zendesk
Post successful authentication, you will be prompted to choose from the list of available tables
Then select all required fields for each table
Submit the integration
Workflow
Integrations would be in Pending state initially and will be moved to Active state as soon as the first job loads data successfully on to the configured warehouse
Users would be able to edit/pause/re-activate/delete integration anytime
Users can view job status and process logs from the integration details page by clicking on the integration name from the active list
Zendesk Data
GroupMemberships
Purpose: A membership links an agent to a group. Groups can have many agents, as agents can be in many groups. You can use the API to list what agents are in which groups, and reassign group members.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/group_memberships
Replication: Key-Based Replication
Replication Key: created_at
Fields
Groups
Purpose: Groups serve as the core element of ticket workflow; support agents are organized into Groups and tickets can be assigned to a Group only, or to an assigned agent within a Group. A ticket can never be assigned to an agent without also being assigned to a Group.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/groups
Replication: Key-Based Replication
Replication Key: created_at
Fields
Macros
Purpose: A macro consists of one or more actions that modify the values of a ticket's fields. Macros are applied to tickets manually by agents. For example, you can create macros for support requests that agents can answer with a single, standard response.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/macros
Replication: Key-Based Replication
Replication Key: created_at
Fields
Organizations
Purpose: Just as agents can be segmented into groups in Zendesk Support, your customers (end-users) can be segmented into organizations. You can manually assign customers to an organization or automatically assign them to an organization by their email address domain. Organizations can be used in business rules to route tickets to groups of agents or to send email notifications.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/organizations
Replication: Key-Based Replication
Replication Key: created_at
Fields
SatisfactionRatings
Purpose: If you have enabled satisfaction ratings for your account, this end point allows you to quickly retrieve all ratings.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/satisfaction_ratings
Replication: Key-Based Replication
Replication Key: created_at
Fields
Tags
Purpose: You must enable the tagging of users and organizations in Zendesk Support for the API calls to work.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/tags
Replication: Key-Based Replication
Replication Key: created_at
Fields
ticket_audits id | INTEGER author_id | INTEGER ticket_id | INTEGER metadata | RECORD events | RECORD via | RECORD
TicketComments
Purpose: Ticket comments represent the conversation between requesters, collaborators, and agents. Comments can be public or private.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/ticket_comments
Replication: Key-Based Replication
Replication Key: created_at
Fields
TicketFields
Purpose: Zendesk Support allows admins to customize the fields displayed on the ticket form. Basic text fields as well as customizable dropdown and number fields are available. You can customize The visibility of these fields for end users in the admin interface.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/ticket_fields
Replication: Key-Based Replication
Replication Key: created_at
Fields
TicketForms
Purpose: Returns a list of all ticket forms for your account if accessed as an admin or agent. End users will only see the list of ticket forms that are marked 'end_user_visible'.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/ticket_forms
Replication: Key-Based Replication
Replication Key: created_at
Fields
TicketMetrics
Purpose: Returns a list of tickets with their metrics. Tickets are ordered chronologically by created date, from newest to oldest. The last ticket listed may not be the absolute oldest ticket in your account due to ticket archiving.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/ticket_metrics
Replication: Key-Based Replication
Replication Key: created_at
Fields
Tickets
Purpose: Tickets are the means through which your end users (customers) communicate with agents in Zendesk Support. Tickets can originate from a number of channels, including email, Help Center, chat, phone call, Twitter, Facebook, or the API. All tickets have a core set of properties.
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/tickets
Replication: Key-Based Replication
Replication Key: created_at
Fields
Users
Purpose: Returns all user details
Source API Documentation https://developer.zendesk.com/rest_api/docs/support/users#list-users
Replication: Key-Based Replication
Replication Key: created_at
Fields
Last updated