Base conditions on an action's status

🕙  2 minute read

Conditions determine whether a task should start or be skipped. Conditions can be simple, like “If the deadline is 3 days from now; start the task” or more complex, “If the deadline is 3 days from now, and the process is high priority; start the task”.

An action can start conditionally based on the status of an action, like whether it is assigned or completed.

screen readers look here

In the example below, the task being configured will not start unless the Send email task is completed.

screen readers look here
If the task "Send email" is completed, this condition would evaluate to true.

How to add a task condition

When setting a task condition, the task executes if the condition is true. The task is skipped is the condition is false. For example:

  • If Action A is snoozed, and your condition is “If Action A is snoozed”, the task will execute.
  • If Action B is not snoozed, and your condition is “If Action A is snoozed”, the task will be skipped.
  1. In the Workflow builder screen, select an action, then select Conditions.
  2. Select the type of object you want to add to the condition, then select the object.
  3. Select an operator.
  4. Select the next type of object you want to add to the condition, then select the object.
  5. Add or remove a condition. Select Add a Condition to add new conditions, or select to remove a condition.
  6. Select
List of selectable condition options

To create a condition, compare two objects. To do this, select the object type, then select the value.

For example, to check if an action is completed, select the type “Action”, then select the action. Set the operator to “is equal”. Then, select the type “Action Status” and select “Completed” status.

screen readers look here
  • Field: Select from a list fields available in this Workflow.
  • Field Choice: Only appears if one of the conditions is a single or multiple choice field. Select from a list of available choices.
  • Text: Enter in a value, such as text or integer, to compare against. This accepts more than just strings.
  • True or False: Select from True or False.
  • Action: Select from a list of actions available in this Workflow.
  • Action Status: Select a status that an action may have, such as “Completed” or “In Progress”

See the task conditions article for more information.

Get help with a problem or question

If something’s not working as expected, or you’re looking for suggestions, check through the options below.

My conditions are not working as expected

Remember that if the conditional statement evaluates to true, the field is hidden or the task is skipped.

For example, when setting a task condition, the task executes if the condition is true. The task is skipped is the condition is false.

  • If Action A is snoozed, and your condition is “If Action A is snoozed”, the task will execute.
  • If Action B is not snoozed, and your condition is “If Action A is snoozed”, the task will be skipped.

Conditions are evaluated from top to bottom. In some cases, it’s necessary to rearrange the order of conditions when you have two or more conditionals linked with and and or statements. For example, it’s usually best practice to put is empty or is not empty statements last.