Mattering Automations Zendesk integration
Connect Zendesk to Mattering Automations: tickets with replies and internal notes, unified search with an uncapped export, users, organizations, macros, views, and incremental exports as workflow steps, authenticated with an account subdomain, agent email, and API token.
The Mattering Automations Zendesk integration adds Zendesk Support to your automation canvas: list, search, create, and update tickets, add public replies or internal notes, manage users and organizations, execute views, preview macros, append and remove tags, read triggers, automations, satisfaction ratings, and ticket fields, and mirror tickets, users, and organizations at scale with cursor-based incremental exports.
Setup takes a few minutes: enable token access and create an API token in Zendesk Admin Center, attach it as a credential in Mattering together with your subdomain and agent email, and test the connection. This guide walks through each step and ends with the full node reference.
The integration is deliberately conservative with data. Its only destructive node, Zendesk: Delete Ticket, is a soft delete with a 30-day recovery window, and the recovery loop ships alongside it as Zendesk: List Deleted Tickets and Zendesk: Restore Deleted Ticket; permanent deletion is not offered. User deletion is not offered either, because Zendesk documents it as not recoverable, so Zendesk: Suspend or Unsuspend User is the reversible alternative. Macro applies are previews, and business rules are read-only.
Before you start
- A Zendesk Support account and its subdomain: the first part of your Zendesk URL, for example examplecorp for examplecorp.zendesk.com. API tokens are available on paid plans, and Zendesk offers a free trial.
- Admin access to Zendesk Admin Center, to enable API token access and create a token.
- An agent or admin email address to pair with the token. A dedicated integration agent is recommended, because the token acts as that person with their permissions.
- A Mattering workspace with access to the Automations app.
Create a Zendesk API token
Mattering authenticates to Zendesk with an API token paired with an agent email, sent over HTTP Basic auth using Zendesk's email/token convention against your account's subdomain. That means the credential has three parts: the account subdomain, the agent email, and the token. Mattering stores them in two fields: the username holds the subdomain and email joined with a pipe character, and the password holds only the token.
Connect Zendesk to Mattering
Verify it works
After connecting, open any automation canvas and check the palette: a Zendesk section should list the query and action nodes. Drop Zendesk: Get Current User onto the canvas and run a test step. It takes no parameters, and a healthy response shows the integration agent's name, email, and role with a non-null user id. If the response comes back with an anonymous user instead, the credential is wrong even though the status was 200; see troubleshooting.
To confirm the wider surface, run Zendesk: List Ticket Fields to see the account's ticket schema with every custom field and dropdown option, or Zendesk: Count Search Results with a query such as type:ticket status:open to get a number back without fetching a single ticket. Everything in the verify path is read-only.
Node reference
45 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 34
Zendesk: Count Search Results
zendesk_count_search_results
Return only the number of records matching a search query, without fetching them. Cheap way to branch an automation on how many open tickets match a filter.
Zendesk: Count Tickets in View
zendesk_count_view_tickets
Return the (possibly cached, estimate-grade) ticket count for one view without fetching tickets. Rate cap: 5 requests per minute per view per agent.
Zendesk: Execute View
zendesk_execute_view
Run a view and get its column titles plus a row per ticket (with a partial ticket object each). Rate cap: 5 requests per minute per view per agent, and results may be served from a cache up to 10 minutes old; for high-frequency polling Zendesk points at Incremental Ticket Export instead. For full ticket objects use List Tickets from View.
Zendesk: Export Search Results
zendesk_export_search_results
Search WITHOUT the 1,000-result cap, cursor paginated, for one record type at a time. Cursors expire after one hour; rate cap 100 requests per minute. Keep page sizes modest (100 is the recommended value; large pages of archived tickets can time out).
Zendesk: Get Attachment Metadata
zendesk_get_attachment
Fetch one attachment's metadata: file name, content type, size, and a download URL (content_url). Attachment ids appear on comments from List Ticket Comments. Uploading attachments is a multipart binary POST the canvas cannot produce, so it is deliberately not offered.
Zendesk: Get Current User
zendesk_get_me
Return the user the API token belongs to. Needs no configuration, which makes it the connector's credential health check. Caution: Zendesk allows this endpoint for anonymous callers, so a wrong credential can come back as HTTP 200 with a null user id instead of a 401; a healthy connection is status 200 AND a non-null data.user.id. The response never echoes the API token (the authenticity_token field is a CSRF token for help-center calls, not your credential).
Zendesk: Get Group
zendesk_get_group
Fetch one group by id.
Zendesk: Get Job Status
zendesk_get_job_status
Poll a background job (status: queued, working, completed, failed, or killed, plus per-record results). Honest note: every write in this connector is synchronous, so no node here produces a job; Zendesk returns job statuses from its bulk endpoints (create/update/delete many, merge, permanent delete), which are not built. Use this to poll a job id obtained elsewhere. Job data expires one day after the job is created.
Zendesk: Get Macro
zendesk_get_macro
Fetch one macro by id, including its actions list.
Zendesk: Get Organization
zendesk_get_organization
Fetch one organization by id.
Zendesk: Get Ticket
zendesk_get_ticket
Fetch one ticket by id. The response holds the ticket's properties and its first comment as description; the full conversation comes from List Ticket Comments.
Zendesk: Get User
zendesk_get_user
Fetch one user by id.
Zendesk: Incremental Organization Export
zendesk_incremental_organization_export
Time-based incremental export of organizations created or changed since a Unix epoch start_time (organizations have no cursor variant). Follow next_page / use the returned end_time as the next start_time; a page shorter than 1,000 records means you are caught up. Rate cap: 10 requests per minute.
Zendesk: Incremental Ticket Export
zendesk_incremental_ticket_export
Cursor-based incremental export: every ticket created or changed since a point in time, the right tool for keeping an external system in sync. First call: start_time (Unix epoch, at least one minute in the past). Every later call: the previous response's after_cursor. Stop when end_of_stream is true and reuse the last cursor next run. Rate cap: 10 requests per minute.
Zendesk: Incremental User Export
zendesk_incremental_user_export
Cursor-based incremental export of users created or changed since a point in time. Same cursor protocol as the ticket export (start_time first, then after_cursor; stop at end_of_stream). Rate cap: 20 requests per minute (60 with the High Volume add-on).
Zendesk: List Automations
zendesk_list_automations
List Zendesk automations (time-based business rules, evaluated hourly) with their conditions and actions. Read-only by design.
Zendesk: List Deleted Tickets
zendesk_list_deleted_tickets
List soft-deleted tickets from the last 30 days that have not yet been scrubbed, oldest first (up to 100 per page). Pair with Restore Deleted Ticket to undo a deletion.
Zendesk: List Group Memberships
zendesk_list_group_memberships
List which agents belong to a group (membership records carry user_id, group_id, and whether it is the agent's default group).
Zendesk: List Groups
zendesk_list_groups
List agent groups (up to 100 per page). Groups are the routing unit: tickets are assigned to a group, or to an agent within one.
Zendesk: List Macros
zendesk_list_macros
List the shared and personal macros available to the authenticated agent (up to 100 per page).
Zendesk: List Organizations
zendesk_list_organizations
List organizations, cursor paginated (up to 100 per page).
Zendesk: List Satisfaction Ratings
zendesk_list_satisfaction_ratings
List CSAT ratings received on tickets, filterable by score and time window. Note: these endpoints serve Zendesk's LEGACY CSAT feature; accounts that switched to the newer survey-based CSAT will see no new ratings here.
Zendesk: List Tags
zendesk_list_tags
List the account's most-used tags with usage counts (the most popular tags of the last 60 days, most used first; up to 100 per page).
Zendesk: List Ticket Comments
zendesk_list_ticket_comments
List a ticket's full conversation, oldest first by default (up to 100 per page). Read-only by API design: new comments are added with the Update Ticket node's comment fields, not here.
Zendesk: List Ticket Fields
zendesk_list_ticket_fields
List every system and custom ticket field with types and dropdown options. This is the schema-discovery node: the field ids and option values here are what the create/update ticket custom_fields arrays refer to.
Zendesk: List Tickets
zendesk_list_tickets
List tickets in the account, cursor paginated (up to 100 per page). Page through with meta.after_cursor. For filtered sets prefer Search or a view node; for a full one-way sync prefer Incremental Ticket Export.
Zendesk: List Tickets from View
zendesk_list_view_tickets
List the FULL ticket objects currently matching a view (up to 100 per page). The heavier sibling of Execute View.
Zendesk: List Triggers
zendesk_list_triggers
List ticket triggers (event-fired business rules) with their conditions and actions. Read-only by design: this connector does not modify admin configuration.
Zendesk: List Users
zendesk_list_users
List users in the account, cursor paginated (up to 100 per page), optionally filtered by role or external_id.
Zendesk: List Views
zendesk_list_views
List the shared and personal views available to the authenticated agent. A view is a saved ticket filter; execute one to get its current tickets.
Zendesk: Preview Macro on Ticket
zendesk_preview_macro_on_ticket
Show the full ticket as it WOULD look after applying a macro. Doc wording: "It doesn't actually change the ticket." To commit, pipe the returned result.ticket fields (and result.ticket.comment if present) into an Update Ticket node.
Zendesk: Search
zendesk_search
Unified search across tickets, users, and organizations with the Zendesk query language, for example type:ticket status:open tags:vip created>2026-07-01. HARD CAP: at most 1,000 results per query (100 per page; page 11 returns 422), though count reports the true total. For result sets beyond the cap, use Export Search Results. New records can take a few minutes to be indexed.
Zendesk: Search Organizations
zendesk_search_organizations
Find organizations by exact name (case insensitive) or exact external_id. Provide exactly one of the two; the API rejects the request otherwise. For fuzzy matching use the Search node with type:organization.
Zendesk: Search Users
zendesk_search_users
Search users by name, email, phone, notes, or details, for example the full search syntax jane@example.com or role:agent smith. Offset pagination only, capped at 10,000 records per query (100 per page). external_id lookups take the id verbatim, not search syntax.
Action nodes 11
Zendesk: Add Ticket Tags
zendesk_add_ticket_tags
APPEND tags to a ticket without touching its existing tags (HTTP PUT on the tags subresource; the Update Ticket tags field replaces the whole set instead). Returns the ticket's full updated tag list. Does not work on closed tickets.
Zendesk: Create Organization
zendesk_create_organization
Create an organization. The name must be unique in the account (a duplicate returns 422). Users whose email domain matches a domain_names entry can be auto-associated.
Zendesk: Create Ticket
zendesk_create_ticket
Create a ticket. The comment body becomes the ticket's description (first comment). Returns 201 with the new ticket. Business rules (triggers) run on creation and can email the requester. Reversible: a created ticket can be soft-deleted and restored within 30 days.
Zendesk: Create User
zendesk_create_user
Create a user (defaults to an end user). Set skip_verify_email true to avoid sending the verification email, which most automations want. Creating agents or admins can add billable seats. Reversible in workflow terms via suspension; note this connector deliberately ships no user delete (Zendesk user deletion is not recoverable).
Zendesk: Delete Ticket
zendesk_delete_ticket
DESTRUCTIVE: soft-delete a ticket. The ticket moves to the deleted-tickets list, stays recoverable for up to 30 days (List Deleted Tickets + Restore Deleted Ticket nodes), and is then permanently scrubbed. Rate cap: 400 deletions per minute. Permanent deletion is deliberately not offered by this connector.
Zendesk: Remove Ticket Tags
zendesk_remove_ticket_tags
Remove the listed tags from a ticket, leaving other tags in place. Returns the remaining tag list. Reversible (add them back); does not work on closed tickets.
Zendesk: Restore Deleted Ticket
zendesk_restore_deleted_ticket
Restore a soft-deleted ticket back to the account. Works only within the 30-day recovery window and only for tickets still on the deleted-tickets list.
Zendesk: Suspend or Unsuspend User
zendesk_suspend_user
Set a user's suspended flag: true blocks sign-in and routes their new tickets to the suspended queue, false lifts the suspension. Fully reversible; this is the safe alternative to user deletion (which Zendesk documents as not recoverable, and which this connector does not offer).
Zendesk: Update Organization
zendesk_update_organization
Update an organization. Only filled fields are sent; tags and domain_names replace their whole lists when provided.
Zendesk: Update Ticket
zendesk_update_ticket
Update a ticket: add a public reply or internal note (comment_body + comment_public), change status, reassign (assignee_id / group_id), set priority, or replace tags. Only the fields you fill are sent. This is THE way to add a comment in the Zendesk API. Rate cap: 30 updates per 10 minutes per ticket. Closed tickets cannot be updated.
Zendesk: Update User
zendesk_update_user
Update a user's profile. Only filled fields are sent. Zendesk quirk: passing email here ADDS it as a secondary, unverified identity rather than replacing the primary address. Rate cap: 5 updates per minute per user.
Using the integration
On the automation canvas
Zendesk nodes chain with every other node: a scheduled Zendesk: Search sweep can open tasks in Mattering Productivity for urgent tickets, Zendesk: Incremental Ticket Export can keep a Mattering database mirrored with the help desk for reporting, and an AI step can draft internal notes that wait on a review task instead of reaching a customer.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can count open tickets, read a conversation with Zendesk: List Ticket Comments, look up requesters and organizations, and preview what a macro would do, through the same nodes your workflows use. The search, view, and export nodes are read-only, which makes them the safest Zendesk surface to hand an agent.
Replies and internal notes through ticket update
The Zendesk API has no direct comment-create endpoint: comments are created by including a comment in a ticket update, so Zendesk: Update Ticket carries typed fields for the comment body and its public flag. A public reply emails the requester and fires business rules; an internal note stays visible to agents only, which makes it the safe path for automated or AI-drafted content. Two constraints to plan around: each ticket accepts at most 30 updates per 10 minutes, and closed tickets cannot be updated, commented on, or tag-edited at all.
Search, count, and the uncapped export
Zendesk: Search speaks the full Zendesk query language, for example type:ticket status:open tags:vip, but the search API hard-caps at 1,000 results per query even though its count reports the true total. Zendesk: Count Search Results returns just that number, cheaply. Zendesk: Export Search Results is the way past the cap: cursor-paginated with no result limit, one record type per run, cursors that expire after an hour, and a recommended page size of 100. Newly created records can take a few minutes to appear in search results.
Incremental exports, the sync workhorse
Zendesk: Incremental Ticket Export returns every ticket created or changed since a point in time: the first call takes a start time, every later call takes the previous response's cursor, and a true end-of-stream flag means you are caught up until next run. Zendesk: Incremental User Export follows the same cursor protocol, while Zendesk: Incremental Organization Export is time-based, since organizations have no cursor variant. These are the right nodes for mirroring the help desk into a Mattering database; they are rate-capped around 10 requests per minute, which a scheduled sync never notices.
The safety posture, node by node
Zendesk: Delete Ticket is a soft delete: the ticket sits on the deleted-tickets list for up to 30 days, visible through Zendesk: List Deleted Tickets and reversible through Zendesk: Restore Deleted Ticket, before Zendesk scrubs it for good; the permanent-delete endpoint is deliberately not built. Zendesk: Preview Macro on Ticket uses Zendesk's own preview semantics, returning the ticket as it would look without changing it, and committing is a follow-up Zendesk: Update Ticket. Tags have precise semantics too: Zendesk: Add Ticket Tags and Zendesk: Remove Ticket Tags append and remove without touching other tags, while the tags field on a ticket update replaces the whole set.
Troubleshooting
Test Connection fails saying Zendesk returned the anonymous user
Every node returns a 401 after working before
Search stops at 1,000 results or errors on deep pages
Updating a ticket fails because the ticket is closed
An automated comment reached the customer as a public reply
Nodes intermittently return 429 responses
A deleted ticket cannot be restored
Satisfaction ratings come back empty
Related
The Zendesk MCP
What connecting Zendesk unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Zendesk is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.