Skip to main content
Zendesk actions let an agent work with your support data directly in a flow. An agent can create and update tickets, manage users and organizations, read ticket fields, and pass the results to later steps.

Supported actions

Prerequisites

Generate an API token in your Zendesk admin center, then store it as a Zendesk credential in Credential Management. Select that credential on every Zendesk action.

How to use these actions

  • Every action needs your Subdomain and authentication email. The Subdomain is the mycompany part of mycompany.zendesk.com, and the authentication email is the email tied to your API token. Both are required on every Zendesk action.
  • Map text inputs from earlier steps. Inputs such as Subject, Description, and Email accept a value mapped from a previous step.
  • Numeric and toggle inputs take fixed values. Numeric IDs such as Assignee ID, Group ID, and Organization ID, the Limit, and the Comment Is Public toggle take fixed values.
  • Comma separated lists. Tags and Domain Names are entered as comma separated values.
  • JSON objects for custom data. Custom Fields, Organization Fields, and User Fields accept a JSON object.
  • List actions cap results with Limit. The Get All actions return up to Limit records.
Subdomain and the authentication email tied to your API token are required on every Zendesk action. They are documented here once and are not repeated in each operation’s input table below.

Actions

Ticket

Zendesk Ticket Create

Creates a new ticket.

Zendesk Ticket Update

Updates an existing ticket.

Zendesk Ticket Get

Retrieves a ticket by ID.

Zendesk Ticket Get All

Lists tickets.

Zendesk Ticket Delete

Deletes a ticket.

Zendesk Ticket Recover

Recovers a deleted ticket.

User

Zendesk User Create

Creates a new user.

Zendesk User Update

Updates an existing user.

Zendesk User Get

Retrieves a user by ID.

Zendesk User Get All

Lists users. Searches for users.

Zendesk User Delete

Deletes a user. Retrieves data related to a user, such as their tickets and organizations.

Organization

Zendesk Organization Create

Creates a new organization.

Zendesk Organization Update

Updates an existing organization.

Zendesk Organization Get

Retrieves an organization by ID.

Zendesk Organization Get All

Lists organizations.

Zendesk Organization Delete

Deletes an organization.

Zendesk Organization Count

Returns the total number of organizations. This action takes no inputs beyond the credential. Retrieves data related to an organization, such as its users and tickets.

Ticket field

Zendesk Ticket Field Get

Retrieves a ticket field by ID.

Zendesk Ticket Field Get All

Lists ticket fields. This action takes no inputs beyond the credential.

Example

An agent that opens a ticket for an inbound support request:
1

Find the requester

A Zendesk User Search action sets Query to the requester’s email so a model step can confirm whether the user already exists.
2

Create the ticket

A Zendesk Ticket Create action sets Subject and Description from the request, sets Priority, and maps Requester Email to the matched user.
3

Confirm

A model step summarizes the ticket result, including the returned ticket ID, for the activity log.

Troubleshooting

Confirm the Subdomain and the authentication email are correct, and that the stored API token belongs to that account and has not been revoked. The authentication email must match the user who owns the token.
The Ticket ID, User ID, or Organization ID you passed does not exist in this Zendesk account. Use a Get All or Search action to confirm the ID before referencing it.
Status, Priority, and Type accept only their listed values. Custom Fields, Organization Fields, and User Fields must be a valid JSON object whose keys match fields defined in your account.
Zendesk Ticket Recover only works on a ticket that was soft deleted and not yet permanently removed. A permanently deleted ticket cannot be recovered.
For issues common to every vendor, see the Actions overview.