Stitch Documentation
has moved!

Please update your bookmarks to https://www.stitchdata.com/docs

If you're not automatically redirected after 5 seconds, click here.

Expected Desk.com Data

Now that Desk is successfully connected to your Stitch account, what comes next? In this article, we'll cover:

Replicating Desk Data

Historical Sync

By default, a historical sync of Desk data goes back one year from the Stitch connection date.

Frequency

Stitch will replicate Desk data based on the frequency you define. The default setting is every 30 minutes, but you can change it to more or less frequent based on your needs.

Replication Method

When Stitch replicates Desk data, it does so using Incremental Replication. This means that every time Desk data is queued for replication, only new and updated rows will be replicated to your data warehouse.

Desk Tables in Your Data Warehouse

Below is a list of the Desk tables that will be created in your data warehouse. Because Desk uses nested arrays to structure data in some of its API's endpoints, Stitch will de-nest these arrays and create subtables. Refer to the Handling of Nested Data Structures doc for more info.

To see a full list of attributes for each table, refer to Desk's API documentation - click the name of the table to go there.

cases
Primary Key:
_id

The cases table contains information about the support cases in your Desk account.

Attributes include the case ID (id), assigned user, summary, subject, priority, description, status, type, language, custom fields, rule suppression setting, lock date, customer ID, changed at, active at, received at, first opened at, opened at, first resolved at, resolved at, and created and updated at dates.

Subtables

The composite key for the following tables - made up of the case ID and the row ID - can be used to tie it back to its parent table, cases: _sdc_source_key_id:_sdc_level_0_id.

  • cases__label_ids - This subtable is created from the label IDs array, which contains the label IDs associated with a case.
  • cases__labels - This subtable is created from the labels array, which contains the labels associated with a case.

customers
Primary Key:
_id

The customers table contains information about the end-users in your Desk account.

Attributes include the customer ID (id), first and last name, company, title, avatar URL, uid, background info, lock date, custom fields, private portal access setting, company cases access setting, and created and updated at dates. 

Subtables

The composite key for the following tables - made up of the customer ID and the row ID - can be used to tie it back to its parent table, customers: _sdc_source_key_id:_sdc_level_0_id.

  • customers__emails - This subtable is created from the emails array, which contains the email addresses associated with a customer.
  • customers__addresses - This subtable is created from the addresses array, which contains the addresses associated with a customer.
  • customers__phone_numbers - This subtable is created from the phone numbers array, which contains the phone numbers associated with a customer.

replies
Primary Key:
case_id:reply_id

The replies table contains the individual replies in cases.

Attributes include the case ID, reply ID, subject, body, direction (in/out), status, to and from email addresses, CC and BCC, client type, rule suppression setting, sent by, and sent, created, and updated at dates.

users
Primary Key:
 _id

The users table contains information about the internal users of your Desk account.

Attributes include the user ID (id), name, email address, email verification setting, avatar URL, permission level, current and last login dates, and created and updated at dates.

users_groups
Primary Key:
user_id:_id

The users_groups table contains information about the groups your internal users belong to.

Attributes include the group ID (id), group name, and user ID.

Related

Was this article helpful?
0 out of 0 found this helpful

Comments

Questions or suggestions? If something in our documentation is unclear, let us know in the comments!