How to Connect n8n to Zendesk: Complete Integration Guide (2025)
Zendesk is where your support conversations live, but a lot of the work around those tickets — tagging, routing, enriching, notifying the right person — is still manual. n8n lets you wire Zendesk to the rest of your stack so those steps happen the moment a ticket is created or updated.
This guide walks you through connecting n8n to Zendesk from scratch: getting credentials, setting up the trigger, and building your first three practical automations. No prior n8n experience required.
What you can automate between n8n and Zendesk
Once the connection is live, the Zendesk node in n8n can read and write almost anything the Zendesk API exposes. The most common wins teams build first:
- Auto-tag and categorize incoming tickets by content, so routing rules fire correctly.
- Escalate high-priority or angry tickets to Slack or a manager instantly.
- Enrich a ticket with CRM data (deal size, plan tier) the moment it arrives.
- Sync ticket status changes to Pipedrive, HubSpot, or a Google Sheet.
- Trigger a satisfaction survey or NPS request when a ticket is solved.
Step 1 — Get your Zendesk API credentials
Zendesk uses API token authentication. In your Zendesk Admin Center, go to Apps and integrations → APIs → Zendesk API and enable Token access. Click Add API token, give it a label like n8n, and copy the token — you only see it once. You'll authenticate in n8n with three pieces of information:
- Your subdomain — the part before
.zendesk.comin your account URL. - The email address of the agent whose token you generated.
- The API token itself.
Step 2 — Add the Zendesk credential in n8n
In n8n, add a Zendesk node to a workflow. When it asks for credentials, choose Create new and select API Token auth. Enter your subdomain, agent email (n8n appends /token automatically), and the token. Click Save — n8n test-calls the API and confirms the connection. If you self-host n8n, no extra network config is needed; Zendesk's API is public HTTPS. Just make sure the API token hasn't been scoped away from the resources you need.
Tired of agents copy-pasting the same answers?
This template auto-answers Tier-1 tickets with RAG and escalates only what needs a human — inside Zendesk.
Step 3 — Trigger on new or updated tickets
You have two options. The simplest is the Zendesk Trigger node, which registers a webhook in your Zendesk account and fires the instant a ticket is created or updated — real-time, no polling. If you're on a Zendesk plan without outbound webhooks, use a Schedule Trigger plus the Zendesk node's Get Many Tickets operation with a filter like updated>{{last run}}. It's a few minutes slower but works everywhere. From the trigger, the full ticket JSON flows downstream — subject, description, requester, tags, priority — ready to branch on with an IF or Switch node.
Step 4 — A practical first workflow: auto-triage
Here's a complete pattern you can build in ten minutes:
- Zendesk Trigger — fires on new ticket.
- AI node (OpenAI/Claude) — classify the ticket into a category and urgency from the subject and body.
- Switch — route by category.
- Zendesk node (Update Ticket) — apply the tag and set priority.
- Slack node — if urgency is high, ping the on-call channel with a link to the ticket.
That single flow removes the manual triage step that eats your first-response time every morning.
Common errors and how to fix them
- 401 Unauthorized — the email is missing the
/tokensuffix or the token was revoked. Recreate the credential. - 403 Forbidden — the agent role can't touch that resource. Use an admin-level agent for the token.
- 422 on update — you sent a field Zendesk doesn't accept (e.g., a custom field ID that doesn't exist). Check the field IDs in Admin Center.
- Trigger never fires — the webhook was created but your ticket update didn't match the condition. Test with a brand-new ticket first.
Frequently asked questions
Is the Zendesk node free in n8n?
Yes. The Zendesk node ships with n8n core, on both cloud and self-hosted. You only pay for your Zendesk plan and (if you self-host) your server.
Can n8n reply to tickets automatically?
Yes — the Zendesk node can add public or internal comments. Pair it with an AI node and a knowledge base for genuine auto-responses, then escalate anything low-confidence to a human.
Does this work with Zendesk Sell (CRM)?
The Zendesk node targets Zendesk Support. For Zendesk Sell, use the HTTP Request node against the Sell API with the same token approach.
Ready to automate this?
Skip the build. The Tier-1 Support Automation template is ready to import into n8n — plug in your credentials and it runs. One-time purchase, yours forever, no subscription.
