Triggers are business rules that run immediately after a ticket is created or updated and automatically perform actions if specified conditions are met. For example, a trigger can be used to notify the customer when a ticket has been opened.
Triggers are composed of conditions, which are the qualifications needed for the trigger to fire, and actions, which are performed when those qualifications are met (see Understanding trigger conditions and actions). In other words, if the conditions are true, then the trigger will perform the actions.
There is a standard set of default triggers that you can use and you can also create your own triggers. Admins and agents in custom roles with permission to manage business rules can create triggers.
Creating triggers
Triggers are business rules that run immediately after a ticket is created or updated and automatically perform actions if specified conditions are met. There are default triggers and you can create additional triggers.
You must be an admin or an agent in a custom role with permission to create triggers.
The following video gives you an overview of how to add triggers:
Automating notifications with triggers [2:02]
- In Admin Center, click
Objects and rules in the sidebar, then select Business rules > Triggers.
- Click Add trigger.
Alternatively, you can copy an existing trigger and modify it.
- Enter a Name for your trigger.
Use a consistent naming convention to help you recognize similar types of triggers.
- (Optional) Enter a Description for your trigger.
You can provide details about what the trigger does. You'll be able to search for triggers based on description.
- Select an existing Category for your trigger or create a new one.
- Click Add condition to set up the trigger to meet All or Any
conditions.
Conditions are the qualifications needed for the trigger to fire.
- Select a Condition, Field operator, and Value for each condition
you add.
The field operator determines the relationship between the condition and the value. For example, if you select the field operator "Is", your condition will need to be equal to the value. Different conditions will contain different field operators.
See Building trigger condition statements.
Note: It is recommended to keep your trigger statements simple. The more complicated a trigger is, the harder it will be to troubleshoot and maintain. - Click the Add action to set the actions that occur when trigger conditions are met.
- Select Action and a Value for each action you add.
- Enter the action information.
Depending on the action you select, you will enter different information. For example, if you select the "Type" action, you will need to select a ticket type.
- Click Create.
Your new trigger is added to the end of the list of triggers.
Note: Each business rule must be less than 65kb.
You can reorder the list of triggers (see Reordering triggers) or edit any trigger (see Managing triggers).
33 Comments
Ezgi Filazoğlu I think the part that's causing problems is that Ticket is Created, and Ticket is Updated cannot both be requirements, that's why it's not firing. If you remove "Ticket is Updated", it should be able to fire.The current user piece will make it so this only fires if a ticket is created by someone for themself, which is fine and should be okay.
After a ticket is created, all future updates are "Ticket Updates", but the very first one, is not considered a ticket update, so it's a conflict with "Ticket is Created".
Thank you for this answer @CJ: Ezgi Filazoğlu I think the part that's causing problems is that Ticket is Created, and Ticket is Updated cannot both be requirements, that's why it's not firing. If you remove "Ticket is Updated", it should be able to fire.The current user piece will make it so this only fires if a ticket is created by someone for themself, which is fine and should be okay. After a ticket is created, all future updates are "Ticket Updates", but the very first one, is not considered a ticket update, so it's a conflict with "Ticket is Created". I have one moe question. So what kind of trigger should I create to receive a notification if an end-user makes a comment for ticket. İsn't it "Ticket is Updated"?
Hi Ezgi,

For my organization, I would make a separate trigger, set up like below to get emails flowing for ticket updates. If we assume your agents set to tickets to pending, and tickets only switch to open when the user replies (which is what happens automatically by default), this would work. It says that if a ticket is updated, and that update changes the status to open, and the update has a comment being added as part of it, email the assignee this template that includes a ticket link and the latest comment formatted in HTML.
Please sign in to leave a comment.