Skip to content
All 148 help articles

Every automation trigger and what starts it

All 22 triggers, grouped the way the picker groups them, with what each one needs, who it picks up and whether it looks back.

5 min readUpdated
  • automations
  • triggers
  • email

The trigger is the moment that puts someone into an automation. Click the trigger at the top of the canvas, then Change, to open Choose a trigger. They are grouped by what they are about, and there is a search box at the top.

Some triggers need one more choice before the automation can be turned on: a course, a lesson, a list, an event. Drry will not let you turn it on until it is set.

Joining and milestones

These pick up members.

  • On join: a new member joins the community.

  • N days after join: day 3, day 7, whenever you choose. Set After how many days. A member enters when their Nth day arrives, as long as that moment is after you turned the automation on.

  • Goes inactive: no activity for N days, counted from the member's last visit. Set the days.

  • Comes back: a member returns after being away for N or more days. Set the days. Only returns after you turned the automation on count.

  • Membership milestone: a tenure milestone, N days after they joined. It times the same way as N days after join.

Events

These all need an event. For a repeating event you can choose Every session on the three that pick people up from an event. See Run an automation for every session of a recurring event.

  • Registers for an event: a member RSVPs "going" to the event you choose. Everyone who has already RSVP'd is picked up when you turn it on, and later RSVPs join as they come in. A member who cancels their RSVP leaves the journey. This counts members only: someone who signs up on a public event page without being a member has no RSVP, so use Everyone who registered or showed up for them.

  • Everyone who registered or showed up: one event's whole list. It picks up contacts: the people you invited from a list, the people who signed up on the event page, and anyone who turned up. Add an "Attended the event" branch to split the follow-up. Someone who opted out of event emails is left out. There is an optional Add people who attend to a list setting that puts the people who actually turned up, and have an email address, on a list you choose.

  • Everyone on a list, timed to an event: everyone on a list, or every member if you leave Which list (optional) empty, rides one event's timeline with no RSVP needed. Pick a list and the contacts on it come in, whether or not they are members. Everyone already in the audience is picked up when you turn it on, and anyone who joins later comes in as they arrive.

  • Books a session: someone books time with you on your booking page. Leave Which session (optional) on any session, or pick one session type. Each booking is its own run, so a second booking starts it again. A canceled booking ends that run.

  • Only the people who attended: after an event ends. For an event hosted in Drry it uses who actually attended. For an in-person event or a pasted Zoom or Meet link there is no attendance to read, so it uses who RSVP'd, which can include someone who did not come. It is not tied to one event: each member enters once, the first time they qualify after you turn it on. Members only.

Courses

These pick up members.

  • Starts a course: a member's first activity in the course you choose, made after you turned the automation on. Someone who started it before does not count.

  • Course stalled: started the course, has not finished, and has had no activity for N days. The N days must run out after you turned the automation on.

  • Course complete: finishes every published lesson in the course, after you turned the automation on.

  • Halfway through a course: reaches half the published lessons without finishing. Members already past halfway when you turned it on are not picked up.

  • Completes a lesson: finishes the specific lesson you choose, after you turned the automation on.

Community

  • Makes their first post: a member's first community post or comment, made after you turned the automation on. Someone who has posted before is not picked up.

Leads and audiences

These pick up contacts, who have to be subscribed.

  • Signed up, didn't join: a lead you captured, after you turned the automation on, who has not joined the community. Optionally filter by Where they came from. They leave the journey if they join.

  • Joined a list: a contact is added to the list you choose, for example by a signup form. Optionally filter by where they came from. Only people added after you turned it on come in, unless you switch on Include people already on the list. See Send a follow-up sequence after someone signs up.

  • Submits a form: someone fills in a form. Leave Which form (optional) on any form or pick one. Every submission from then on is a run of its own. With one form chosen you can branch on its answers, and with any form you can still branch on where they came from.

Shop

  • Leaves checkout without paying: someone gives their email at your shop checkout and does not pay within 30 minutes. Optionally pick a product and an offer to include. See Remind shoppers who left checkout.

Membership and billing

These pick up members.

  • About to cancel: a member scheduled a cancellation but still has access. This is your window to win them back. Only cancellations scheduled after you turned the automation on count.

  • Cancels their subscription: a member's paid membership has lapsed, after you turned the automation on.

Common questions

Can a tag or a segment start an automation?

No. Only the triggers above can. A list can, through Joined a list. See Tags in automations: what they can and cannot do.

Which trigger do I use for a webinar follow-up?

Usually Everyone who registered or showed up, because it covers people who signed up on the event page as well as people who turned up. See Time emails around an event.

Related