Comment on page
Zendesk
Sync your Zendesk organizations, end users, and tickets to Vitally with our Zendesk integration

What a Zendesk ticket looks like in Vitally
Vitally's Zendesk integration can be used to sync the following Zendesk data into Vitally in real time:
- Tickets - Vitally can import your Zendesk tickets into Vitally as threaded conversations (including internal Notes!).
- Users - Vitally can import your Zendesk end users and any custom traits associated with them into Vitally as users.
- Accounts - Vitally can import your Zendesk organizations and any custom traits associated with them into Vitally as accounts.
- Ticket Fields - Vitally can import the Zendesk ticket fields you want to pull in to Vitally
How to Enable | How-To Visual |
---|---|
| ![]() |
You can import both users and account data from Zendesk, and the configuration process is the same for both!

How-to Configure | How-to Visual |
---|---|
Configuring End Users The preferred way to unify User and Account data from Zendesk with Vitally is by the use of an external ID. You have the option to select another common identifier though. Read below for both configurations:
| For example, if you'd like to simply pull Zendesk tickets in and organize them underneath the user in Vitally with the same email as the Zendesk end user associated to the ticket ![]() Example configuration if your Zendesk users DO have the external ID of the user stored in some field
![]() |
Configuring Organizations The configuration process is the same for both Users and Organizations. Follow the steps above to configure Organizations! | ![]() |
Configuring Tickets PLEASE NOTE: End Users must be configured in order for Ticket syncs to occur. Now it's time to configure Tickets once you've set up your configuration for Accounts/Users.
| ![]() |
- Sync time
- Hourly
- Create vs Update on Accounts and Users
- Choose create and/or update
- Which objects the integrations can sync in:
- Accounts (= Organizations)
- User (= End Users)
- Conversations
- Import Filters (trait level filters)
- No for End Users but yes for Organizations
- Bi directional: yes or no
- No
- Data out (natively in vitally and pushing out to other platforms)
- No
- How is link established
- External ID or look up trait
- Historical data
- Import tickets from last 30 days
- Can I disable/delete data via the integration page?
- Disable and delete
Once you grant access to your Zendesk account, two things occur to ensure we track your Zendesk tickets as conversations in Vitally:
- 1.We'll import your most recent Zendesk tickets on initial connection: Once you connect your Zendesk account, we'll historically import tickets from the last 30 days and sync those into Vitally.
- 2.We'll listen for new Tickets moving forward: We'll listen for tickets associated with your existing users and accounts in Vitally. When one is found that matches an existing record, it will be added to Vitally as a conversation and linked to the corresponding user and account.
Furthermore, we'll sync data about any users and accounts (optional) to their corresponding records in Vitally.
Vitally pulls in the following details about your Zendesk tickets and attaches them to the created conversation in Vitally:
- The original ticket and all replies are pulled in as a threaded conversation
- The user that created the ticket and any teammate(s) assigned to the ticket
- The ticket's status in Zendesk (e.g. open vs closed)
- All statuses besides closed (on hold, pending, etc) will display as open in Vitally.
- The ticket's rating in Zendesk (if left by the user)
Q: Can I add multiple instances of Zendesk?
A: No, currently you can only connect 1 instance.
Q: Can you reply to Zendesk Tickets in Vitally?
A: No, it's a one-way sync.
Q: Can I sync all ticket fields to Vitally?
A: Yes! Users can now map in new native Zendesk ticket fields into Vitally. The new fields supported are:
- Assignee email
- Assignee ID
- Group ID
- Priority
- Status
- Submitter ID
Q: Are there any cases where we support syncing a Conversation that does not have a customer attached?
A: No, the ZD ticket must include the email address of an end user (your customer). An email address for a vitally user, but no end user (your customer), would be dropped.
Last modified 1mo ago