How do I set up an automation?

A trigger, optional conditions, and one or more actions. Which triggers fire instantly, which wait for the nightly pass, and how to check a run.

The short answer

A trigger, optional conditions, and one or more actions. Which triggers fire instantly, which wait for the nightly pass, and how to check a run.

Automations › New automation, or tap a ready-made card

Steps

  1. 1
    Open Automations and press New automation.
  2. 2
    Pick the trigger. If it takes a number of days, set it.
  3. 3
    Add a condition only if you want to target part of your members.
  4. 4
    Pick the action. For Send message, choose a template and tick the channels.
  5. 5
    Give it a name if you want, then create it.
On this page8

Three parts, always in the same order

Path: Automations › New automation, or tap a ready-made card.

Every automation is a trigger, then optional conditions, then one or more actions. The summary at the top of the editor writes it out as a sentence and updates as you build.

Under your own automations sits a library of ready-made cards, Start from a template, which prefills the editor for a common case. It fills the trigger and the number of days it works on, never the message: you still pick the template.

Three parts, always in the same order
Automations: the Start from a template library, which prefills the editor.
With Send a message selected, Activate stays greyed out until you pick which message. You can write a new one without leaving the editor.

The eleven triggers

A member joins. Membership expires soon. Membership expired. Membership renewed. Payment received. Payment failed or overdue. First check-in. Session completed. No check-in for X days. Member birthday. New lead.

Session completed fires when an attendance is recorded. It can be narrowed to one class or service by name, and it is the only trigger that carries a send delay in minutes, so a thank-you message can land an hour after the session rather than while the member is still putting their shoes on.

Which triggers fire instantly, and which wait for the night

Seven fire the moment the event happens: a member is added, a membership is renewed, a payment is saved as paid or overdue, a first attended check-in is recorded, a session is completed, and a lead comes in from your form.

Four are date based and are checked once a day by a scheduled job: membership expires soon, membership expired, member birthday, no check-in for X days. They match an exact day. Expires soon fires when the end date is exactly X days away, expired fires the day after the end date, and no check-in fires exactly N days after the last attended visit.

Each date-based run is recorded so the same member is not messaged twice on the same day.

Exact day means no catching up. A member who is 8 days from expiry is not caught by a 7-day rule, and if the daily job does not run on the right day, that day is simply missed.

Everything dated depends on scheduled jobs, and there are four

Four separate calls to the server, on four different rhythms, all protected by the same secret. The main one carries the date-based triggers, the class reminder, the expiry reminders and the no-show sweep. A second one runs about every quarter of an hour and carries the delayed sends and anything held back by your quiet hours. A third one carries the workflows. A fourth one carries the automatic backup.

Without those calls, or without the secret, nothing runs and nothing is marked. It fails silently: no error appears on any screen. A delayed send that never leaves is almost always the quarter-hourly one missing.

A gym whose trial or subscription has ended is skipped by the main pass and by the quarter-hourly one, even for automations still switched on. The workflow pass does not make that check, so a marketing sequence can keep sending after the subscription stops.

Conditions filter, they do not create

A condition tests one field of the member: plan, membership, discipline, status or tag, with is or is not. Add several and all of them must be true.

Membership is special: it checks whether the member currently holds an active, non-expired membership of that type, not what is written on their profile.

No check-in for X days only looks at active members who have at least one attended visit. Someone who signed up and never came is never picked up by that rule.

A condition left on Select compares against nothing. It then only matches members whose field is empty, which is almost never what you meant. Fill every condition or remove it.

Channels: connected, and reachable for that member

Inside the Send message action you tick channels. Email is always available. LINE, WhatsApp and SMS appear greyed with the word connect until your gym has connected that account in Settings › Integrations.

At send time each channel is checked again for that specific member. Email is skipped if the member has no address. LINE is skipped if the member never linked their LINE. WhatsApp needs a phone number and a Meta template on the template. SMS needs a phone number.

WhatsApp and SMS also require the plan that includes them. An automation written while you were on a higher plan stops using those channels after a downgrade, silently.

The other actions

Create task writes a note on the member's timeline, prefixed with Task. It is a note for your team, not an entry in a separate task list.

Notify staff emails one coach if you pick one, otherwise the gym account address. It can also add a line to the reception note on the dashboard, and it writes a Staff note on the member's own file, which is where those notes you did not type come from.

Add tag and remove tag write on the member profile. Assign coach does NOT: it only writes a line in the member's timeline saying who they were assigned to, and no coach field changes anywhere. You can stack several actions on one automation; they run in order and the activity log keeps one line per action.

For the New lead trigger there is no member profile yet, so create task, add tag, remove tag and assign coach are skipped. A lead has no linked LINE either, so LINE never works there. Email, SMS, WhatsApp and Notify staff do work on a lead, as long as the lead has a phone number for the last two.

Checking that it really ran

Each card shows its trigger, a summary of its actions, and when it last ran. The switch pauses and restarts it.

The Activity button lists each run: the automation, the member, and what was actually done, for example sent Renewal reminder to email, skipped LINE not connected. A green tick means at least one action succeeded.

Automations are part of the Pro plan. If your plan no longer covers them, nothing runs at all, even for automations still switched on.

The activity log keeps the last 300 entries per gym. Older runs are dropped, so check it while the problem is fresh.