Перейти к содержанию
tl;dr of Zendesk Integrations
- Zendesk has five built-in integrations in the Admin Center: Salesforce, Shopify, Slack, Workday and Microsoft 365 Copilot. That list is fixed, and none of them are switched on as standard.
- The Marketplace holds 1,822 apps, 1,040 of them free to install. A listing there doesn’t mean Zendesk supports it, or that anything will show up in your agent view.
- Apps and integrations are different things. Zendesk keeps them separate in its own interface, and some Marketplace apps never install anything into Zendesk at all.
- There are also 55 free connectors built by Zendesk. They sit inside Zendesk’s automation rather than the agent sidebar, which is why most people never find them.
- Reading a tool’s trigger and action lists on Zapier tells you which direction data can move, in about a minute, before you book a demo.
- tl;dv connects through Zapier with three triggers and one action, so meetings create tickets. Zendesk also supports MCP connections natively.
Zendesk integrations are an easy way to use the information that is stored in your Zendesk account to work with other tools and workflows that you may have. They come in two ways, but the Admin Center only stores five native ones, covering Salesforce, Shopify, Slack, Workday and Microsoft 365 Copilot.
If that list looks short to you, then it may be the tool or app you need will be located within Zendesk’s Marketplace, where there are over 1,822 apps.
I took a look by launching a free trial of a Zendesk account, partly to test Zendesk’s MCP, and also to see how easy it was to set up an integration to help manage different workflows and situations. The word integration is a bit of a misnomer, because often what people want help with is sorted by an app. It’s a little confusing but I’m going to lay it out here: what each thing is, where each connection sits, how the information is passed between them, and what it costs.
Zendesk Apps vs Zendesk Integrations: What’s the Difference?
A Zendesk integration is something that was built by Zendesk, can be turned on in the Admin Center and is supported by Zendesk itself.
An app is built by a third party, located and installed via Zendesk’s Marketplace, and is supported by the team that created it.
Zendesk keeps these separate in its interface, and that’s right because Apps are not technically integrations.
Zendesk Integrations
- Salesforce. Syncs tickets and account data between the two platforms, so an agent can see what the customer is worth before they answer.
- Shopify. Pulls order and customer data into the ticket on Zendesk, so nobody has to ask which order the complaint is about.
- Slack. Pushes ticket notifications and lets people raise tickets from a Slack channel, so requests stop arriving as DMs to whoever is nearest.
- Workday. Shows worker data alongside the relevant tickets, useful when the person raising the ticket is an employee rather than a customer.
- Microsoft 365 Copilot. Lets people search help articles and manage their own tickets inside Copilot, so routine requests never reach an agent.
None of these are switched on as standard, so if this is what you’re looking for you’ll need to trigger it in your Zendesk dashboard.
Zendesk Apps
There is a good chance that none of those five are what you are looking for, in which case you’ll need to take a look at the 1,822 apps currently in the Marketplace. Microsoft Teams, Pipedrive, Klaviyo, TikTok Shop and Fullstory are all in there, which gives you a sense of how far it runs.
Those are the two most common types, but there are four other ways into Zendesk.
| Layer | How many | Supported by | Where it shows up |
|---|---|---|---|
| Built-in integrations | 5 | Zendesk | Admin Center |
| Marketplace apps | 1,822 (1,040 free) | The app vendor | Usually the agent sidebar |
| Соединители | 55 | Zendesk | Inside automation, not the agent view |
| Channels | ~14 | Zendesk | As a new inbox |
| Build your own | Без ограничений | Вы | Wherever you put it |
| Zapier and similar | ~9,000 apps | Zapier | Nowhere visible |
The Best Zendesk Integrations by Job in 2026
Why would you need a Zendesk integration in the first place?
Most of the time, a customer support rep knows what they need to do but doesn’t have the information to do it. An order number, the tier the customer is on, whether engineering already knows about the bug. All of it lives somewhere else. Connecting those tools means the rep stops opening tabs to go and find it.
Here are a few examples of what the job is and the ways to get to a quicker answer.
| Job | Инструмент | Layer | Что вы получаете |
|---|---|---|---|
| Engineering handoff | Jira | Marketplace app, built by Zendesk | Link a ticket to a dev issue and see the status change without asking |
| Team chat | Slack | Built-in integration | Ticket notifications in a channel, and anyone can raise a ticket from there |
| CRM | Salesforce | Built-in integration | Ticket and account data syncing both ways |
| CRM | HubSpot | Marketplace app | Support tickets visible inside HubSpot |
| Ecommerce | Shopify | Built-in integration | Order and customer detail in the ticket |
| HR | Workday | Built-in integration | Worker data alongside tickets from employees |
| Запись встречи | tl;dv | Zapier | Meeting transcripts into tickets automatically |
The official Zendesk integration list is pretty thin. Zendesk has built 55 apps of its own, and only about 15 of these connect to anything outside of Zendesk.
The rest are apps for Zendesk’s own other products like Sell and Chat, small agent tools like Time Tracking and Out of Office, and developer utilities. Counting dozens of Zendesk-built integrations only works if you count Emoji.
HubSpot and Microsoft Outlook are two that sound quite useful, but they don’t actually run in the way you’d think. Outlook can turn an email into a ticket, and HubSpot shows tickets to your sales teams in HubSpot natively, but neither does anything inside Zendesk.
One thing Salesforce does that almost nothing else does: the setup screen asks whether you want to connect to production or a sandbox before you authenticate. If you have ever been told to test an integration safely and had no idea how, that is what you were missing.
The Sixty-Second Check I Would Run Before Booking a Demo
There is a fast way to work out what a tool can actually do with your Zendesk, in about a minute of clicking and without speaking to any reps.
The Zapier directory tells you most of it, including the things a sales call likely won’t.
First, go to the tool’s page on Zapier and take a look at the list of actions and triggers.
Triggers are what a tool can tell other systems about. For example, tl;dv has a trigger for when a transcript is ready, which is how it announces that a meeting has finished and the text is available.
Actions are the things it will accept from them. For example, Zendesk has an action for creating a ticket, so it takes what arrives from tl;dv and turns it into something a rep can pick up and work on.
The next step is to compare the two lists against each other. Pair the tool’s triggers against Zendesk’s actions and you have one direction. Then flip it around for the other. If either pairing comes back empty, that direction doesn’t exist. No matter how much a sales rep talks up the integration, nothing changes without a developer and a budget.
Read what a trigger actually carries, not just its name. One that sends a meeting title and a link gives you a useless ticket. One that sends the full transcript gives a rep something to work with. On the page they look identical.
Zapier also only shows what the vendor put on Zapier, which is usually less than the tool can really do.
There is one thing that often gets dodged in a demo. If a field gets changed in both systems on the same day, which one overwrites the other? If you do end up on a call with a vendor, ask them that and see what happens.
Zendesk Connectors: 55 Free First-Party Tools
Zendesk also has a connectors directory, separate from its Marketplace.
When I looked inside the trial account, it had 55 connectors, and each card was marked as built by Zendesk. They are all free, and quite easy to miss, because they don’t show up where you would naturally look for them. A connector doesn’t put anything in the agent’s sidebar. It becomes a step inside Zendesk’s automation, under Actions, so the only person who ever sees one is someone building a workflow.
It is quite a big list, and it includes Adyen, Airtable, Asana, BambooHR, Calendly, Chargebee, Claude, Confluence, GitHub, Gmail, Google Gemini, Google Drive, Google Forms, Google Sheets, HubSpot, and incident.io, which is not even half of them.
Claude and Google Gemini both being in there is worth a second look, because it means Zendesk has built AI tools into its own automation rather than leaving you to bolt them on. If you’re weighing up which MCP servers are actually worth connecting, that’s a separate rabbit hole.
There is an anomaly I found, though. Adyen and BambooHR don’t actually appear on Zendesk’s own public developer page, which is supposed to list the connectors it builds. They only show up inside the product.
The reason to care is that connector pages tell you what each one can actually do and which plan you need before you commit to anything. Marketplace listings tend to leave you to find that out yourself.
tl;dv and Zendesk: Getting Meeting Recordings Into Tickets
There is no native integration between tl;dv and Zendesk at the moment, though tl;dv does connect natively to a fair few other tools.
Anything happening between the two tools goes through Zapier.
As of September 2026, this is what tl;dv puts on Zapier.
| Тип | Name | Что он делает |
|---|---|---|
| Триггер | Note Added | Fires when a note is added or generated |
| Триггер | Transcript Added | Fires when a transcript is created |
| Триггер | Recording Added | Fires when a recording is created |
| Действие | Upload Recording | Accepts a recording and its name |
There are three triggers and one action. When you pair those against Zendesk, there is a setup that’s really worth building.
Trigger on Transcript Added, add a filter on the meeting title so your internal stand-ups don’t start generating tickets, then create a ticket in Zendesk or add a comment to an existing one. The full transcript and the meeting link both show up as fields, and you can drop them wherever you want. It takes a few minutes and doesn’t need anybody technical to get involved.
What that ultimately gets you is the one thing support teams normally have to chase. A customer calls, someone promises it’s fixed, and the details of that promise live in someone’s memory or in a note on someone’s desk. With this running, the whole conversation lands on the ticket before anybody even opens Zendesk. The rep picking it up can read what was actually said, not a summary.
Now, the direction. Meetings can create tickets. Tickets cannot create meetings, because the only thing tl;dv will accept from another system is a recording, and a support ticket doesn’t have one. That is how it should work. tl;dv is where meetings live, and there’s no reason for a ticket to turn up in a meeting library.
There is a second route, and it answers a different question: can your AI assistant see your meeting history and your ticket history at the same time?
Yes. Zendesk supports MCP connections natively, set up in the Admin Center under Connections, and they were available on the Suite Professional trial I was using. It works both ways round, too. Zendesk can connect out to other tools’ servers and use them inside its own automation, and it can expose its own data to an AI assistant. tl;dv publishes a server as well, so both ends of this exist. I’ve gone through the Zendesk side in more detail in a separate piece on Zendesk MCP.
What to Ask Before You Connect A Zendesk Integration
Most of what we’ve covered so far is free. The five built-in integrations are included in your Zendesk costs; all 55 connectors are free, and 1,040 Marketplace apps cost nothing to install. But free to install is not the same as free to run.
So if you have found something that works with your Zendesk and fits your workflow, and you want to be sure nothing is waiting to bite you later, ask these questions first.
What can it read, and what can it change? These are two different permissions and vendors tend to ask for both by default. Find out whether you can start read-only and open up writing later once you trust it. If the answer is no, that tells you something about how the tool is built.
How will I know when it breaks? Ask where errors show up and what they actually look like. Most people don’t, and then find themselves trying to work out what went wrong without knowing what they’re looking for. A demo won’t cover it unless you raise it.
And if it is paid, what am I charged per? Is it by agent, ticket, sync event, API call? They look similar on a quote, but some fire far more often than others. A tool priced per sync event is cheap until the month something goes wrong upstream. Then you’re paying for the error twice. Ask whether a light agent counts as an agent too, because on a big team that one answer can double your bill.
Getting Meeting Context Into Zendesk
We’ve looked at Zendesk integrations, Zendesk apps, and everything else that could reasonably be called an integration. But the crux of it is this. If you have a support team that sits in on customer calls and then has to write them up afterward, the most useful thing you can connect is tl;dv.
Set up the Zap, and it takes a few minutes if you have admin rights.
Once it’s live, record the call in tl;dv, filter on the meeting title so your internal meetings stay out of it, and let Zendesk build the ticket. The rep who picks it up sees exactly what was said, not someone’s recollection.
It won’t fix everything. You’ll still need someone to decide which meetings should be generating tickets in the first place, but that’s a process question rather than a tooling one.
If you want to try it, tl;dv is free to start and the Zapier side doesn’t need a developer. Get the first one running before your next call.
FAQs About Zendesk Integrations
Which Zendesk plan do I need to install Marketplace apps?
Any plan lets you install public Marketplace apps, but you need admin rights on the account, so a rep can’t do it alone. Uploading an app your own team has built requires a higher tier. Zendesk’s 55 free connectors each publish their own plan requirements on their connector page.
Why isn't the app showing up in my agent sidebar?
Because some apps were never going to appear there. Zendesk separates apps that install into your account from ones that only run inside the other product, where the Zendesk end is just a set of credentials. The Marketplace listing rarely makes this obvious. Check which kind you installed.
Can I test a Zendesk integration before rolling it out?
Безусловно. tl;dv очень щедрый бесплатный тарифный план, который позволяет тестировать все его функции без ограничения по времени.
What happens to my tickets if an integration breaks?
That depends entirely on the vendor. Ask whether failed records queue up and retry or just vanish, whether a restored connection catches up on what it missed, and where the errors show up. Failure behavior rarely comes up in a demo unless you raise it.
Do third-party integrations count against Zendesk's API limits?
Yes. Every connection draws on the same account allowance, which varies by plan, so four or five running together will slow each other down. If syncs go sluggish after you add a tool, that’s usually why. Check your plan’s limit before adding another.
