Admins can use sales triggers in Sell to automate specific parts of the workflow of every sales rep. This means that when an event you specified occurs, and the conditions you configured are met, then an action that you defined is carried out. For example, you can automate the workflow of all sales reps so that every time a trigger event (such as a deal being updated) occurs in Sell, and meets its pre-defined conditions (such as, “Deal value is greater than 1000”), then Sell automatically attempts to carry out the actions defined for that trigger, for example “Update Deal Owner to Valerie Golden”.
You must be an admin to create triggers. However, all Sell users can cause a trigger event that prompts the evaluation of conditions and carries out the predefined action if the trigger conditions are met.
This article covers the following topics:
Creating the conditions of a trigger
You can define conditions to specify when trigger actions are implemented after a trigger event occurs. Every time it occurs, the sales triggers that use it will evaluate their conditions against the object that caused the trigger event. Trigger actions are carried out every time a trigger event occurs and the trigger conditions are met.
To avoid repetitive triggers, if trigger A, for example, carries out actions on object B, then object B causes a trigger event and the trigger A conditions are met, you want to ensure that the actions will not be carried out again and again.
The following sample recipe avoids this sort of problem. The Sales Trigger conditions assign any deal that is updated to a worth of 1,000 or more in value to be assigned to the sales rep in New York, Valerie Golden.
Deal is updated
Deal Value is greater than
Deal State is
Deal Owner to
To create a trigger
- On the Sell sidebar, click Settings > Business rules > Triggers.
- On the Triggers page, click Add trigger.
- In the Name field, name your trigger (for example
Deal owner updated).
- Select the Set as active checkbox if you want this trigger to be active.
- Under When, click the event that will cause the trigger (for example,
Deal is updated).
- Under If, click +Add condition.
- Enter information about the trigger in the following fields:
- Object - Deal is the only object currently supported.
Field - choose the type of field you want the object to refer to (for example,
Operator - choose from the dropdown menu that relates to the field you've chosen (for example,
Is greater than).
Value - enter the value that relates to your choice from the Field menu (for example
Greater than 1000)
- Click Add.
Setting the actions of a trigger
After setting the trigger event and conditions, you can determine the actions that will happen if the trigger evaluation is successful.
Actions perform on objects that are the subject of the trigger event and have met the trigger conditions that you specified for it.
You select which fields of an object you want to add values for, or update. For example selecting the
Owner field and “Valerie Golden” as the value will cause the owner of the deal to change to Valerie Golden every time a trigger event happens and the conditions are met to incur that action.
To create the action for the trigger
- Under Then, click Add action.
- Under Update, in the Object to update field, choose an object from the dropdown menu (Deal is currently the only supported object).
- Under Update field values, enter information about the actions that the trigger will set into motion:
Field to update - choose from the dropdown menu (for example
- Value - available on the Field to update menu, choose from the Value dropdown menu the value that relates to your choice (for example the name of the person you want the deal to be owned by).
- Field to update - choose from the dropdown menu (for example
- Add as many relevant fields and values as is necessary for your trigger (up to 200). When you are finished, click Add.
- Click Save.
Using 'and' 'or' operators
After you've added the first condition, an AND operator appears beneath it. The operator determines the relationship between conditions for the logic behind the trigger. You can set it to AND or change it to OR.
AND - use this operator if you have two or more conditions that must be met for the trigger evaluation to succeed. You can also use the AND operator to connect conditions across clauses.
OR - use this operator when you have two or more conditions in a clause, but only one of the conditions must be met for the trigger to be successful.
The following example, uses a set of conditions that evaluate to true in two independent scenarios:
- 1st scenario: Requires only one condition to be met: if the
Deal Valueis greater than
- 2nd scenario: If three conditions are met: the
Deal Countryis the
Deal Sourceis a
Tradeshow, and the
Deal primary contactis
Deal.Value is greater than
primary contact is
Using a nullifying condition
Sometimes the logic for a trigger requires a nullifying condition, for example, to prevent a trigger from looping. As the following scenario shows, a nullifying condition will prevent your trigger from performing further actions if that condition has already been met.
Scenario: a looping trigger
In this scenario, the logic for an ownership trigger assigns
Distribution assigns a user from its pool as a new
Deal.Owner > The result is that the deal is updated. This triggers a new trigger event, causing the trigger to run again on the same object, assigning another owner from the Distribution pool, and repeating the cycle again, and again.
To prevent a looping trigger
Add a nullifying condition that only allows the trigger to run once on a given object. For example,
Deal.Owner is not
Adding this condition means a distribution will act on a deal only when the conditions are met. When the trigger acts again on the deal, it will check if the deal owner belongs to that distribution. If that’s true then the condition IF
Deal.Owner is not
Distribution will be met, causing the evaluation logic of the trigger to be false and preventing the trigger from repeating the same action over and over again.
Do you have an ETA for adding custom fields to triggers?
Hi Ranya, first batch of custom fields (Single Line Text, Number and Dropdown) will be available within the next 1-2 weeks.
They will be followed with Date, Paragraph, Multi Select and Checkbox custom fields within a few weeks, and then within another few weeks we'll add the rest.
Quick question, is there a timeline or plans for including contact/company properties in to triggers?
Been spoiled with the level possibilities of triggers on the support side and really looking forward to Sell triggers expanding (it's currently one of the things holding us back from migrating from our existing CRM)
Thanks in advance!
This thread would be a good place to ask that question: Sales Triggers - we want your feedback!
Hi! I have few questions:
- how much time trigger need to run? Are they able to deal with a lot of deals in same time?
- "Deal is updated" means, no matter what field and in no matter what way will it be updated? Or does this mean that the condition field must be updated from a specific trigger for it to work?
- are you planning to add the option "greater than or equal to?" for numeric fields?
Hi Katarzyna Traczyk,
1. Triggers would run immediately for updated deals that fit the trigger conditions.
2. "Deal is updated" is the event. So triggers would run anytime a deal has been updated, hence the "when" function but only when it meets the requirement under the "if" function. So it won't run everytime and would only run if it meets your conditions.
3. We are working on adding custom fields to the trigger conditions which was mentioned by Jakub here in our feedback section: Sales Trigger Feedback
Hope this helps
Hi everyone, quick update... we added new custom field types to trigger conditions and actions! This means we currently support:
Hi, I'd like to confirm if the default feature when "deal is updated" also works when a deal is created/added.
Please sign in to leave a comment.