Zendesk automations
Support · 6 integrations
Automating Zendesk typically means routing tickets to the right teams, syncing customer data with CRMs like Salesforce or HubSpot, and triggering notifications in tools like Slack when support conditions are met. Because support volume is unpredictable and SLAs are time-sensitive, teams automate Zendesk to eliminate manual triage and keep customer records consistent across platforms. The platform's API has meaningful rate limits and webhook reliability quirks that matter a lot at scale.
What it costs to automate Zendesk
Platform pricing at different volumes. Annual billing shown.
| Platform | Free tier | 100 tasks/mo | 1K tasks/mo | 10K tasks/mo |
|---|---|---|---|---|
| Zapier | 100 tasks/mo | Free | $69/mo | $69+/mo |
| Power Automate | 750 runs/mo | Free | $15/mo | $15/mo |
| Make | 1,000 credits/mo | Free | Free | $10.59/mo |
| Pipedream | 100 credits/mo | Free | $29/mo | $79/mo |
| n8n | Yes | $20/mo | $20/mo | $50/mo |
Zendesk integrations
Each page compares all five platforms for that pair.
Zendesk triggers & actions by platform
Which capabilities each platform supports for Zendesk.
| Capability | Pipedream | Zapier | Power Automate | Make | n8n |
|---|---|---|---|---|---|
| Triggers | |||||
| Salesforce Webhook | ✓ | — | — | ✓ | ✓ |
| New Ticket | — | ✓ | — | ✓ | — |
| Zendesk Webhook | ✓ | — | — | — | ✓ |
| Apollo Webhook | ✓ | — | — | — | — |
| App Event Source | ✓ | — | — | — | — |
| Attio Record Updated | — | — | — | — | ✓ |
| Deal Property Change (Instant) | — | ✓ | — | — | — |
| Deal Stage Changed | ✓ | — | — | — | — |
| Deal Stage Updated | — | ✓ | — | — | — |
| Deal Updated | — | — | — | — | ✓ |
| When a ticket is created (Zendesk) | — | — | ✓ | — | — |
| When an HTTP request is received | — | — | ✓ | — | — |
| Actions | |||||
| Create Zendesk Ticket | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create Ticket | — | ✓ | — | ✓ | ✓ |
| Create Note | — | ✓ | — | — | ✓ |
| Create Record | ✓ | — | — | ✓ | — |
| Create/Update Contact | — | — | — | ✓ | ✓ |
| HTTP Request | ✓ | — | ✓ | — | — |
| Send Message | ✓ | — | — | ✓ | — |
| Update Salesforce Record | — | — | ✓ | ✓ | — |
| Update Ticket | — | ✓ | — | ✓ | — |
| Add Comment to Ticket | — | ✓ | — | — | — |
Things to know about automating Zendesk
API Rate Limits by Plan
Zendesk enforces per-minute rate limits that vary by plan: ~200 req/min on Team, ~400 on Professional, ~700 on Enterprise, and 2,500 on Enterprise Plus (built-in). If you're on Growth or Support Professional and need higher throughput, the High Volume API add-on (minimum 10 agent seats) bumps you to 2,500 req/min for an additional fee.
Endpoint-Specific Sublimits
Beyond the account-wide limit, specific endpoints have their own stricter caps: the Search API is capped at 100 req/min per account, Incremental Export endpoints allow only 10 req/min (30 with the High Volume add-on), and the same ticket can only be updated 30 times within a 10-minute window by the same agent. Automations that hit Search or Incremental Export frequently will run into these sublimits well before the account-wide cap.
Webhook Circuit Breaker Risk
Zendesk's webhook system includes a circuit breaker: if 70% of webhook requests fail within a 5-minute window, or if 1,000+ errors occur in 5 minutes, Zendesk stops sending webhooks entirely. Once tripped, the webhook must be manually reactivated — there are no failure notifications, and webhook logs are only retained for 7 days.
Tag Updates Replace, Not Append
When using n8n's Zendesk node to update ticket tags, specifying any tag values will replace the entire tag list on the ticket — existing tags not included in the update are silently deleted. Workflows that add a single tag without first fetching and re-submitting all existing tags will cause data loss without any error message.
OAuth vs. API Token Auth
Password-based authentication was permanently disabled on January 12, 2026, so any workflow using email/password credentials is now broken. API tokens support up to 256 tokens per account and can impersonate any user including admins — OAuth 2.0 with refresh tokens is recommended for production integrations on Zapier, Make, n8n, Power Automate, and Pipedream.
Zapier Trigger Reliability Caveat
The Zapier 'Recent Ticket' trigger only fires for tickets that appear in Zendesk's built-in 'Recent Tickets' view — tickets filtered out of that view will never trigger the Zap. Additionally, if a required field (like the first comment body) is empty in the incoming event, Zendesk will block Zapier from creating the ticket and the Zap will error rather than skip.
What breaks at scale
At ~400 req/min on a Professional plan, any automation workflow that triggers an API call per ticket event — creating records in a CRM, updating a field, posting to Slack — will exhaust the account-wide rate limit and return 429 errors. What makes this painful is that Zapier, Make, n8n, Power Automate, and Pipedream all pull from the same quota simultaneously, so a busy Slack notification workflow can starve a critical ticket-routing automation. The Search API sublimit of 100 req/min will be hit even earlier if any workflow uses search-based lookups to find existing records.
If the receiving endpoint — your n8n instance, a Make scenario webhook URL, or a Pipedream HTTP trigger — goes down for more than a few minutes during a high-traffic period and 70% of Zendesk's outbound webhook requests fail, the circuit breaker trips and Zendesk stops sending events entirely. There are no failure notifications, webhook logs only go back 7 days, and any events that occurred during the outage are permanently lost since Zendesk does not queue undelivered webhooks. Reactivation is manual, meaning every minute of unnoticed downtime equals missed ticket events.
The Incremental Export endpoint — the standard way to pull large ticket datasets — is limited to 10 requests per minute (30 with the High Volume add-on), and each response returns a maximum of 1,000 records. A sync of 50,000 tickets could take over 80 minutes and will fail midway if the automation platform times out or the OAuth token expires during the job. On self-hosted n8n, loading large result sets into memory without using the 'Split in Batches' node has caused out-of-memory crashes in Docker environments, silently halting the sync partway through with no clear error in the workflow log.
Frequently asked questions
What is the Zendesk API rate limit for automation platforms like Zapier and Make?
Zendesk enforces per-minute rate limits that depend on your plan: around 200 req/min on Team, 400 on Professional, 700 on Enterprise, and 2,500 on Enterprise Plus. All automation platforms — Zapier, Make, n8n, Power Automate, and Pipedream — share this same account-wide limit, so if multiple workflows run simultaneously they compete for the same quota. Hitting the limit returns a 429 error with a Retry-After header indicating how long to wait.
Why are my Zendesk webhooks failing or stopping unexpectedly?
Zendesk webhooks have a 12-second timeout, retry up to 5 times on certain failure codes, and will trip a circuit breaker if 70% of requests fail within 5 minutes or 1,000+ errors accumulate — after which the webhook stops firing and must be manually reactivated. Transient server errors that don't meet the retry criteria result in permanently lost events with no notification. This affects any platform receiving Zendesk webhooks, including Zapier, Make, n8n, Power Automate, and Pipedream.
How do I sync Zendesk tickets with Salesforce or HubSpot automatically?
All five major automation platforms — Zapier, Make, n8n, Power Automate, and Pipedream — support Zendesk-to-CRM syncs using trigger-based workflows that fire when tickets are created or updated. The main reliability consideration is that Zendesk's 'ticket updated' triggers can race with Zendesk's own internal business rules (Triggers), which may modify the same ticket simultaneously and cause conflicts. For high-volume syncs, watch the Incremental Export endpoint limit of 10 req/min, as bulk historical syncs will exhaust this quickly.
Is it safe to use Zendesk API tokens with automation tools?
API tokens are the simplest authentication method supported by Zapier, Make, n8n, Power Automate, and Pipedream, but they carry elevated risk because a single token can impersonate any account user including admins. Zendesk allows up to 256 tokens per account, and password-based auth was permanently removed in January 2026. For production integrations serving multiple customers, Zendesk's developer terms require OAuth 2.0 — sharing API tokens across customers is explicitly prohibited.