+
Stream marketing data from Zendesk Support to Snowflake
About Zendesk Support
About SnowFlake
Connect Zendesk Support to Snowflake in 2023
It is very simple to connect Zendesk Support to Snowflake, it can be done in a fast and easy manner with Windsor.ai.
First Step
Follow the Tutorial Below:
- Add all the columns that are returned by your connector’s URL.
- Create the WINDSOR_UPLOAD role (name has no importance)
- Create a user and add the previously created role to that user
- Grant rights to the DATABASE to the created user
- Grand the rights to the destination table
- Get the required fields from Snowflake to use the Snowflake destination in Onboard Form
- Get the username
- Get the password
- Get the account
- Get the warehouse
- Get the database
- Get the schema
- Get the table name
Second step
1.You need to select Zendesk Support as a Data Source and Grant Access to Windsor.ai.
2. In Select Destination select Snowflake as destination
3. Enter all the credentials required and click Save
4.Your data will now be streamed to Snowflake. In case there is an error you will be notified.
Zendesk Support metrics and dimensions available for streaming into Snowflake
| name | type | description |
|---|---|---|
| Agent Wait Time In Minutes (business) | NUMERIC | Number of minutes the agent spent waiting during calendar and business hours |
| Agent Wait Time In Minutes (calendar) | NUMERIC | Number of minutes the agent spent waiting during calendar and business hours |
| Allow Attachments | BOOLEAN | Permission for agents to add add attachments to a comment. Defaults to true. |
| Allow Channelback | BOOLEAN | Is false if channelback is disabled, true otherwise. Only applicable for channels framework ticket. |
| Assigned At | DATE | When the ticket was assigned |
| Assignee Email | TEXT | Write only. The email address of the agent to assign the ticket to. |
| Assignee ID | TEXT | The agent currently assigned to the ticket. |
| Assignee Stations | NUMERIC | Number of assignees the ticket had |
| Assignee Updated At | DATE | When the assignee last updated the ticket |
| Attribute Value IDs | TEXT | Write only. An array of the IDs of attribute values to be associated with the ticket. |
| Brand ID | TEXT | Enterprise only. The id of the brand this ticket is associated with. |
| Collaborator IDs | TEXT | The ids of users currently CC'ed on the ticket. |
| Collaborators | TEXT | POST requests only. Users to add as cc's when creating a ticket. |
| Comment | TEXT | Write only. An object that adds a comment to the ticket. |
| Created At | DATE | When this record was created. |
| Custom Fields | TEXT | Custom fields for the ticket. |
| Custom Status ID | TEXT | The custom ticket status id of the ticket. |
| Custom Status Updated At | DATE | The date and time the ticket's custom status was last updated |
| Data Source | TEXT | The name of the Windsor connector returning the row |
| Date | DATE | Alias for Created At. |
| Day of month | TEXT | Day of the month |
| Description | TEXT | Read-only first comment on the ticket. When creating a ticket, use comment to set the description. |
| Due At | DATE | If this is a ticket of type task it has a due date. |
| Email cc IDs | TEXT | The ids of agents or end users currently CC'ed on the ticket. |
| Email ccs | TEXT | Write only. An array of objects that represent agent or end users email CCs to add or delete from the ticket. |
| External ID | TEXT | An id you can use to link Zendesk Support tickets to local records. |
| First Resolution Time in Minutes (business) | NUMERIC | Number of minutes to the first resolution time during calendar and business hours |
| First Resolution Time in Minutes (calendar) | NUMERIC | Number of minutes to the first resolution time during calendar and business hours |
| Follower IDs | TEXT | The ids of agents currently following the ticket. |
| Followers | TEXT | Write only. An array of objects that represent agent followers to add or delete from the ticket. |
| Followup IDs | TEXT | The ids of the followups created from this ticket. Ids are only visible once the ticket is closed. |
| Forum Topic ID | TEXT | The topic in the Zendesk Web portal this ticket originated from, if any. The Web portal is deprecated. |
| From Messaging Channel | BOOLEAN | If true, the ticket's via type is a messaging channel. |
| Full Resolution Time in Minutes (business) | NUMERIC | Number of minutes to the first resolution time during calendar and business hours |
| Full Resolution Time in Minutes (calendar) | NUMERIC | Number of minutes to the first resolution time during calendar and business hours |
| Group ID | TEXT | The group this ticket is assigned to. |
| Has Incidents | BOOLEAN | Is true if a ticket is a problem type and has one or more incidents linked to it. Otherwise, the value is false. |
| ID | TEXT | Automatically assigned when the ticket is created. |
| Initially Assigned At | DATE | When the ticket was initially assigned |
| Is Public | BOOLEAN | Is true if any comments are public, false otherwise. |
| Macro ID | TEXT | Write only. A macro ID to be recorded in the ticket audit. |
| Macro IDs | TEXT | POST requests only. List of macro IDs to be recorded in the ticket audit. |
| Metadata | TEXT | Write only. Metadata for the audit. In the audit object, the data is specified in the custom property of the metadata object. |
| Month | TEXT | Number of the month |
| Organization ID | TEXT | The organization of the requester. You can only specify the ID of an organization associated with the requester. |
| Priority | TEXT | The urgency with which the ticket should be addressed. Allowed values are urgent, high, normal, or low. |
| Problem ID | TEXT | For tickets of type incident, the ID of the problem the incident is linked to. |
| Raw Subject | TEXT | The dynamic content placeholder, if present, or the subject value, if not. |
| Recipient | TEXT | The original recipient e-mail address of the ticket. Notification emails for the ticket are sent from this address. |
| Reopens | NUMERIC | Total number of times the ticket was reopened. |
| Replies | NUMERIC | The number of public replies added to a ticket by an agent |
| Reply Time in Minutes (business) | NUMERIC | Number of minutes to the first reply during calendar and business hourss |
| Reply Time in Minutes (calendar) | NUMERIC | Number of minutes to the first reply during calendar and business hours |
| Reply Time in Seconds (business) | NUMERIC | Number of seconds to the first reply during calendar and business hourss |
| Reply Time in Seconds (calendar) | NUMERIC | Number of seconds to the first reply during calendar and business hours |
| Requester | TEXT | Write only. |
| Requester ID | TEXT | The user who requested this ticket. |
| Safe Update | BOOLEAN | Write only. Optional boolean. Prevents updates with outdated ticket data (updated_stamp property required when true). |
| Satisfaction Rating | TEXT | The satisfaction rating of the ticket, if it exists, or the state of satisfaction, offered or unoffered. The value is null for plan types that don't support CSAT. |
| Sharing Agreement IDs | TEXT | The ids of the sharing agreements used for this ticket. |
| Solved At | DATE | When the ticket was solved. |
| Source | TEXT | The name of the Windsor connector returning the row |
| Status | TEXT | The state of the ticket. Allowed values are new, open, pending, hold, solved, or closed. |
| Staus Updated At | DATE | When the status of the ticket was last updated |
| Subject | TEXT | The value of the subject field for this ticket. |
| Submitter ID | TEXT | The user who submitted the ticket. The submitter always becomes the author of the first comment on the ticket. |
| Tags | OBJECT | The array of tags applied to this ticket. |
| Ticket Form ID | TEXT | Enterprise only. The id of the ticket form to render for the ticket. |
| Today | DATE | Today's date |
| Type | TEXT | The type of this ticket. Allowed values are problem, incident, question, or task. |
| Updated At | DATE | When this record last got updated. |
| Updated Stamp | DATE | Write only. Datetime of last update received from API. |
| URL | TEXT | The API url of this ticket. |
| Via | TEXT | For more information, see the Via object reference |
| Via Followup Source ID | TEXT | POST requests only. The id of a closed ticket when creating a follow-up ticket. |
| Via ID | TEXT | For more information, see the Via object reference |
| Voice Comment | TEXT | Write only. See Creating voicemail ticket. |
| Week | TEXT | Week (Sun-Sat). |
| Day of week and day number | TEXT | Weekday number and name combined (Sun-Sat).Numbered from 0 Sunday to 6 Saturday. |
| Day of week and day number, ISO | TEXT | Weekday number and name combined, ISO format (Mon-Sun).Numbered from 1 Monday to 7 |
| Week ISO | TEXT | Week, ISO format (Mon-Sun). |
| Year | TEXT | Year |
| Yearmonth | TEXT | Year and month, e.g. 2024|3 |
| Year of week | TEXT | The year that contains first day of the week (Sun-Sat). |
| Year of week, ISO | TEXT | The year that contains first day of the ISO week (Mon-Sun). |
| Year week | TEXT | Year and week for US weeks (Sun-Sat), e.g. 2024|15 |
| Year week ISO | TEXT | Year and week for ISO weeks (Mon-Sun), e.g. 2024|20 |
Easily connect Zendesk Support to Snowflake
See the value and return on every marketing touchpoint
Providing 70+ marketing data streams, we make sure that all the data we integrate is fresh and accessible by marketers, whenever they want.
Spend less time on manual data loading and spreadsheets. Focus on delighting your customers.