The builder lays an automation out as rows you read top to bottom: When, Only if, the steps, and Settings. Click a row to edit it in the panel beside it. Build from scratch here, or start faster from a template or by describing it to Dumby.
Steps
- Click Automations in the sidebar, then New automation.
- Click the When row and choose what starts it under Start when. Fill in its settings, such as the services, forms or tags it watches. Leave a list like Services or Forms empty to mean any.
- To narrow who it runs for, click Only if, then Add condition. Pick a fact (such as Tags, Goal or Age), a comparison, and the values. For Age, choose is at least or is at most and type a number of years, such as 70.
- Click Add a step and pick what Strix should do, such as Message the client or Notify staff. Fill in its fields in the panel.
- To space steps out, choose Wait from Add a step, then set the Amount and Unit (Minutes, Hours, Days or Weeks).
- Use the ⋮ menu next to a step to Move up, Move down or Remove step.
- Click the Settings row. Give it a Name and choose Can the same client run this again? If your gym has more than one location, pick the Locations it runs at, or leave it empty for all locations. Under Stop early when, tick anything that should end a client’s run, such as They book a session.
- Click Save draft to keep it without turning it on.
- When it reads right, click Turn on and confirm with Turn on.
Good to know
- A draft does nothing. Turning it on starts runs from the next matching event; nothing that already happened starts a run.
- Rows the automation can’t run with yet show Fix. Turning on is refused until each one is filled in, and the panel says what is missing.
- Under a message, click an Insert button (such as First name or Team name) to fill in details for each client. Some triggers add their own, such as Visit date and Coach for visit triggers or Renewal date before a renewal. A blank Subject on Message the client uses your team name.
- Before you turn it on, open More actions (⋮) and click Test run to see who it would have reached over the last 30 days. Test runs save your edits first.
- Leaving the builder with unsaved changes asks before you go.
- An automation limited to some Locations only starts for clients at those locations, and a client who moves to another location stops at their next step. Clients with no location never match one. Leaving Locations empty runs it at every location, including ones you add later.
- Automations list as Live, Draft or Paused, with the runs this week. The tabs at the top filter by status and Needs attention.
Related
- What automations can do
- Test an automation
- Pause or change a live automation
- Start an automation from a template
Last updated