Skip to main content

Which triggers and steps can I use in an automation?

Every trigger that can start an automation and every step that can follow, in short.

Written by Nettla

An automation starts with one trigger, under When a player…, followed by your steps in order.

Triggers

  • Joins the player list: once per player.

  • Joins a cohort: choose the cohort. Players already in it when you activate aren't included.

  • Completes a booking or session: choose the booking types, optionally one activity or coach, and Every time, First time or Nth time.

  • Hasn't played for a while: choose the number of days. Players enter on the day they reach it, and only if they have no upcoming booking.

  • Membership starts: club memberships only, not company-wide ones.

  • Membership expires soon: choose the days before expiry. Only memberships that don't renew automatically.

  • Birthday today: uses the date of birth on the player's profile.

  • On a schedule: weekly on the days you pick, or monthly on a day from the 1st to the 28th. It goes to every player, so start with a Condition to choose who. See "How do I send a weekly email of upcoming matches and activities?".

  • Once, on a date: runs one time, on the date and hour you pick. Choose who with a Condition, as for On a schedule.

Daily, scheduled and one-off triggers run at the Run at time you choose, between 06:00 and 21:00 club time. Where it applies, How often can a player get this? sets once, every time or at most once every number of days.

Steps

  • Delay: wait a set time (up to 30 days) or until a time of day.

  • Send message: a Push notification (up to 120 characters, with your club's name as the title) or an Email from one of your email templates. For a push, Opens sets where it leads: Its notification, A page in the app or A channel.

  • Condition: only players who match continue, for example by number of bookings, upcoming booking, membership, membership type, cohort, gender, age or level.

  • Add to cohort: adds the player to a cohort.

  • Add to channel: adds the player to one of your channels. Players who left or were removed from it are never added back.

  • Notify staff: sends your staff a notification with a note about the player.

  • Send to integrations: sends an event to another tool. See "How does the Send to integrations step work?".

  • End: stops here, and can move the player into a cohort.

Good to know

  • Anything that happens while an automation is a draft or paused is missed, except new members of a cohort trigger.

  • A push that opens a channel only goes to that channel's members.

Did this answer your question?