In Zapier, open the Apps page, click + Add connection, search for Zendesk, enter your Zendesk subdomain and authorise with OAuth. You need Administrator permissions in Zendesk, a Zendesk Team plan or higher, and a Zapier plan that includes premium apps. Then build a Zap with a trigger such as New Ticket.
Three things to check first
- You're an Administrator in your Zendesk account.
- Your Zendesk account is on a Team plan or higher.
- Your Zapier plan includes premium apps, which is how Zapier classes Zendesk.
Miss any of these and the connection either won't appear or won't do much. The admin point matters beyond setup: non-admins can only watch one ticket per Zap with the New Action on Ticket trigger.
Connecting the account
- In Zapier, go to the Apps page and click + Add connection.
- Search for Zendesk, select it and click Add connection.
- Enter your Zendesk subdomain, log in if prompted and grant Zapier permission.
- Create a Zap and choose a Zendesk trigger, such as New Ticket.
- Add an action in another app or in Zendesk, such as Create Ticket or Add Comment to Ticket.
Old connections need reconnecting
Zapier Help Center flags a deadline every Zendesk admin should diarise. Zendesk is removing API token authentication by 30 April. Any older connection that asked for Account, Agent Email and API Token fields must be reconnected through OAuth before then, or the Zaps using it will stop. If you set up Zendesk Zaps a while ago, open your Apps page now and check how each connection signs in.
What you can automate
| Type | Examples Zapier lists |
|---|---|
| Triggers | New Ticket, Updated Ticket, New Tag Added to Ticket, New Organization, New User, New View, New Group |
| Instant trigger | Tag Added to User |
| Searches | Find Tickets, Find Latest Comment, Find a User, Find or Create User, Find an Agent, Find or Create Organization |
| Actions | Create Ticket, Add Comment to Ticket, Create Organization, Update User, Attach File to Ticket, Add or Remove Tag(s), Delete User |
| Advanced | API Request (Beta), a raw HTTP request using the connection's sign-in |
Most triggers are polling, so they check for new data on a schedule rather than firing instantly. Tag Added to User is the instant one. The New Suspended Ticket trigger notes that suspended tickets are automatically deleted after 14 days, so don't rely on Zendesk to keep them while you decide what to do.
Zapier's Zendesk page shows templates such as turning webhooks into Zendesk tickets, adding new tickets to Google Sheets rows, and creating tickets from Webflow form submissions.
Fixing the two most common failures
A ticket Zap that never triggers
The Recent Ticket trigger only fires for tickets in Zendesk's Recent Tickets view, so plenty of new tickets never reach it. The fix: in Zendesk, go to Admin, Views, Add View, set it to order by ID descending, then use that view with the New Ticket trigger.
Create Ticket fails on some runs
A Create Ticket action fails when a required field is mapped only from trigger data that can be empty. If a web form lets someone skip the subject, the ticket can't be created. Add static text alongside the trigger field, such as Web enquiry followed by the form's subject, so the field is never blank.
A worked example for a small support team
Say enquiries arrive through a Webflow form. A Zap triggered by each submission runs Create Ticket in Zendesk, with the subject mapped as Website form plus the visitor's subject, and the message as the description. A second Zap watches a custom Zendesk view of new tickets and adds a row to a Google Sheet for weekly reporting. Neither needs code.
n8n and help desks with their own automation
n8n lists Zendesk among its built-in app nodes for custom workflows, and my comparison of n8n and Zapier covers when it's the better fit. Other help desks, such as Intercom, have their own workflow automation built in. If you're reviewing your help desk too, see my roundup of Zendesk alternatives.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My advice for Zendesk admins
Connect with OAuth now, and move any API token connections over well before the deadline. Use a custom view with New Ticket instead of Recent Ticket, and pad required fields with static text. Keep the person who owns the Zaps on an admin account, so they're not limited to one ticket per Zap.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What do I need to connect Zendesk to Zapier?
Zendesk Administrator permissions, a Team plan or higher, and a Zapier plan that includes premium apps.
Why isn't my ticket Zap triggering?
The Recent Ticket trigger only sees Zendesk's Recent Tickets view; use a custom view with New Ticket.
What happens to API token connections?
Zendesk removes them by 30 April; reconnect with OAuth.
Can Zapier create Zendesk tickets?
Yes, with the Create Ticket action.
Can I attach files?
Yes, with the Attach File to Ticket action.