Skip to main content

How do condition steps work in a Smart Workflow?

What a Condition step checks in a Smart Workflow, what Yes and No do, and the conditions you can choose.

A condition step checks one thing about the member at that point in the workflow. If the answer is Yes, the workflow carries on to the next step. If the answer is No, the workflow ends for that member. On the workflow canvas these show as Yes — continue and No — end workflow, and they can't be swapped.


How do I add a condition step?

  1. Open your workflow in Smart Workflows.

  2. Click Add step where you want the check to happen and choose Condition ("Only continue if member matches criteria").

  3. Pick the condition you want, and fill in any number it asks for.

  4. Add the next steps under Yes — continue. Steps can only follow the Yes branch.


Which conditions can I choose?

  • Has visited recently: the member has visited in the last number of days you set (In the last X days, 7 by default).

  • Has active membership: the member has a membership that is currently active.

  • Has specific membership: the member is on the membership plan you choose.

  • Attended enough classes: the member has attended at least the number of classes you set (Minimum classes attended, 1 by default).

  • Has overdue payment: the member has a payment that is overdue.

  • Is still a prospect: the person hasn't become a member yet.

  • Has active direct debit: the member has an active Direct Debit.


Can I make the workflow carry on when the answer is No?

No. A condition step only lets members through when the answer is Yes. Members who don't match always leave the workflow at that step, and there's no setting to reverse it.

This means a condition can't send a message only to members who don't match something, for example only to members who haven't renewed or haven't been to a class. Choose conditions that describe the members you do want to message.


Where should I put a condition step?

Put it just before the step it's protecting, and after any wait step, so the check runs when the answer can have changed. For example, in a workflow that sends a reminder to new members after a week:

  1. Wait 7 days.

  2. Condition: Has active membership.

  3. Send the reminder. Only members who still have an active membership get it.

💡 Tip: If you check before the wait instead, a member who cancels during the wait would still get the message.


Related help articles

Did this answer your question?