What automations can do

Every trigger, condition, step and setting the automation builder offers, so you can tell whether a routine can run without you.

Who can do this
Owners and team admins
Where in Strix
Automations, New automation

An automation is a routine Strix runs for each client who matches it: something starts it (When), optional conditions narrow who it runs for (Only if), then its steps run one after another. Owners and team admins find it under Automations in the Your Gym group of the sidebar.

Steps

  1. Pick what starts it. Under When, the builder offers:
    • A visit is booked, for any service or the Services you pick.
    • A visit’s status changes, to the statuses you pick under Changes to: Booked, Requested, Confirmed, Checked in, Waitlisted, Cancelled, Early cancel, Late cancel, No show or Rescheduled.
    • A client checks in for their first visit, overall or to one of the services you pick.
    • A client reaches a session milestone: their 100th, 250th, 500th or 1,000th session, or any session count you type under Milestones, such as 95 to have a badge ready before their 100th. Any milestone also counts every 500 after 1,000. Sessions are counted the way the check-in board counts them, including imported history, and each milestone starts it once per client.
    • A client reaches a repeating session count: every so many sessions, picked under Repeat every. 10th session starts it on the 10th, 20th, 30th session and so on. Pick 5th, 10th, 20th, 25th or 50th, or type any count from 2 to 500. Sessions are counted the same way as milestones.
    • A visit is coming up, from 1 to 72 hours before it (How long before).
    • A visit is coming up with no workout planned, from 1 to 72 hours before it, for any service or the Services you pick.
    • A client creates their account in the app.
    • A tag is added or removed, for any tag or the Tags you pick.
    • A client’s lead source is set or changes: pick the Source that starts it, such as Instagram, or leave it empty for any source. Under Changes from, pick No source yet to start only when a client first gets a source, such as a new lead from a flow link or “How did you hear about us?”. Staff setting a source on the profile counts too; clearing one doesn’t.
    • A custom field changes: pick the Field, then under Changes to the new values that start it, such as a partner clinic changing to Northside, a yes or no field changing to Yes, or a date or text field getting A new value or being Cleared. Leave Changes to empty for any change. To catch a move between two values, also pick Changes from, such as a partner clinic changing from Riverside to Northside, or a date that was Empty getting a new value. Saving the same value again doesn’t count.
    • A client’s type changes, From and To the client types you pick (Lead, Free, Client, Inactive, Do not contact), such as a lead becoming a client. It counts changes staff make on the profile, Set the client type steps, and marking a client inactive or reactivating them, by hand or when a new membership’s first payment reactivates them, but not adding someone new.
    • A client moves on the journey board, From and To the member journey stages you pick, by your gym’s names for them, or Off the board, such as someone reaching First visit. It counts moves Strix makes and moves staff make on the board.
    • A client completes a form, any form or the Forms you pick.
    • A client has a required form to sign: a form they must sign to book or train is assigned to them, or they try to book or start a workout without signing one, for any required form or the Forms you pick. It starts once per form they’re assigned, whichever happens first.
    • A client buys something, anything or the Products you pick. It counts once the payment succeeds.
    • A client sets a personal record: their first record on an exercise.
    • A client beats a personal record: a higher value than one of their own records on an exercise.
    • On a schedule: daily, weekly, monthly, a number of days before or after each client’s start date, sign-up date or a date custom field, or yearly on their birthday, gym anniversary or a date custom field.
    • A report on a schedule: one of your team’s shared saved reports, daily, weekly or monthly. It runs once for your whole gym, not per client, so it takes no Only if conditions and only the two report steps below.
    • A client goes quiet: 7 to 90 days without a visit, booking, logged workout or wellness check-in.
    • A client starts drifting: the morning a client shows up on Today’s drift list, for any reason or only the ones you pick under Because of: missed visits, skipped workouts, gone quiet, feeling worse than usual, a program ending with nothing next, a pause ending with nothing booked, or a card that expires before renewal. It starts once each time they start drifting, after 8 am.
    • A client’s vitals are off their usual and A client’s health data stops coming in, once a client on your team shares Apple Health, Garmin, WHOOP or Oura data: when their last 3 finished days of HRV, resting heart rate, sleep or steps fall outside their usual, or after 2 to 14 days without new data.
    • A client is running low on sessions: when their package balance reaches none left, or 1 to 5 sessions left.
    • A client’s program is ending: 1 day, 3 days, 1 week or 2 weeks before the last day of the weeks you’ve published to them. Under Weeks after it, choose whether it starts either way or Only when nothing is published after it.
    • A payment fails, for anything or the Products you pick. Membership renewals count as their membership’s product. It starts on every failed attempt, including each time Stripe retries a renewal. To act only after a few, pick the Failed attempt to start on, such as the 3rd failed attempt, or type any count up to 20. Attempts count in a row, since what failed was last paid. Switch on Wait for Stripe’s retry to skip a renewal’s first failed attempt when Stripe will retry it, since the retry often goes through; payments Stripe won’t retry, like a no-show fee or a renewal the client’s bank needs them to confirm, still start it on their first. Strix already emails the client on every failed attempt and alerts the owner and admins with its built-in Payment failed automations, so build one only to do more.
    • A failed payment is recovered: a membership whose payment failed is paid again and active.
    • A membership is suspended after a failed payment: the 7-day grace period after a failed payment ends unpaid and the membership’s included services are turned off, for any membership or the Products you pick. Strix’s own Block access when a membership is suspended system automation already blocks booking at this moment.
    • A membership renewal is coming up: 1, 3, 7 or 14 days before it renews (How long before). Memberships set to cancel, or to pause before the renewal, are skipped. Memberships paid outside Strix or comped count too, renewing on their start date’s schedule.
    • A membership renews: each paid renewal of a membership after its first payment, once per renewal.
    • A client asks to change their membership: any membership request, or only the kinds you pick under Request: changes (including more or less training), pauses or cancellations.
    • A cancellation is scheduled: staff schedule a cancellation for a later last day, or the client cancels in Stripe’s billing portal, for any membership or the Products you pick. It starts once per cancellation, while the membership still has days left; changing the date doesn’t start it again, and a cancellation that ends access straight away only counts as A membership change takes effect.
    • A membership change takes effect: a pause starts, a membership resumes, a cancellation takes effect or a package changes, any of them or the ones you pick under Change, for any membership or the Products you pick. Scheduling a change doesn’t count; it starts when the change happens. A change counts as the product the membership is on when it happens. A membership Stripe ends without a cancellation in Strix, such as after its last failed retry, counts as a cancellation taking effect, and so does ending a membership paid outside Strix or comped.
    • A lead capture form is submitted (gyms with lead capture): any form or the Lead forms you pick, from Someone new or Someone already in Strix. It starts once per submission.
    • A lead turns hot (gyms with lead scoring): once each time a lead’s score crosses into Hot, not on every rescore while they stay hot.
    • A lead gets an owner (gyms with the CRM): lead routing handing them out or staff picking an owner, By lead routing, By staff or either way. It stops before the next step once the lead changes owner or stops being a lead. Messages can use {{ lead.owner_name }}, {{ lead.details }} (their email, phone and source) and {{ lead.contact_within }}.
    • Someone leaves an intro offer checkout unpaid (gyms with the CRM): any offer or the Intro offers you pick. It stops before the next step once they buy that offer. Messages can use {{ intro_offer.name }} and {{ intro_offer.checkout_link }}.
    • A deal moves to another stage, A deal is won and A deal is lost (gyms with pipelines): for any pipeline or the Pipelines you pick, the stages a deal Moves to, and for a lost deal the Lost because reasons you pick. Each move or close starts it once.
    • An appointment is booked in GoHighLevel and A GoHighLevel appointment’s status changes (gyms connected to GoHighLevel): an intro, sales call or anything else on your GoHighLevel calendars, booked there or from My Calendar. Under Appointments, pick Intros for only the calendar your gym takes intro bookings on, Other appointments, or leave it on any. A booking starts it once, while the appointment is still to come. A status change starts it each time the appointment Changes to Showed, No-show or Cancelled. Messages can use {{ appointment.title }}, {{ appointment.date }}, {{ appointment.time }} and {{ appointment.with }}.
    • A client answers your feedback question (gyms with Reputation): any answer, or Promoter (9–10), Passive (7–8) or Detractor (0–6) under Answer, or exact Scores. It starts once per answer.
    • A referral qualifies (gyms with referrals): when a referred friend does what your program counts. Under Runs for, pick The client who referred them or The friend they referred.
    • Staff start it for a client (gyms with the CRM): nothing else starts it. Staff start it for one client from their profile, or for many from the client list or a Smart List, and see first exactly who will start and who won’t and why. Use it for a lead nurture or any series of emails you send to people you choose.
    • Staff press its button on Today: nothing else starts it. Owners and admins pin it to Today as a button; pressing it shows what it does and exactly who it will start for, and Run starts it for every active client its Only if conditions and locations let in.
    • A client clicks a link in a campaign (gyms with email campaigns): the client’s first click on a link in any campaign or the Campaigns you pick. Only clicks the bot filter calls a person count, and a run stops before its next step if the filter later finds the click was a scanner. Opening an email doesn’t count.
  2. Narrow it under Only if (optional). Each condition tests the client: Client type (Lead, Free, Client, Inactive, Do not contact), Lead source (is any of, is none of, is known or is unknown), Location, Primary coach, Rosters (is in all of, or none of), Tags (has all of, or none of), Age (is at least, or at most, a number of years, worked out from their date of birth), their training profile: Experience, Goal, Injury, Injury areas, Session length, Training days per week, Training environment and Coaching style, Journey stage (any of your stages, or Not on the board), Days in journey stage (at least or at most a number of days), Drifting (is drifting, is not drifting, because of all of, or not because of any of the reasons you pick), once a client on your team shares health data Vitals (are off their usual, are not off their usual, show all of, or show none of the reasons you pick) and Days since new health data (at least or at most a number of days, or has never shared any), what they’re doing now: Next visit (is booked, is not booked, or is in the next so many days), Days since last visit (at least or at most a number of days since their last check-in, or has never visited), Sessions left in their packages (at least or at most), Membership status (Past due, Cancellation scheduled, Billing, Awaiting checkout, Scheduled to start, Canceled or Not billing, the same as the Billing status in Reports) Card on file (has or has no card on file) and, for gyms with the CRM, Lead contact (staff reached them since they got their owner, or nobody has reached them yet), or one of your gym’s custom fields. A choice field can be any of or none of its choices, a number at least or at most a value, a date in the next so many days, and a yes or no field yes or no; any field can have a value or be empty. Conditions are checked again before every step, so a follow-up with Next visit is not booked stops once the client books. A client who has never checked in doesn’t match Days since last visit is at least. A client with no date of birth never matches an Age condition, and a client with no answer for a profile or custom field never matches “is any of” and always matches “is none of”. Add up to 20 with Add condition.
  3. Add steps with Add a step. Each step is one of:
    • Message the client by App inbox, Email and/or Text, with a Subject and a Message that can fill in their first name, full name and your team name. Some triggers add their own details: visit triggers (a visit is booked, changes status, is coming up, is a first visit, has no workout planned, or reaches a session milestone or a repeating session count) fill in the Visit date, Visit time, Service, Coach, Location and a Booking link to your schedule; A payment fails and A client buys something fill in the Amount and What it was for (the product, or the kind of payment, such as Membership or No-show fee, when there’s none), and A payment fails also fills in Failed attempts in a row; A membership renewal is coming up fills in the Renewal date; and A cancellation is scheduled fills in the Last day. Automations on payment and membership triggers send by Email or Text only, so billing stays out of the app.
    • Send the welcome message by Email and/or Text: your welcome from Client emails in Team settings, or the client’s location’s own, with links to download your app.
    • Send the onboarding link by Email and/or Text: the client’s own link to finish their profile and save a card, the same one staff send from the client’s Support tab. Each client is sent it once: someone who already has a link, has finished onboarding or has no valid email is skipped, and the run’s step says why. Start it from A deal moves to another stage to invite a lead when their deal reaches your sign-up stage. See Send or resend an onboarding link.
    • Notify staff: alert the Client’s coach, the Owner, Admins, the Lead owner (gyms with the CRM) or named coaches by App inbox and/or Email. Staff whose permission group leaves out People aren’t told, or Billing in automations a payment or membership starts.
    • Assign a form, sent by App, Email or Text. It skips clients who still have that form open. Once they complete it, a form with Allow repeat sends turned on goes out again, so a scheduled check-in form reaches them every time; other forms go out once. Turn on Dumby asks it in chat to send it as a check-in instead: Dumby asks your questions in the client’s app chat, from their coach (or the owner when they have none), and the coach gets a summary and the whole conversation once they send it. It’s off and can’t be turned on for a form that needs a signature or has file upload, profile field or injury questions. A client without the app, or whose app needs an update, gets it as a plain form by email instead, and the run’s step says so. See Send a check-in with Dumby.
    • Add to a roster or Remove from a roster.
    • Add a tag or Remove a tag.
    • Assign a coach, which makes them the client’s primary coach.
    • Set the client type. It starts automations that use A client’s type changes. Setting it to Inactive also takes the client out of their upcoming sessions and stops their standing bookings, the same as marking them inactive by hand. Setting it to Client also opens the app to someone whose profile is Awaiting activation, the same as Activate app access.
    • Create a task for staff, with an owner, a due time and escalation.
    • Ask for a review (gyms with Reputation): emails the client your private feedback question when the step runs, waiting out your quiet hours; add a wait before it to ask later. Happy members are offered your review sites and everyone else becomes a follow-up for their coach. It follows your Reputation settings, including the wait between asks, so it skips a client asked recently. A visit, personal record or renewal trigger opens the email with a line about that moment.
    • Send the report (report automations only): send the saved report’s results to Each client’s coach (the coach of every client it lists), the Owner, Admins or named coaches by App inbox and/or Email, with an optional Note. Emails can attach the whole report as a CSV, Excel or PDF file.
    • Create a task with the report (report automations only): a task with the report’s results attached, with an owner, a due time and escalation. With Each client’s coach as the owner, each coach gets a task with only their own clients.
    • Block access: stop the client booking and/or starting a workout for themselves, picked under Block. Pick the Reason: Payment, Form, Membership or Custom. It starts from the trigger, so A payment fails starts as Payment and A client has a required form to sign as Form. A custom reason needs a Message for the client, which they see when they try. A Payment block lifts by itself once that payment goes through; for A payment fails, that means paying for what failed, such as the same membership. A Form block lifts once they sign the form, and a Membership block once a membership payment goes through, a paused membership resumes or a cancellation is called off. Custom blocks stay until staff unblock them from the client’s page or an Unblock access step runs. When it blocks booking, Existing bookings picks what happens to the sessions they already booked. Keep and flag them, the default, leaves them booked and flags them for staff. Cancel upcoming sessions cancels every session they have booked that hasn’t started, returns the credits with no late-cancel fee or no-show charge, offers each freed spot to the waitlist, and pauses their standing bookings. A paused standing booking stays paused after the block lifts until staff Resume it from the client’s page. Running the same block again never cancels or refunds twice. Staff can still book for them. Under Notify, pick who hears about it: The client, the Client’s coach, Their location’s admins (every admin when none work at the client’s location), and any email address you type. The client gets an app notification and an email with the reason and a button to fix it: Update your card for a payment block, Sign the form for a form block, otherwise they’re asked to contact their coach. Staff get an app notification and an email with what is blocked, why, and the sessions they still have booked in the next 7 days; typed addresses get the email. When the block lifts, by itself, from an Unblock access step or by staff, the same people get one short notice saying who or what lifted it. The client’s notice never includes the staff note. Leave Notify empty to tell nobody.
      • Staff who book a blocked client or start their workout see a warning naming the reason first. Going ahead is for that one booking or workout and leaves the block on. A blocked client shows Blocked in the client list, on their page, on session rosters and on the check-in board, and the Sessions tab on their page lists each block and every time staff went ahead.
    • Unblock access: lift the client’s blocks on booking and/or starting a workout, for any reason or the Blocks for reasons you pick.
    • Wait from minutes to weeks (up to a year) before the next step.
  4. Under Settings, name it and choose Can the same client run this again?: Every time, After the last run ends, or Once ever. If your gym has more than one location, choose the Locations it runs at; leave it empty for all locations, including ones you add later.
  5. Under Stop early when (optional), tick what ends a client’s run because the automation got what it was after: They book a session, They become a client or member, Their deal is won, Their deal is lost, They reply to an email or They unsubscribe. Report automations don’t have it.

Good to know

  • Up to 20 steps per automation. Conditions are checked when a run starts and again before every step, so a client who stops matching stops there.
  • Stop early when goals are checked before every step, waits included, and only count what happens after the run started. A reply stops the run as soon as it arrives. The run shows as Stopped with the goal it met, such as Goal met: they booked a session, and the step it stopped at says what happened, such as “Sam booked Intro session on Tue, Oct 14”. A run doesn’t start for a client who already met a goal: someone who is already a client for They become a client or member, someone with a session or a GoHighLevel appointment coming up for They book a session, or someone unsubscribed or marked do not contact for They unsubscribe. They reply to an email needs replies to your emails coming back to Strix; until that’s set up it’s greyed out. Out-of-office replies don’t count.
  • A run also stops before its next step once what started it no longer applies: the visit was cancelled or deleted, a no-show was changed to a check-in, a GoHighLevel appointment was cancelled, missed or deleted, or its outcome was corrected, a client who cancelled or missed a visit booked another, a quiet client booked or finished a workout, a failed payment went through, a required form was signed, a client’s vitals are back within their usual, or new health data arrived. Built-in system automations check for themselves instead.
  • A client who is archived stops at their next step, and events from before they were archived start nothing.
  • An automation limited to some Locations only starts for clients at those locations, and it stops a client’s run at the next step if they move to another location. Clients with no location never match one. Changing Locations on a live automation takes effect once you publish the change.
  • When you pick one location in the location switcher at the top of the page, the Automations list shows the automations that run there: those for all locations and those limited to it.
  • Nothing runs until you turn it on, and turning it on never reaches back: only events after that start runs.
  • Message the client steps wait out quiet hours and the daily message limit, and automations skip clients you paused. Set these on the Safety page.
  • Texts go only to clients who agreed to texts, and clients marked Do not contact or archived get no messages.
  • Strix starts every text with your gym’s name and ends it with “Reply STOP to opt out.”, so don’t write either into the message.
  • Every email a Message the client step sends has an Unsubscribe link at the bottom that opens a page where the client confirms, and mail apps such as Gmail show their own unsubscribe button for it. A client who unsubscribes gets no more emails from your automations, but app inbox and text messages still reach them, and so do booking, form, billing and sign-in emails and the emails your built-in system automations send.
  • The client’s profile shows Unsubscribed from automated emails next to their email. If they ask to get these emails again, click Edit on the Contact card, tick They asked to get automated emails again and click Resubscribe. The client can also resubscribe from the page the link opens.
  • Add to a roster, Remove from a roster and the Rosters condition list single rosters, not folders.
  • Taking a client off a roster keeps the training already on their program. Adding them to a roster gives them any training the roster hands to people who join later, dated from today.
  • They book a session also counts an appointment on your GoHighLevel calendars that hasn’t been cancelled or missed.
  • The GoHighLevel appointment triggers start nothing for the appointments already on your calendars when your gym was connected, for a moved or deleted appointment, or for one with someone who isn’t in Strix.
  • Automations can’t charge cards, change bookings or edit programs. If Dumby says a description “can’t do that yet”, the builder doesn’t offer it.
  • The payment triggers, A membership renews, and the pause, resume and package changes follow memberships billed through Strix. Memberships paid outside Strix or comped only start A membership renewal is coming up and the cancellation in A membership change takes effect, because Strix records no payments for them.
  • Only owners and team admins can see and build automations. Coaches see the tasks automations create on Tasks and alerts in their Inbox.

Last updated

All help articles