Zendesk Support
Send the right update through Zendesk Support at the right moment, with a person approving what reaches customers.
48 ways to read, 13 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Zendesk Support, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Add agent to group
group_memberships.createApproval by rule - Create group
groups.createApproval by rule - List Help Center articles
articles.listRead
Example flow
- AfterShip Tracking · Read trackings
trackings.listDone - Zendesk Support · Create ticket
tickets.createMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Zendesk Support.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Zendesk Support
- Zendesk Support's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read, filter and write Zendesk tickets, comments, tags, users, organizations, groups and memberships, plus audits, metrics, forms, CSAT, rules and Help Center content.
Zendesk API docs- Source actions
- 48
- Destination actions
- 13
- Data types
- 33
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
articles2
- Get Help Center articleSource
One Help Center (Guide) article.
- List Help Center articlesSource
Help Center (Guide) articles with section, labels and locale.
automations1
- List automationsSource
Time-based automations with conditions and actions (read only).
brands2
- Get brandSource
One brand.
- List brandsSource
Brands with subdomain, host mapping and Help Center status.
current user1
- Get API userSource
The agent or admin whose credential this connection uses.
custom statuses1
- List custom ticket statusesSource
Custom ticket statuses with their category and labels.
filtered tickets1
- Filter ticketsSourceIncremental
Tickets matching validated filters (status, priority, type, group, assignee, requester, organization, brand, tag, channel, dates and custom fields). No free-form query.
group memberships2
- Add agent to groupDestinationNot retried automaticallyApproval before production
Adds an agent to a group.
- List group membershipsSource
Which agents belong to which groups.
groups4
- Create groupDestinationNot retried automaticallyApproval before production
Creates an agent group.
- Get groupSource
One agent group.
- List groupsSource
Agent groups used for ticket routing.
- Update groupDestinationProvider duplicate protectionApproval before production
Renames a group or changes its description or visibility.
help center categories1
- List Help Center categoriesSource
Help Center categories.
help center sections1
- List Help Center sectionsSource
Help Center sections, optionally in one category.
macros2
- Get macroSource
One macro with its actions.
- List macrosSource
Macros with their actions, for reference in flows.
organization fields1
- List organization fieldsSource
Custom organization fields with keys, types and options.
organization memberships2
- Add user to organizationDestinationNot retried automaticallyApproval before production
Adds a user to an organization (users can belong to several on some plans).
- List organization membershipsSource
Links between users and organizations.
organization tickets1
- List organization ticketsSource
Tickets requested by members of an organization.
organization users1
- List organization usersSource
Users who belong to an organization.
organizations6
- Create organizationDestinationProvider duplicate protectionApproval before production
Creates an organization. Zendesk requires organization names to be unique.
- Get organizationSource
An organization with domains, tags and organization fields.
- List organizationsSource
Organizations with domains, tags and organization fields.
- Find organizationSource
Organizations with an exact external ID or name.
- Update organizationDestinationProvider duplicate protectionApproval before production
Updates an organization's name, domains, tags and organization fields.
- Create or update organizationDestinationProvider duplicate protectionApproval before production
Creates an organization, or updates the one with this external ID.
satisfaction ratings2
- Get satisfaction ratingSource
One CSAT rating.
- List satisfaction ratingsSourceIncremental
CSAT ratings with score, comment, reason and the rated ticket.
sla policies1
- List SLA policiesSource
SLA policies with their filters and targets (Professional and above).
tags1
- List tagsSource
Most-used tags with their usage counts.
ticket audits1
- List ticket auditsSource
The change history of a ticket (field changes, comments, notifications).
ticket comments2
- Add ticket commentDestinationNot retried automaticallyApproval before production
Adds a public reply (emailed to the requester) or an internal note through a ticket update.
- List ticket commentsSource
Public replies and internal notes on a ticket, oldest first.
ticket fields2
- Get ticket fieldSource
One ticket field with type and options.
- List ticket fieldsSource
System and custom ticket fields with types and drop-down options.
ticket forms2
- Get ticket formSource
One ticket form.
- List ticket formsSource
Ticket forms with their fields and brands.
ticket metrics2
- Get ticket metricsSource
Reply, resolution and wait times for one ticket.
- List ticket metricsSource
Reply, resolution and wait times for all tickets.
ticket tags2
- Add ticket tagsDestinationProvider duplicate protectionApproval before production
Adds tags to a ticket without removing existing ones.
- List ticket tagsSource
Tags on one ticket.
tickets5
- Create ticketDestinationProvider duplicate protectionApproval before production
Creates a ticket with a first comment, requester, fields and tags.
- Get ticketSource
A ticket with custom fields, tags and channel.
- List ticketsSourceIncremental
Tickets in update order. With Updated since, uses the cursor-based incremental ticket export.
- Search ticketsSource
Tickets matching a Zendesk search query, using the cursor-based search export.
- Update ticketDestinationProvider duplicate protectionApproval before production
Updates status, priority, assignee, group, tags and custom fields without adding a comment.
triggers1
- List triggersSource
Ticket triggers with conditions and actions (read only).
user fields1
- List user fieldsSource
Custom user fields with keys, types and options.
user identities1
- List user identitiesSource
A user's email addresses, phone numbers and social identities.
user tickets1
- List user ticketsSource
Tickets a user requested, is assigned or is copied on.
users5
- Get userSource
A user with user fields, tags and organization.
- List usersSourceIncremental
End users, agents and admins. With Updated since, uses the cursor-based incremental user export.
- Search usersSource
Users matching a search query (name or email) or an exact external ID.
- Update userDestinationProvider duplicate protectionApproval before production
Updates a user's profile, organization, tags and user fields.
- Create or update userDestinationProvider duplicate protectionApproval before production
Creates a user, or updates the user that already has this email.
view tickets1
- List view ticketsSource
Tickets currently in a view, using the view's conditions.
views2
- Get viewSource
One view with its conditions.
- List viewsSource
Ticket views with their conditions.
Access and limits
- Authentication
- Agent email and API token, or an OAuth access token
- Plans and access
- All Zendesk Suite and Support plans; Help Center articles need Guide. Results follow the role of the agent or admin who owns the API token or OAuth token. Incremental exports and user management need an admin.
- Test environment
- Zendesk trials and sponsored developer accounts can be used; Enterprise plans include sandboxes.
- Rate limits
- Plan-based per-minute limits (for example 200–700 requests per minute; 2,500 with High Volume); incremental exports 10 requests per minute; HTTP 429 with Retry-After.
- Pagination
- Cursor pagination with page[size] up to 100 and meta.after_cursor; incremental exports use after_cursor until end_of_stream.
- Provider events
- Zendesk webhooks with triggers, automations and event subscriptions. Flows can start the moment something happens: when a Zendesk ticket is created; when a ticket's status changes; when a comment is added to a ticket; when a new Zendesk user is created.
Before you build a flow
- Ticket, user, organization, group, membership and tag deletion, ticket and organization merging, spam marking, user suspension and identity changes are intentionally not implemented.
- Bulk and many-record endpoints (create_many, update_many, ticket imports) and outbound customer sends beyond the existing Add ticket comment are excluded. Trigger, automation, view, macro, SLA, form, field and brand configuration is read-only.
- The existing Search tickets and Search users operations accept a free-form query that Zendesk only takes in the URL query string, so a mapped email or name reaches the URL.
- Filter tickets returns at most the results Zendesk's search export allows and can lag recent changes by a few minutes.
- Attachment metadata is read; files are not uploaded or downloaded.
- Incremental exports need an admin and require start times at least one minute in the past.
- Ticket creation uses the Idempotency-Key header (keys expire after two hours); comments, organization creates by name and other writes are not repeated automatically when uncertain.
- Help Center articles, sections and categories are read-only.
- Ticket metrics, audits, organization tickets and view tickets use cursor pagination where Zendesk supports it; endpoints that ignore page[size] return their first page.
Developer reference
- Create the Zendesk credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Zendesk Support, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/zendesk and the Connections API.