Release Status Closed Beta Supported By Singer community
Availability Free Status Page Zendesk Chat Status Page
Default Historical Sync 1 year Default Replication Frequency 30 minutes
Whitelisting Unsupported Destination Incompatibilities None

Connecting Zendesk Chat

Connecting your Zendesk Chat (formerly known as Zopim) data to Stitch is a four-step process:

  1. Add Zendesk Chat as a Stitch data source
  2. Define the Historical Sync
  3. Define the Replication Frequency
  4. Authorize Stitch to access Zopim

Prerequisites

  1. Owner permissions in Zendesk Chat. The user who authorizes the integration must have Owner permissions in Zendesk Chat. Otherwise, Stitch will encounter authentication issues and be unable to replicate data.

  2. An Advanced or Premium Zendesk Chat account. Zendesk only allows customers on their Advanced or Paid Zendesk Chat plans to utilize the Rest API, which is what Stitch uses to connect to your Zendesk Chat account and replicate data.

    If your Zendesk Chat account is on Lite or Basic, you will need to upgrade your Zendesk Chat plan. More info on Zendesk Chat plans can be found on Zendesk’s website.

Add Zendesk Chat as a Stitch Data Source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Zendesk Chat icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Zendesk Chat” would create a schema called stitch_zendesk_chat in the destination. Note: Schema names cannot be changed after you save the integration.

Define the Historical Sync

The Sync Historical Data setting will define the starting date for your Zendesk Chat integration. This means that:

  • For tables using Incremental Replication, data equal to or newer than this date will be replicated to your data warehouse.
  • For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Zendesk Chat’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Stitch offers two methods of creating a replication schedule:

  • Replication Frequency: This method requires selecting the interval you want replication to run for the integration. Start times of replication jobs are based on the start time and duration of the previous job. Refer to the Replication Frequency documentation for more information and examples.
  • Anchor scheduling: Based on the Replication Frequency, or interval, you select, this method “anchors” the start times of this integration’s replication jobs to a time you select to create a predictable schedule. Anchor scheduling is a combination of the Anchor Time and Replication Frequency settings, which must both be defined to use this method. Additionally, note that:

    • A Replication Frequency of at least one hour is required to use anchor scheduling.
    • An initial replication job may not begin immediately after saving the integration, depending on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.

To help prevent overages, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Authorizing Stitch to Access Zendesk Chat

Lastly, you’ll be directed to Zendesk’s website to complete the setup.

  1. Enter your Zendesk Chat credentials and click Login.
  2. Complete the authorization process.
  3. After the authorization process successfully completes, you’ll be redirected back to Stitch.
  4. Click All Done.

Initial and historical replication jobs

After you finish setting up Zendesk Chat, its Sync Status may 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 replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.


Zendesk Chat Schema

Stitch's Zendesk Chat integration includes these tables:


zopim_account

Replication Method: Full Table
Primary Key: account_key
Contains Nested Structures?: No

The zopim_account table contains info about your Zopim account.

Table Info & Attributes

zopim_account Attributes

While we try to include everything Zendesk Chat has here, this may not be a full list of attributes. Refer to Zendesk Chat's documentation for a full list and description of each attribute.

  • Widget Key (account_key)

  • create_date

  • status

  • plan

  • billing

zopim_agents

Replication Method: Full Table
Primary Key: id
Contains Nested Structures?: Yes

The zopim_agents table contains info about the agents in your Zopim account.

Table Info & Attributes

zopim_agents & 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 *

zopim_agents Attributes

While we try to include everything Zendesk Chat has here, this may not be a full list of attributes. Refer to Zendesk Chat's documentation for a full list and description of each attribute.

  • Agent ID (id)

  • first_name

  • last_name

  • display_name

  • create_date

  • email

  • role

  • enabled

  • departments*

zopim_banned_ips

Replication Method: Full Table
Primary Key: id
Contains Nested Structures?: No

The zopim_banned_ips table contains info about the IPs banned from your Zopim account.

Table Info & Attributes

zopim_banned_ips Attributes

While we try to include everything Zendesk Chat has here, this may not be a full list of attributes. Refer to Zendesk Chat's documentation for a full list and description of each attribute.

  • Banned IP ID (id)

  • ip_address

  • reason

  • type

zopim_banned_visitors

Replication Method: Full Table
Primary Key: id
Contains Nested Structures?: No

The zopim_banned_visitors table contains info about the visitors banned from your Zopim account.

Table Info & Attributes

zopim_banned_visitors Attributes

While we try to include everything Zendesk Chat has here, this may not be a full list of attributes. Refer to Zendesk Chat's documentation for a full list and description of each attribute.

  • Ban ID (id)

  • ip_address

  • visitor_id

  • visitor_name

  • reason

  • type

zopim_chats

Replication Method: Key-based Incremental
Primary Key: id
Contains Nested Structures?: Yes

The zopim_chats table contains info about the chats in your Zopim account.

Table Info & Attributes

zopim_chats & 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 *

Chat Types & Null Values

Depending on the type of chat - support versus offline - some records may have NULL values. Offline chats will only have some of the attributes listed below populated.

zopim_chats Attributes

While we try to include everything Zendesk Chat has here, this may not be a full list of attributes. Refer to Zendesk Chat's documentation for a full list and description of each attribute.

  • Chat ID (id)

  • visitor

  • type

  • started_by

  • session

  • timestamp

  • count

  • duration

  • department_id

  • department_name

  • response_time

  • agent_names*

  • agent_ids*

  • triggered

  • triggered_response

  • unread

  • missed

  • history

  • tags*

  • rating

  • comment

  • webpath*

  • zendesk_ticket_id

zopim_departments

Replication Method: Full Table
Primary Key: id
Contains Nested Structures?: Yes

The zopim_departments table contains info about the departments in your Zopim account.

Table Info & Attributes

zopim_departments & 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 *

zopim_departments Attributes

While we try to include everything Zendesk Chat has here, this may not be a full list of attributes. Refer to Zendesk Chat's documentation for a full list and description of each attribute.

  • Department ID (id)

  • name

  • description

  • enabled

  • members*

  • settings

zopim_shortcuts

Replication Method: Full Table
Primary Key: name
Contains Nested Structures?: Yes

The zopim_shortcuts table contains info about the shortcuts in your Zopim account.

Table Info & Attributes

zopim_shortcuts & 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 *

zopim_shortcuts Attributes

While we try to include everything Zendesk Chat has here, this may not be a full list of attributes. Refer to Zendesk Chat's documentation for a full list and description of each attribute.

  • Shortcut Name (name)

  • options

  • message

  • tags*

zopim_triggers

Replication Method: Full Table
Primary Key: name
Contains Nested Structures?: No

The zopim_triggers table contains info about the triggers in your Zopim account.

Table Info & Attributes

zopim_triggers Attributes

While we try to include everything Zendesk Chat has here, this may not be a full list of attributes. Refer to Zendesk Chat's documentation for a full list and description of each attribute.

  • Trigger Name (name)

  • enabled

  • description



Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.