Resources · Zapier integration

Zendesk Zapier integrationAutomate Zendesk with Zapier.

The Zendesk Zapier integration offers 13 triggers, 12 actions and 7 searches on tickets, users and organizations. Here is what each one does, why it needs a paid plan, which triggers react at once, and the traps that quietly stall a support Zap.

Premium app Zapier reserves this app to its paid plans.

See the 32 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Zendesk Zapier integration actually does

The Zendesk Zapier integration plugs your Zendesk help desk into Zapier, a tool that chains apps together without code. It watches tickets, comments, tags, users, organizations, groups and views, and it can create or update tickets, users and organizations, add comments and files, move tags, or look up what already exists.

Three results come back on support teams. Tickets sorted before an agent opens them: New Ticket spots the request, Add Tag(s) to Ticket routes it. A customer base that stays tidy: Find a User looks the person up, creates them if missing, and Update User keeps the record current. A paper trail on every escalation: New Tag Added to Ticket catches the escalation tag, Update Ticket posts an internal comment.

The most useful thing to know before building: only 2 of the 13 triggers are instant, New Comment on Ticket and Tag Added to User. Zendesk tells Zapier the moment they happen, so they start the Zap right away on any plan. The 11 others are polling triggers, checked on a timer set by your plan. If speed matters, build around those two.

What Zapier does not do here: New Action on Ticket follows a single ticket for a non-admin account, and none of the actions deletes a ticket or an organization. For anything missing, API Request (Beta) remains, limited to Zendesk's domains. The same app is also covered on the Zendesk n8n integration and Zendesk Make integration pages.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the whole page. Take them in once, then everything below reads fast.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it: a new ticket, a comment, a tag.
Action
What the Zap does once started: the step that writes, sends or moves something for you, like tagging a ticket.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts only those.
Polling vs instant
Polling: Zapier checks the app on a timer and keeps what is new. Instant: the app calls Zapier the moment the event happens.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Premium app
An app Zapier keeps for paid plans and free trials. Zendesk is one, so the free plan alone will not run it.
Cost

What a Zendesk Zap really costs

Zendesk is a premium app: it needs a paid Zapier plan, or the free trial. The free plan, on its own, does not run it.

  • Premium appYes, paid plan or free trial
  • Instant triggers2 of 13, not tied to the plan grid
  • BilledEach successful action, one task
  • Trigger checksNever billed

Once you are on a paid plan, the logic is simple. The trigger never costs a task, however often Zapier checks your help desk. Each action that succeeds counts as one task, so a Zap with three actions eats three times more than a Zap with one. An action that fails is not counted. A filter or a search makes the Zap multi-step, which paid plans allow. For reference, the free plan gives 100 tasks a month and two-step Zaps, but no premium app.

Connect

Connect your Zendesk account in 3 steps

  1. 01

    Open Apps and start a connection

    In your Zapier account, open the Apps page and click + Add connection. One connection is enough: every Zendesk step you build afterwards can reuse it, in any Zap.

  2. 02

    Find Zendesk and confirm

    Type Zendesk in the search box of the dialog, pick it, then click Add connection. A new tab opens where you sign in to the Zendesk account the Zaps will act on.

  3. 03

    Sign in and grant access

    Sign in, then grant Zapier access to the account. You need a Zendesk account, plus read or write access to the tickets, users or organizations you do not own and still want a Zap to touch.

First Zap

Your first Zap: refund requests tagged on arrival

GoalA software company wants every new ticket about a refund tagged for the billing team, before any agent has to read and reroute it.

  1. 01

    Build: set the trigger

    Start building, pick Zendesk as the app and New Ticket as the event. You can narrow it to one organization if only one customer account matters for this flow.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent tickets of your connected account, so you map the next steps on a real request rather than on a blank form.

  3. 03

    Add a filter

    Click the plus icon, add a Filter and fill its three boxes: the field to look at, a text rule such as contains, and the word refund. A number rule on text never passes.

  4. 04

    Add the action

    Add Zendesk again and choose Add Tag(s) to Ticket. Map Ticket to the ticket the trigger brought back, then pick the billing tag from the list or type it as a custom value.

  5. 05

    Test, then Publish

    Test the action once and open the ticket in Zendesk to see the tag. Then Publish to switch the Zap on. Tickets created before that moment stay untouched.

Triggers

The 13 Zendesk triggers

13 events start a Zap when something happens in Zendesk, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Group

Polling trigger

In Zapier“Triggers when a new group is created.”

Starts the Zap when someone creates a group in Zendesk. Useful when the way your team is organised also lives in another tool.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a support manager opens a new group for a language or a region and wants the rest of the setup to follow from that single gesture.
2

New Tag Added to Ticket

Polling trigger

In Zapier“Triggers when a new tag is added to a ticket.”

You pick one or more tags, and the Zap starts when they land on a ticket. It turns a label an agent already uses into a workflow.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
an agent tags a ticket escalation and the account manager needs to hear about it.
Watch out
the Tags field is required, and with several tags selected the trigger waits until all of them are on the ticket.
3

New Comment on Ticket

Instant trigger

In Zapier“Triggers when a comment is added to a ticket.”

Each comment added to a ticket starts the Zap. It is one of the two triggers of this app that Zendesk reports itself.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a SaaS team that wants a customer's reply on a waiting ticket to reach the assigned engineer without anyone refreshing Zendesk.
Watch out
never pair it with Add Comment to Ticket on the same tickets, or each comment the Zap adds starts it again.
4

New Ticket in View

Polling trigger

In Zapier“Triggers when a new ticket is added to a view.”

Watches one of your Zendesk views and starts the Zap when a ticket enters it. The view does the sorting with its own conditions, so the Zap inherits a selection you already trust.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a view gathers tickets from your largest accounts and each one should open a follow-up somewhere else.
5

New Ticket

Polling trigger

In Zapier“Triggers when a new ticket is created. Optionally select an organization.”

The broad starting point: every ticket created in Zendesk starts the Zap. You can restrict it to one organization when only that customer matters for the flow.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
routing incoming requests by topic with a filter, before an agent has to read and reassign them.
Watch out
without a filter or the organization setting, every single ticket costs at least one task.
6

Tag Added to User

Instant trigger

In Zapier“Triggers when a one or more tags are added to a user.”

One or more tags added to a user profile start the Zap. The second instant trigger of the app, and the one that follows people rather than tickets.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an agent flags a customer as a key account on their profile, and an onboarding ticket should open for the success team straight away.
Watch out
it listens to tags on users only; a tag added to a ticket goes through New Tag Added to Ticket instead.
7

New Organization

Polling trigger

In Zapier“Triggers when a new organization is created.”

Fires when an organization is created in Zendesk. It marks the moment a new customer company exists on the support side.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a B2B support team that wants each new customer company greeted with a welcome ticket and the right tags from day one.
8

New Suspended Ticket

Polling trigger

In Zapier“Triggers when a new suspended ticket is created in Zendesk. Note: Suspended tickets are automatically deleted after 14 days.”

Picks up tickets that Zendesk put in suspension instead of the normal queue.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
making sure a real customer message caught in suspension gets a second look by a human.
Watch out
Zendesk deletes suspended tickets automatically after 14 days, so the Zap is a rescue net, not an archive.
9

New Action on Ticket

Polling trigger

In Zapier“Triggers when there is activity (an audit) on a specific ticket. Non-admins can only watch one ticket at a time.”

Follows the activity on one specific ticket: every change recorded in its audit starts the Zap. Think of it as a close watch on a single case rather than a help desk-wide feed.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a critical incident ticket that management wants to follow move by move.
Watch out
a non-admin account can only watch one ticket at a time with this trigger.
10

Updated Ticket

Polling trigger

In Zapier“Triggers when an existing ticket is updated.”

Any change to an existing ticket starts the Zap. It is the widest net of the app, so a filter behind it keeps the task count under control.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
mirroring ticket progress into a reporting tool that has to stay in step with Zendesk.
Watch out
an Update Ticket action in the same Zap changes the ticket again, which starts the Zap again.
11

Updated Ticket in View

Polling trigger

In Zapier“Triggers when a ticket is updated in the selected view.”

Same idea as Updated Ticket, narrowed to the tickets of one view. The view's conditions filter the noise before Zapier even sees it, which keeps the task count down.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a team lead who follows changes on urgent tickets only, through a view that already holds them.
12

New User

Polling trigger

In Zapier“Triggers when a new user is created.”

Every user created in Zendesk, the profile behind each requester, starts the Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a subscription business that wants every new requester tagged by plan or language as soon as the profile exists.
Watch out
users created in bulk, after an import, can arrive as a large batch that Zapier may hold back.
13

New View

Polling trigger

In Zapier“Triggers when a new view is created.”

Fires when someone creates a view in Zendesk. A new view is a new way of sorting the team's tickets.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
keeping an operations lead informed when someone sets up a new view, so documentation and dashboards follow.
Watch out
views that already exist when the Zap goes live are never sent, only the ones created afterwards.
Actions

The 12 Zendesk actions

Zendesk gives you 12 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Delete User

Action

In Zapier“Deletes the user and associated records from the account.”

Deletes a user and the records attached to them in the account. The Permanent Deletion option goes further and erases all of that person's information immediately, for GDPR requests.

When to use it
processing a confirmed erasure request.
Watch out
testing the step in the editor runs it for real, so point the test at a user created for that purpose.
2

Create Organization

Action

In Zapier“Create a new organization.”

Creates an organization in Zendesk, the record a customer company gets on the support side.

When to use it
a new B2B contract should give support a home for that company right away.
Watch out
to avoid duplicates, Find or Create Organization, a variant of Find an Organization, creates one only when nothing matches.
3

Remove Tag(s) from Ticket

Action

In Zapier“Remove one or more tags from an existing ticket.”

Takes one or more tags off an existing ticket. You choose them from the Zendesk list or type them as a custom value, and the ticket is picked or mapped from an earlier step.

When to use it
clearing a waiting-on-customer tag once the customer has answered, so the ticket leaves that queue.
4

Create Ticket

Action

In Zapier“Create a new ticket.”

Opens a new ticket in Zendesk from whatever started the Zap. The only field it insists on is the first comment, which becomes the description of the request.

When to use it
turning a key-account tag on a user into an onboarding ticket for the success team.
5

Attach File to Ticket

Action

In Zapier“Attach a file to an existing ticket.”

Adds a file to an existing ticket, together with a comment. The ticket, the comment and the file are all three required, so the earlier steps must carry a real file.

When to use it
putting a generated invoice or a signed form straight on the customer's ticket.
6

Add Comment to Ticket

Action

In Zapier“Add a Comment to an existing Ticket.”

Writes a comment on an existing ticket that you pick or map from an earlier step. Handy for leaving a trace of what an automation did.

When to use it
recording on the ticket that a refund was processed elsewhere.
Watch out
paired with New Comment on Ticket on the same tickets, it loops.
7

Add Tag(s) to Ticket

Action

In Zapier“Add one or more tags to an existing ticket.”

Puts one or more tags on an existing ticket. You pick them from your Zendesk list or type a custom value.

When to use it
routing refund tickets to the billing queue the moment they arrive.
Watch out
a tag watched by New Tag Added to Ticket in another Zap will start that Zap too.
8

Update Organization

Action

In Zapier“Update an existing organization.”

Edits an existing organization, looked up by its ID. Find an Organization placed before it provides that ID without anyone copying numbers by hand.

When to use it
a company's contract details change and the support side should reflect them.
9

Update Ticket

Action

In Zapier“Update an existing ticket status or add comments.”

Changes the status of an existing ticket or adds a comment to it, and lets you decide whether that comment is public or internal.

When to use it
posting an internal note on escalated tickets so the next agent sees the procedure.
Watch out
with Updated Ticket as the trigger, this action restarts the Zap it belongs to.
10

Update User

Action

In Zapier“Update an existing user.”

Changes the details of an existing user, found by their ID. In practice, a Find a User step placed just before it supplies that ID, so nobody copies numbers from Zendesk by hand.

When to use it
a customer changes plan in billing and their Zendesk profile should say so.
11

Create User

Action

In Zapier“Create a new user.”

Adds a new user to Zendesk, so the person exists before their first ticket does. Pair it with Find a User to avoid duplicates.

When to use it
new customers should already be known to support on the day they sign up.
12

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

The advanced exit: a raw HTTP request to Zendesk that reuses the authentication of your connection. HTTP Method, URL and Stop on error are required.

When to use it
a developer needs a Zendesk call none of the other actions offers.
Watch out
only Zendesk's own domains are accepted.
Searches

The 7 Zendesk searches

7 search steps look for data that already exists in Zendesk, so a later step can use it.

In the editor, searches sit at the bottom of the Action event list, under the SEARCH heading. Some action fields also show + Add search step, which inserts the right search just before and wires its result in. Whether a search wants an exact value or something close is decided by Zendesk, not Zapier. Three settings decide what happens next.

1

Find an Agent

Search

In Zapier“Finds an existing agent.”

Looks up an agent from a search string you write in the required Query field, then hands that agent to the next steps.

When to use it
a Zap needs the agent behind a name or an email before mentioning them in an internal comment.
2

Find Ticket Comments

Search

In Zapier“Finds all comments on a ticket.”

Brings back every comment of a ticket, the full conversation rather than its last line.

When to use it
handing the whole exchange to a later step that summarizes or archives it.
Watch out
on long tickets, that is a lot of text to map.
3

Find Tickets

Search

In Zapier“Finds existing tickets. Returns multiple results as individual items.”

Finds existing tickets and returns each match as a separate item, so the following steps can treat them one by one.

When to use it
checking whether a customer already has an open request before creating another.
Watch out
pair it with the multiple-results setting below.
4

Find a Group

Search

In Zapier“Finds an existing group.”

Locates an existing group from a search string written in the required Query field. Whether that string must match exactly is up to Zendesk.

When to use it
a Zap that sends tickets to a team needs that group's identity first, without anyone hardcoding it in the step.
5

Find Latest Comment

Search

In Zapier“Finds the latest comment on a ticket.”

Fetches only the most recent comment of a ticket, the line that usually says where things stand.

When to use it
a status update in another tool should quote what was last said to the customer, not the whole history.
6

Find an Organization

SearchFind or create

In Zapier“Finds an existing organization.”

Finds an existing organization from a search string in the required Query field. Its find-or-create variant, Find or Create Organization, is this same search with the create box ticked: when nothing matches, it creates the organization.

When to use it
attaching a new ticket to the right customer company.
7

Find a User

SearchFind or create

In Zapier“Finds an existing user.”

Your way to an existing user: a search string in the required Query field. Find or Create User is the same search with the create box ticked, and it adds the person when nobody matches.

When to use it
feeding Update User the ID it needs, or making sure each requester exists exactly once.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switched on, the Zap goes on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When a Zendesk Zap breaks

Most of these cases come from Zendesk's own rules, the rest from how Zapier watches an app.

Check these six cases before anything else. If a Zap still misbehaves, the Zapier troubleshooting page walks through the method, and a Zapier agency can take over the harder builds.

  • Suspended tickets vanish

    Zendesk deletes suspended tickets automatically after 14 days. A Zap on New Suspended Ticket has to act before then, or there is nothing left to rescue.

  • Only one ticket is watched

    With New Action on Ticket, a non-admin account can watch one ticket at a time. Connect an admin account if you need more.

  • The tag trigger stays silent

    With several tags selected, New Tag Added to Ticket waits until all of them are on the ticket. Use one tag per Zap when any of them should count.

  • The Zap feeds itself

    Updated Ticket plus Update Ticket, or New Comment on Ticket plus Add Comment to Ticket: the Zap changes what it watches and restarts, burning tasks fast.

  • A deleted user is gone

    Testing Delete User in the editor runs it for real, and Permanent Deletion erases the person's information immediately. Point the test at a user made for it.

  • Old tickets are ignored

    A Zap only reacts to what happens after you publish it. Existing tickets are never picked up; moving that backlog is a separate job.
Need help

Need help automating Zendesk with Zapier?

A person reads every message.

FAQ

Zendesk and Zapier: the questions people ask

01Is the Zendesk Zapier integration free?
No. Zendesk is a premium app on Zapier, which means it is reserved for paid plans and for the free trial. The free plan, with its 100 tasks a month, does not include premium apps at all. Once you are on a paid plan, multi-step Zaps open up too, so a filter or a search step costs nothing extra in plan terms. Plan names to look for on Zapier: Professional, Team and Enterprise.
02How many tasks does a Zendesk Zap use?
One task per action that succeeds, nothing else. The trigger is free, and so are the checks Zapier runs on your help desk, however often they happen. A Zap that tags each new ticket costs one task per ticket. A Zap that finds a user, updates them and comments on a ticket costs one task for each completed action. An action that fails is not counted. Note that a few apps and actions take more than one task when they complete.
03Does Zendesk start a Zap the moment something happens?
For 2 of its 13 triggers, yes: New Comment on Ticket and Tag Added to User are instant, Zendesk reports them to Zapier as they happen, on any plan. The 11 others are polling triggers. Zapier checks for new items at an interval set by your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. The type comes from Zendesk's API and cannot be changed in the editor. On paid plans you can adjust the check frequency and run a check by hand while testing.
04What does connecting Zendesk to Zapier require?
A Zendesk account, plus read or write access to any tickets, users or organizations you do not own and want a Zap to touch. Then three moves: open the Apps page of your Zapier account and click + Add connection, search Zendesk in the dialog and confirm with Add connection, sign in to Zendesk in the tab that opens and grant access. The connection is then reused by every Zendesk step. If your Zaps follow ticket activity with New Action on Ticket, prefer an admin account for the connection.
05Why does a suspended ticket never reach the Zap?
Likely because it was gone before the Zap could act on it. Zendesk deletes suspended tickets automatically after 14 days, and the New Suspended Ticket trigger is a polling one, so Zapier only sees what is still there when it checks. A Zap published after the ticket was suspended will not pick it up either, since a Zap never processes what existed before it was switched on. Publish the rescue Zap first, then let it handle new suspensions as they come.
06What if the Zendesk operation you need is not in the list?
Use API Request (Beta), the advanced action at the end of the list. It sends a raw HTTP request to Zendesk with the authentication of your existing connection, so there is no key to handle yourself. You choose the HTTP Method and the URL, and set Stop on error: Yes stops the step when Zendesk returns an error and enables automatic authentication refresh, No lets the Zap go on regardless. Only Zendesk's own domains are accepted. Plan for someone at ease with API documentation.
07Zapier, Make or n8n for Zendesk?
It depends on three criteria rather than on a winner. Operations: compare the 13 triggers, 12 actions and 7 searches listed here with what each other tool offers for Zendesk. Cost model: on Zapier, Zendesk is a premium app, so a paid plan is needed from the first Zap. Freshness: on Zapier, two triggers are instant and the rest wait for the interval of your plan. Weigh those three points against your own help desk before choosing, and read each tool's Zendesk page side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations