Zendesk Support

Read and write Zendesk tickets, comments, users and organizations, plus fields, CSAT, macros, views and Help Center articles.

Keep support tickets, customers and satisfaction data aligned with CRM, commerce and operations systems.

Build a flow with Zendesk Support Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

articles

List Help Center articles
Source
Help Center (Guide) articles with section, labels and locale.

groups

List groups
Source
Agent groups used for ticket routing.

macros

List macros
Source
Macros with their actions, for reference in flows.

organizations

Create organization
Destination
Duplicate protected
Creates an organization. Zendesk requires organization names to be unique.
List organizations
Source
Organizations with domains, tags and organization fields.
Update organization
Destination
Duplicate protected
Updates an organization's name, domains, tags and organization fields.
Create or update organization
Destination
Duplicate protected
Creates an organization, or updates the one with this external ID.

satisfaction ratings

List satisfaction ratings
Source
Incremental
CSAT ratings with score, comment, reason and the rated ticket.

ticket comments

Add ticket comment
Destination
Not retried automatically
Adds a public reply (emailed to the requester) or an internal note through a ticket update.
List ticket comments
Source
Public replies and internal notes on a ticket, oldest first.

ticket fields

List ticket fields
Source
System and custom ticket fields with types and drop-down options.

tickets

Create ticket
Destination
Duplicate protected
Creates a ticket with a first comment, requester, fields and tags.
Get ticket
Source
A ticket with custom fields, tags and channel.
List tickets
Source
Incremental
Tickets in update order. With Updated since, uses the cursor-based incremental ticket export.
Search tickets
Source
Tickets matching a Zendesk search query, using the cursor-based search export.
Update ticket
Destination
Duplicate protected
Updates status, priority, assignee, group, tags and custom fields without adding a comment.

user fields

List user fields
Source
Custom user fields with keys, types and options.

users

Get user
Source
A user with user fields, tags and organization.
List users
Source
Incremental
End users, agents and admins. With Updated since, uses the cursor-based incremental user export.
Search users
Source
Users matching a search query (name or email) or an exact external ID.
Update user
Destination
Duplicate protected
Updates a user's profile, organization, tags and user fields.
Create or update user
Destination
Duplicate protected
Creates a user, or updates the user that already has this email.

views

List views
Source
Ticket views with their conditions.

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.

Provider events

Zendesk webhooks with triggers, automations and event subscriptions. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Ticket deletion, merging and user or organization deletion are not implemented.
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 are read-only.