A Condition step splits the flow into branches. Each branch has one rule and its own steps. Use it to treat trainees differently inside the same automation, for example by plan, by coach or by whether they opened the app again.

​
Add a condition

1

Add the step

Open the Add action menu where you want the split and choose Condition.The condition starts with two branches: Branch A and In any other case. Any steps that were below the point where you added it move into Branch A.
2

Write the rule for Branch A

Pick a field, then fill in the comparison. See the field list below.
3

Add more branches

Click Add condition on the condition step to add Branch B, Branch C and so on. The In any other case branch always stays last.
4

Add steps inside each branch

Use the plus button inside a branch. A branch can hold any step, including another condition.

​
Which branches run

  • Every branch whose rule is true runs, in the order shown. It is not “first match wins”. A trainee who matches Branch A and Branch B goes through both.
  • In any other case runs only when no other branch matched.
  • If no branch matched and In any other case has no steps, the flow continues with whatever comes after the condition.
  • After the branches finish, the flow continues with the steps below the condition.
A branch whose rule you left unfinished, with no value chosen, counts as true for everyone. Finish every rule, or delete the branch.

​
Fields you can test

​
Flow fields

​
Trainee filters

The field picker also lists the filters from the trainee list, so a condition can use the same rules you use to filter trainees: Status, Age, Submitted a form, Last activity, Operating system, Nutrition plan, Workout plan, Subscription start date, Subscription end date, Gender, Tags, Current weight, Goal weight, Join date, Days to subscription end and Frozen subscription. Each one shows the same operators and values as on the trainee list. A condition tests one trainee, so the operators that count plans are not offered.

​
Notes on Form field value

  • Type the field’s label as it appears on the form, for example “weight”. Perform looks for a field with that exact label first, then for a label that contains your text.
  • Only number answers can be compared. A text answer never matches.
  • It reads the trainee’s latest form submission, whichever form it was. If that form has no such field, the rule is false.

​
Useful patterns

Follow up only if nothing changed. Add a Wait of 2 days, then a condition with Opened the app since the trigger set to No. Put the follow-up message in that branch. Different coach, different task. Add a branch for each plan with Subscription / plan, and put a Create task step with a different assignee in each. Escalate. After a Wait, test Form status is Not filled and open a second task for the manager.

​
Delete a branch or a condition

  • Hover over a branch and use Delete branch. If the branch has steps, Perform asks you to confirm, because the steps are deleted with it.
  • Deleting the whole condition deletes every step in all of its branches.

​
Limits

  • A condition can have up to 6 rule branches plus In any other case.
  • Conditions can be nested up to 5 levels deep.
See Limits for the rest.

Building a flow

Use the test run to see which branch is taken.

Actions

The steps you can put inside a branch.