How does the Zendesk Trigger pick events?

It has no event list. You set conditions on ticket fields (Assignee, Group, Priority, Status, Type) with operators like Changed, Changed To, Is and Is Not; n8n creates the matching webhook and trigger in Zendesk.

Why did my tags disappear after Update Ticket?

The n8n docs warn that Update with Tag Names or IDs replaces all tags on the ticket. Read the tags first and merge, or call the tags endpoint (or additional_tags) with HTTP Request.

Do Zendesk steps convert automatically?

No. They arrive as placeholders with their props (ticket ID, subject, comment, custom fields), and the report lists the Zendesk credential to create.

Zendesk in n8n: API token or OAuth2?

Both work. The API token needs Token access turned on in Admin Center → Apps and integrations → APIs → Zendesk APIs, plus your subdomain and agent email.

Pipedream Zendesk steps in n8n

Updated 2026-10-21 · 3 min read · n8n: Zendesk (Native n8n node)

Zendesk workflows in Pipedream mostly route tickets: a new ticket goes to Slack, an urgent one pages someone, a form creates a ticket, an LLM drafts a reply. n8n has a native Zendesk node and a Zendesk Trigger, but the trigger is configured differently.

The n8n side

Zendesk node (n8n-nodes-base.zendesk):

Resource	Operations
Ticket	Create, Delete, Get, Get All, Recover (suspended), Update
Ticket Field	Get, Get All
User	Create, Delete, Get, Get All, Get Organizations, Get Related Data, Search, Update
Organization	Create, Delete, Count, Get, Get All, Get Related Data, Update

Zendesk Trigger (service: Support) does not offer named events. You build conditions, All or Any, on Assignee, Group, Priority, Status and Type with operators such as Changed, Changed To, Is, Is Not. On activation n8n creates the webhook and a Zendesk trigger that calls it.

What maps where

Pipedream (app `zendesk`)	In n8n	Status
Create Ticket	Ticket → Create	manual
Update Ticket, Set Custom Ticket Fields	Ticket → Update	manual
Add Ticket Tags	HTTP Request → tags endpoint (not Update, see below)	manual
Search Tickets	Ticket → Get All with a query, or HTTP Request → search	manual
Get Ticket Info, Get User Info	Ticket → Get, User → Get	manual
List Ticket Comments	HTTP Request → ticket comments	manual
New Ticket (Instant)	Zendesk Trigger, condition Status Is New (or Changed)	manual
Ticket Updated / Solved / Closed (Instant)	Zendesk Trigger with Status Changed To Solved / Closed	manual
New Ticket Comment Added (Instant)	Zendesk Trigger + filter, or a Zendesk webhook to an n8n Webhook	manual

Zendesk actions are not in the converter's mapped list; each step is a placeholder that keeps its props in a comment, and the trigger becomes a Manual Trigger naming the Pipedream source.

Zendesk credentials in n8n

API token: subdomain, agent email, token. Turn on Token access in Admin Center first.
OAuth2: register an OAuth client in Zendesk; useful when several Zendesk accounts connect.

Typical migration: urgent tickets to Slack

Pipedream: Zendesk New Ticket (Instant) → filter priority → Slack Send Message to Channel. n8n: Zendesk Trigger with conditions Priority Is Urgent → Slack → Message → Send. The filter step disappears because the condition lives in the trigger.

Zendesk migration pitfalls

Tags get replaced. Ticket → Update with Tag Names or IDs overwrites the whole tag list. Use HTTP Request (PUT /api/v2/tickets/{id}/tags adds tags) or merge before updating.
Rate limits. Support API: 200 requests per minute on Team, 400 on Growth and Professional, 700 on Enterprise, 2,500 on Enterprise Plus or with the High Volume add-on. Updates are also capped at 30 per 10 minutes per user per ticket, so a loop that edits one ticket repeatedly fails fast.
Leftover triggers. Pipedream's sources created webhooks and triggers in Zendesk. Delete them in Admin Center after the switch, or both platforms fire.
Custom fields use numeric field IDs. Ticket Field → Get All lists them.

How to move your Zendesk workflows

Export the workflows from Pipedream.
Upload on /convert; the free report lists every Zendesk step with its props and the credential.
Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide. Related: Freshdesk, Intercom, Slack.

FAQ

How does the Zendesk Trigger pick events?: It has no event list. You set conditions on ticket fields (Assignee, Group, Priority, Status, Type) with operators like Changed, Changed To, Is and Is Not; n8n creates the matching webhook and trigger in Zendesk.
Why did my tags disappear after Update Ticket?: The n8n docs warn that Update with Tag Names or IDs replaces all tags on the ticket. Read the tags first and merge, or call the tags endpoint (or additional_tags) with HTTP Request.
Do Zendesk steps convert automatically?: No. They arrive as placeholders with their props (ticket ID, subject, comment, custom fields), and the report lists the Zendesk credential to create.
Zendesk in n8n: API token or OAuth2?: Both work. The API token needs Token access turned on in Admin Center → Apps and integrations → APIs → Zendesk APIs, plus your subdomain and agent email.