Skip to content
All 148 help articles

Conditions: the questions an automation can ask

Every condition you can use in an If / else, a split, a condition wait or a goal, and which ones only work for members.

3 min readUpdated
  • automations
  • conditions
  • branches

A condition is a yes or no question about a person. You use one in four places: an If / else step, a Split paths step, a Wait until step set to A condition, and the journey's goal under Stop at a goal.

The conditions

  • Finished a course: they have completed every lesson in the course you pick.

  • Opened the last email: they opened the previous email this journey sent them.

  • Clicked the last email: they clicked a link in the previous email this journey sent.

  • Is a paying member: they have an active paid membership, not a free or comped one. A free trial does not count as paying.

  • Active in the community: they have posted, replied or liked at least once.

  • Has a tag: they carry the tag you choose.

  • Is on a list: they are on the list you choose.

  • Joined the list after this went live: new since you turned the automation on, as opposed to the people who were already on the list. It sorts a back-fill from everyone who arrives afterwards.

  • Attended the event: they turned up to the journey's event, at least a minute in the room or the stream, and did not just RSVP.

  • Filled in a form: they have submitted the form you choose. It is matched on the email address they used, so someone who filled it in with a different address reads as not having.

  • Their answer and Where they came from: about the form submission that started the run. They only exist on a Submits a form journey.

Attended the event has limits

  • It only works for an event hosted in Drry. For an in-person event or a pasted Zoom or Meet link nobody passes through Drry, so there is no attendance and everyone would read as not attending. Drry refuses to turn the automation on in that case and tells you why.

  • A Wait until step cannot hold on it. It would release the moment someone joins and email them mid-session. Wait until the event ends first, then branch.

  • It needs the automation pointed at one event, so it cannot be used with Every session on a repeating event. See Run an automation for every session of a recurring event.

A goal is a condition too

Switch on Stop at a goal under When to stop and pick a condition under They are done when. It is checked before every step, and anyone who already matches leaves the journey right then. It is never checked before someone's first step, so a goal that is already true when they arrive does not remove them before the journey has said a word. Unlike most edits, a goal applies to people who are part-way through right now.

Related