Summary: ◀▼
Use action flows to automate work triggered by ticket, user, custom object, asset, Slack, schedule, or external events—or run them on demand. Combine ticket and user actions with branches, waits, repeats, variables, and custom code to handle different conditions and data. Custom actions and connector actions let you query or update external systems, while outputs can support agent copilot suggestions.
An action flow is a user-defined automated workflow. Each action flow consists of an action flow trigger, which initiates the flow, and one or more actions. Action flows can run in response to their configured trigger or be initiated by agents using agent copilot auto assist.
This article describes the parts of an action flow and specific steps and actions that can be added to them.
Action flow triggers
Every action flow begins with a trigger event. This is what initiates the flow. The following types of events are available as action flow triggers:
List of action flow triggers
| Action flow triggers | Description |
|---|---|
| Ticket events | Including ticket lifecycle, such as creation, and ticket
updates to: ticket properties, standard or custom ticket
fields, routing, comments, SLAs, schedules, and
CSAT Action flows initiated by ticket updates often run when a ticket is created, too, because ticket values are perceived as changing from null or empty to an actual value. |
| User events | Including user creation; updates to a user's name, role,
organization, group, brand, and so on; updates to custom
field values on a user's profile; adding or changing a
profile picture; changes to a user's identity; and changes
to a user's status, such as suspended or deleted. Note the
following:
|
| Custom object events | Including custom object lifecycle, such as custom object record created, updated, or deleted. |
| IT asset events | Including asset creation, update, assignment, unassignment, and deletion. |
| Slack events | (EAP) Including new message posted in channel, new direct
message sent to a user, and new reaction added to message
There isn't a built-in way to link a Slack message to a Zendesk ticket after the ticket is created, for ongoing conversational support. If you use a Slack event as an action flow trigger that then creates a Zendesk ticket, only the contents of the message that initiated the action flow as it existed at that moment in time, is available for inclusion in the ticket. |
| Run on demand | The Run on demand action flow trigger functions only for AI agents and auto assist. |
| Schedule | A time-based trigger allowing action flows to run at a specific time, in the selected timezone, on a recurring basis. Schedules can run daily, hourly, weekly, or monthly. Additional options vary based on the frequency selected. |
| Custom action flow trigger | User-defined triggers designed to listen for an HTTP request from a specific external system. Select an existing custom trigger or create a new custom trigger. |
- Open an action flow.
- In the visual workflow builder, click + Add trigger.
- In the step sidebar, select whether you want the action flow to be initiated by a Ticket event, User event, Slack event, when a Suggested action flow is approved by agent, or by a custom trigger.
- Click through the available options and select a single action flow trigger.
- If you selected Agent copilot > Auto assist > Suggested action
flow approved by agent, you can configure an input to be
provided by auto assist:
- In the step sidebar, click + Add input.
- Enter a Name and Description.
Providing clear and detailed names and descriptions for inputs helps auto assist determine the correct information to provide when the action flow runs.
It is possible to have auto assist provide a ticket ID as input for this action flow trigger. To do so, you must name the input zendesk_ticket_id and set the type to number. If the input name and type aren't exact matches to this, auto assist won't be able to add the ticket ID.
- For Type, select one of the following options: True/False (Boolean), Text, Number (Integer), Decimal, Date, Date and time, or an array of the supported types.
- Click Save.
- (Optional) For ticket event, user event, and custom action flow
triggers, you can configure conditions that must be met for the action
flow trigger to fire.
- Select the Variable. This is data output from the action flow trigger.
- Select the Operator that describes the relationship between the condition's variable and value. The available operators change based on the variable selected.
- Enter the Value used when evaluating the condition.Note:
- These values are case-sensitive. It's important to note that Zendesk tickets use lowercase for the type, status, and priority fields. For example, when referring to a ticket's type, entering a value of Incident would fail to match because it's expecting incident.
- The value field isn't required when using the Is present or Is not present operators. Use the is present operator when a variable is present only sometimes or is consistently included but can have a null value.
- To add other conditions, click Add condition and specify
whether the condition must be met (AND) or can be met
(OR).
An action flow trigger can have a maximum of 10 conditions.
- To create nested condition groups, such as
Condition A AND (Condition B OR Condition C), click Add next group.Conditions can be nested up to two levels deep. Conditions nested beyond two levels can't be saved.
Zendesk actions
Zendesk action steps perform Zendesk-specific tasks, such as modifying a ticket's priority. Zendesk actions that are performed by the flow are attributed to the system user.
The available Zendesk actions depend on the features that are turned on in your account, but include:
List of Zendesk actions
| Zendesk actions |
|---|
| Add internal note to ticket |
| Add public reply to ticket |
| Add tags to ticket |
| Add task to ticket |
| Assign asset (ITAM only) |
| Batch import assets (ITAM only) |
| Create asset (ITAM only) |
| Create custom object record |
| Create or update custom object record |
| Create or update user |
| Create ticket |
| Create user |
| Delete asset (ITAM only) |
| Delete custom object record |
| Hand off to custom agent (Custom Agents EAP only) |
| Import asset (ITAM only) |
| List ticket comments |
| List ticket history |
| Look up asset (ITAM only) |
| Look up custom object record |
| Look up organization |
| Look up ticket |
| Look up user |
| Remove tags from ticket |
| Search assets (ITAM only) |
| Search custom object records |
| Send approval request |
| Unassign asset (ITAM only) |
| Update custom object record |
| Update ticket |
| Update user |
- Open an action flow.
- In the action builder, beneath an existing step, click the Add
step icon (
). - In the step sidebar, under Zendesk actions, click the menu options to select the action.
- In the step sidebar, enter the required inputs for the selected action. See Providing inputs and outputs for actions and steps.
Flow control and utility steps
Flow control and utility steps structure your action flow and extend it with custom logic. The following flow control and utility steps are available:
Branch
Although some action flows progress linearly, it's common for them to include one or more branches. When you add a branch step, you must define a single condition for the first branch. Optionally, you can add other conditional branches. The default Else branch encompasses everything that doesn't match a conditional branch, so no configuration is required for the Else branch.
- Open an action flow.
- In the visual workflow builder, beneath an existing step, click the
Add step icon (
). - In the step sidebar, under Flow control and utility, select Branch.
- In the step sidebar, configure Branch 1 with a descriptive name
and a condition. This is the default conditional branch.
- Enter a descriptive Name for the branch.
- Under Conditions, select the Variable. This is data output from a previous step in the action flow.
- Select the Operator that describes the relationship between the condition's variable and value. The available operators change based on the variable selected.
- Enter the Value used when evaluating the condition.Note:
- Values are case-sensitive. It's important to note that Zendesk tickets use lowercase for the type, status, and priority fields. For example, when referring to a ticket's type, entering a value of Incident would fail to match because it's expecting incident.
- Dates have additional configuration options, which enable more complex time-related conditions, such as a date value plus or minus a certain number of days. See Using date and time values in actions and steps.
- The value field isn't required when using the Is present or Is not present operators.
- (Optional) In the step sidebar, click + Add branch as needed, configuring each branch with a unique name and condition.
Wait
Wait steps are used to pause an action flow mid-execution until either a specified amount of time has passed or condition is met. After the wait time or condition occurs, the action flow resumes from that point in the action flow.
Note when testing action flows with wait steps, the wait step runs at 10 times the speed and displays both the test duration and the production duration.
You can cancel an action flow run while it's waiting at a Wait step. See Cancelling an action flow run.
- Open an action flow.
- In the visual workflow builder, beneath an existing step, click the
Add step icon (
). - In the step sidebar, under Flow control and utility, select Wait.
- In the step sidebar, use the following fields to configure a static wait
time with a whole number value and unit of time or select a variable
wait time output from a previous step.For example, you might use a custom code step to output a variable wait time based on the ticket's priority, such as 2 hours for urgent tickets and 24 hours for all other priority levels. In that case, you'd configure the wait time in the following way:
- Label: Wait by ticket priority
- Unit of time: Hours
-
Amount of time: Custom code step >
dynamic_wait_hours
Repeat while condition is met
If you need to repeat an action under specific circumstances, you can use the Repeat while conditions are met step. This is ideal for fetching data.
- Open an action flow.
- In the visual workflow builder, beneath the last step in your action
flow (or branch of an action flow), click the Add step icon
(
). - In the step sidebar, under Flow control and utility, select Repeat while condition is met and place it where you want it in the flow.
- Add at least one action to the repeat box in the action builder.Note: Repeat for each steps can be added within a repeat while conditions are met step, but not vice versa.
- Click the Repeat while condition is met step to specify the
step's condition.
Conditions are the qualifications needed for the step to repeat. Only one condition can be defined for a repeat while step.
- Select a Variable, Operator, and Value for the
condition.
The variable must be an output from an action in the repeat box. The operator determines the relationship between the variable and the value. The available operators vary based on the selected variable's type.
Repeat for each
If you need to repeat an action for a list of items, use the Repeat for each step. This is designed for bulk data operations.
- Open an action flow.
- In the visual workflow builder, beneath the last step in your action
flow (or branch of an action flow), click the Add step icon
(
). - In the step sidebar, under Flow control and utility, select Repeat for each and place it where you want it in the flow.
- Under List, select an output from a previous step in the action flow that is an array.
- (Optional) If you need to check more than one list, click Check for more items in the repeat box in the action builder and select another array.
Update custom variables
The update custom variable step allows you create new variables you need for a workflow and update a previously created or referenced variable with a new value. This is particularly useful for iterating through paginated data and incrementing counters.
- Open an action flow.
- In the visual workflow builder, beneath an existing step, click the
Add step icon (
). - In the step sidebar, under Flow control and utility, select Update custom variable.
- Select one or more previously specified variables and enter a variable
as input for the step.
For more information, see Providing inputs and outputs for actions and steps.
Send outputs to copilot
- Open an action flow.
- In the visual workflow builder, beneath the last step in your action
flow (or branch of an action flow), click the Add step icon
(
). - In the step sidebar, under Flow control and utility, select Send outputs to copilot and place it where you want it in the flow.
- In the step sidebar, click Add output to add at least one
output:
- Select the Variable. This is data output from a previous step in the action flow.
- Enter a unique Name that describes the output.
Custom code
Custom code steps allow you to incorporate modern JavaScript code into your action flows. The JavaScript must export a function that takes an inputs object and returns an outputs object. Each time you add a custom code step to an action flow, it is prepopulated with this framework, which you can modify, expand upon, or delete and start fresh.
Although the custom code step is designed to be as user-friendly as possible, admins might still require engineering support when implementing these steps.
For more information, see Using custom code steps in action flows.
Custom actions
Custom actions are user-defined steps that update or query data using any API. Custom actions are used by agent copilot auto assist, AI agents, and action flows.
Custom actions
Custom actions are user-defined steps that update data using any API the user specified. The custom actions defined for auto assist are also available for action flows.
- Text
- Number
- Decimal
- True/false
- Date
- Date and time
- Arrays (the above data types only; arrays of other data types might work but aren't guaranteed)
For more information, see Creating and managing custom actions.
- Open an action flow.
- In the visual workflow builder, beneath an existing step, click the
Add step icon (
). - In the step sidebar, under Custom actions, select one of the
actions you've created.
Keep in mind the following:
- Custom actions created prior to March 13, 2025 must be re-saved in order to be available as actions in action flows.
- A custom action reflects the action as it was defined at the moment it was added to the action flow. If a custom action is updated after it was added to an action flow, you must delete the custom action step in the flow and re-add it to see the changes.
- Provide static values or variables as inputs into the input fields
required by the custom action.
For more information, see Providing inputs and outputs for actions and steps.
Connector actions
The steps associated with connected systems in action flows are referred to collectively as connector actions. Connector actions perform tasks specific to a connected system, such as sending a Slack message or creating a Jira issue.
Article Q&A
Click to view
What events can I use to start an action flow?
I can use ticket, user, custom object, IT asset, Slack, schedule, custom action flow, or Run on demand triggers. Run on demand works only for AI agents and auto assist. Schedule triggers can run hourly, daily, weekly, or monthly; custom triggers listen for HTTP requests from a specified external system. Agents can also initiate action flows using agent copilot auto assist.
How can I add conditions to an action flow trigger, and what are the limits?
For ticket, user, and custom action flow triggers, I can add conditions by selecting a trigger output variable, operator, and value, then combine conditions with AND or OR. Values are case-sensitive; ticket type, status, and priority values use lowercase. Is present and Is not present don't require a value. A trigger can have up to 10 conditions, nested no more than two levels deep.
How can I control the order or repetition of steps in my action flow?
I can add a Branch step to direct the flow based on one condition; its default Else branch covers anything that doesn't match. A Wait step pauses for a set time or until a condition is met, then resumes. Repeat while condition is met repeats actions when one condition is true, using an output from an action inside the repeat box. Repeat for each runs steps for items in an array from an earlier step. I can also update custom variables for values such as counters.
What Zendesk actions can I add to an action flow?
Depending on the features enabled in my account, I can add actions such as creating or updating tickets and users, adding ticket notes, replies, tags, or tasks, and looking up tickets, users, organizations, or custom object records. IT asset actions are available only with ITAM. Zendesk actions performed by the flow are attributed to the system user.
How can I use custom actions, custom code, or connector actions in an action flow?
I can add a custom action to update or query data through an API, provide its required inputs, and use supported outputs such as text, numbers, Boolean values, dates, and arrays of those types. Custom actions created before March 13, 2025 must be re-saved to appear in action flows; if one is updated after being added, I must delete and re-add its step to use the changes. Custom code steps use JavaScript that accepts an inputs object and returns an outputs object, and may require engineering support. Connector actions perform tasks for connected systems, such as sending a Slack message or creating a Jira issue.