Automation
Configuring Automation Actions
Configuring Automation Actions
Automation actions define what the Helpdesk does after a rule's trigger and conditions qualify.
Supported actions
Available actions depend on the automation engine and module.
Typical action categories may include changing ticket properties, assigning responsibility, or performing other configured workflow operations.
Action order
When a rule contains multiple actions, consider whether one change affects the meaning of a later action.
Assignment actions
Assignment-related actions should use valid teams and agents and should not silently produce impossible ownership combinations.
Field changes
Only set values that are valid for the target field.
Prevent conflicts
Review other automation and assignment rules that may act on the same ticket.
Good practices
Use the smallest set of actions required for the business outcome. Test the final ticket state, not merely whether the rule reported that it executed.