Rules and Triggers Solution Guide
Below are the common use-cases for using rules and triggers to automate manual actions and activities.
Common Triggers
If an Ask is created, Then ...
There are many scenarios where you want to run certain actions every time as soon as the Ask is created. Here's how to create this condition:
If this field Ask
- With this condition
Is Not Blank
This condition will always be true, because the Ask name is never blank.
Any Then action
Common Actions
The following are common actions, which are configured in the Then section of the rule, ex:
If ... , Then execute a webhook
Need to trigger a notification to a 3rd-party system when a certain condition occurs? You can with a webhook! Here's how to set it up:
Any If condition
Then the item Webhook
- To Url:
[Url of webhook]
This will execute the webhook when the condition occurs.
Checkout Pipeline's library of pre-built webhooks for commonly occurring tasks that are too complex for rules.
If ... , Then flag the Ask as high priority
Adding a flag emoji 🚩 to indicate that the Ask is high priority is very common, especially for time-sensitive Asks. Here's how to create the action:
Any If condition
Then the item Field
- That is this
Ask
- Will be
Updated
- With this value
🚩 {{ask.name}}
This will prepend the Ask name with 🚩 when the condition occurs.
Note, {{ask.name}}
is the content variable for the current name of the Ask, see Content Variables and Formulas Reference.
If ... , Then reassign step(s)
In many flows, certain steps are assigned and routed based on a form value, ex:
- If the user marks an order as
Rush
, assign steps to a specific individual - If the user indicates
Yes
for "Do you post on social media?", assign steps to a specific individual - If the user indicates
No
for "Are your taxes up-to-date?", assign steps to a specific individual
Here's how to create this rule:
Any If condition
Then the item Step
- That is this
[select steps to reassign]
- Will be
Reassigned
- Enter the person's email, team's name, or use a Content Variable
{{field[Field Name]}}
This will cause the step(s) to be reassigned when the condition occurs.
If ... , Then skip step(s)
In some flows, certain steps may be conditional, needed only when certain conditions apply, ex:
- If the purchase request uses an existing vendor, skip the new vendor registration steps
- If the purchase amount is less than $1,000, skip the manager approval steps
- If the customer rates their satisfaction as 8+, skip the executive notification steps
So, create rules to automatically skip those conditional steps. Here's how:
Any If condition
Then the item Step
- That is this
[select steps to skip]
- Will be
Skipped
This will cause the step(s) to be skipped when the condition occurs.