Zendesk Support provides SaaS products related to customer support, sales, and other customer communications. You can use Zendesk Support as a data source when landing or replicating data.
Click Authenticate when you have filled in the required connection settings.
You may be asked to log in to the source application.
A window is displayed with an authentication code.
Copy the code to the clipboard and return to the connection dialog.
Paste the code in Complete authentication with the code provided by the source and click Verify.
Примечание к подсказкеYou may need to scroll down to see this field.
When status is Verified, the authentication is verified.
Provide a name for the connection in Connection name.
Select Open connection metadata to define metadata for the connection when it has been created.
Connection settings
Setting
Description
Data gateway
Выберите шлюз Шлюз движения данных, если этого требует текущий сценарий использования.
Примечание к информации
Это поле недоступно при использовании подписки Qlik Talend Cloud Starter, так как она не поддерживает Шлюз движения данных. Если используется другой уровень подписки или не требуется использовать Шлюз движения данных, выберите Нет.
Для получения информации о преимуществах Шлюз движения данных и о сценариях, требующих его использования, см. раздел Шлюз данных Qlik — движение данных.
Start Date
Enter the date, in the format MM/DD/YYYY, from which the data must be replicated from your source to your target.
Zendesk Subdomain
You can find the subdomain of your Zendesk site in the URL of your account homepage. If the URL is https://qlik.zendesk.com/, the subdomain is qlik.
Client ID
Client ID.
Client Secret
Client secret.
Marketplace Name
Name of the integration.
Marketplace Organization ID
Organization ID.
Marketplace App ID
App ID.
Schema
Примечание к информации
Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.
The schema and info displayed below is for version 2.
Depending on your destination, table and column names may not appear as they are outlined below.
group_memberships
The group_memberships table contains info about the groups your Zendesk Support agents are members of.
Note: Retrieving group membership data requires Zendesk Support Agent or Admin permissions.
Deleted group memberships
As Zendesk Support’s API doesn’t currently provide a method for identifying deleted group memberships, 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.
The macros table contains info about the macros in your Zendesk Support account. Macros are actions defined by you that modify the values of a ticket’s fields.
Note: Retrieving macro data requires Zendesk Support Agent or Admin permissions.
ids: ARRAY, which is also a nested data structure.
type: STRING
title
STRING
updated_at
DATE-TIME
url
STRING
organizations
The organizations table contains information about the organizations your end-users belong to.
Custom organization fields
Zendesk Support integration will replicate any custom fields associated with organization records.
Note: Replicating organization custom fields requires that you be on a Team, Professional, or Enterprise Zendesk Support plan and have Admin permissions in Zendesk Support.
The sla_policies table contains info about the Service Level Agreements (SLAs) in your Zendesk Support account. An SLA is a documented agreement between a support provider and their customers that defines performance measures for support.
Note: Replicating SLA policies requires that you be on an Enterprise or Professional Zendesk Support plan, and have Admin permissions in Zendesk Support.
The ticket_audits table contains info about the activity associated with a ticket. An audit is a history of all updates to a given ticket. When a ticket is updated in Zendesk Support, an audit record is created. Each audit represents a single update to a ticket.
A single audit record may include multiple event types. For example: A ticket comment, satisfaction rating, and a change event. For a full list of Zendesk Support audit event types, refer to Zendesk Support’s documentation.
Replication
This table uses Append-Only Incremental Replication. This means that new audit records, or updates made to existing audits, are appended as new rows to the end of the table.
attachments: ARRAY, which is also a nested data structure.
audit_id: INTEGER
author_id: INTEGER
body: STRING
created_at: DATE-TIME
data: OBJECT, which is also a nested data structure.
answered_by_id: INTEGER
answered_by_name: STRING
call_duration: STRING
from: STRING
recording_url: STRING
started_at: DATE-TIME
to: STRING
transcription_status: STRING
transcription_text: STRING
field_name: STRING
formatted_from: STRING
formatted_to: STRING
html_body: STRING
id: INTEGER
macro_deleted: BOOLEAN
macro_id: STRING
macro_title: STRING
plain_body: STRING
previous_value: ARRAY, STRING, which is also a nested data structure.
public: BOOLEAN
recipients: ARRAY, which is also a nested data structure.
resource: STRING
subject: STRING
trusted: BOOLEAN
type: STRING
value: ARRAY, STRING, which is also a nested data structure.
via: OBJECT, which is also a nested data structure.
channel: STRING
source: OBJECT, which is also a nested data structure.
from: OBJECT, which is also a nested data structure.
address: STRING
deleted: BOOLEAN
id: INTEGER
name: STRING
original_recipients: ARRAY, which is also a nested data structure.
revision_id: INTEGER
subject: STRING
ticket_id: INTEGER
title: STRING
rel: STRING
to: OBJECT, which is also a nested data structure.
address: STRING
name: STRING
id
INTEGER
metadata
OBJECT
This is a nested data structure:
flags: ARRAY, which is also a nested data structure.
flags_options: OBJECT, which is also a nested data structure.
11: OBJECT, which is also a nested data structure.
message: OBJECT, which is also a nested data structure.
user: STRING
trusted: BOOLEAN
2: OBJECT, which is also a nested data structure.
trusted: BOOLEAN
notifications_suppressed_for: ARRAY, which is also a nested data structure.
system: OBJECT, which is also a nested data structure.
client: STRING
ip_address: STRING
json_email_identifier: STRING
latitude: NUMBER
location: STRING
longitude: NUMBER
message_id: STRING
raw_email_identifier: STRING
trusted: BOOLEAN
ticket_id
INTEGER
via
OBJECT
This is a nested data structure:
channel: STRING
source: OBJECT, which is also a nested data structure.
from: OBJECT, which is also a nested data structure.
address: STRING
deleted: BOOLEAN
id: INTEGER
name: STRING
original_recipients: ARRAY, which is also a nested data structure.
subject: STRING
ticket_id: INTEGER
ticket_ids: ARRAY, which is also a nested data structure.
title: STRING
rel: STRING
to: OBJECT, which is also a nested data structure.
address: STRING
name: STRING
ticket_comments
The ticket_comments table contains info about the comments on tickets, which is the conversation between requesters, collaborators, and agents. Comments can be public or private.
The ticket_forms table contains info about the ticket forms in your Zendesk Support account.
Note: Replicating ticket forms requires that you be on an Enterprise Zendesk Support plan or a Professional plan with the corresponding add-on, and have Admin permissions in Zendesk Support.
policy: OBJECT, which is also a nested data structure.
description: STRING
id: INTEGER
title: STRING
target: INTEGER
status
OBJECT
This is a nested data structure:
business: INTEGER
calendar: INTEGER
ticket_id
INTEGER
time
DATE-TIME
type
STRING
ticket_metrics
The ticket_metrics table contains info about the metrics associated with Zendesk Support tickets. This table will not include records for deleted tickets.
Note: Retrieving ticket metric data requires Zendesk Support Admin permissions.
Deleted ticket metrics
As Zendesk Support’s API doesn’t currently support returning metrics for deleted tickets, this table will not contain any metrics for deleted tickets.
If you believe you’re missing records, check in your Zendesk Support account to see if the missing records are for deleted tickets.
The tickets table contains info about the tickets in your Zendesk Support account. Tickets are the means through which your end users (customers) communicate with your Zendesk Support agents.
Note: Retrieving ticket data requires Zendesk Support Admin permissions.
Custom ticket fields
Zendesk Support integration will replicate all custom ticket fields.
Если вы обнаружили какую-либо проблему на этой странице или с ее содержанием — будь то опечатка, пропущенный шаг или техническая ошибка, сообщите нам об этом!
