Automations put a team's routine decisions on autopilot. Each one is a decision tree: a trigger decides when it runs, and every athlete who enters is checked against your conditions and acted on, such as starting a program, changing their groups or sending a survey. This article covers building an automation, every trigger, condition and action it offers, turning it on, and reading its run log.

Automations belong to a team. Open Automations in the team's navigation to see its list. Only coaches who can edit the team see New Automation (1) and can open an automation (2); select rows to Delete several at once.

The canvas draws the tree from the top down: the trigger (1), then a decision (2) fanning out into its routes (3), each leading to what happens on it, like an action (4). Click any card to open its editor. Click the + under a card to add a node there; the new node goes between that card and everything already below it. A route with nothing on it yet says Nothing happens on this route yet.

Editors have no save button: every field saves as you change it. Run log (5) and Settings (6) sit in the header.

Picking a kind adds the node straight away:

Every automation has exactly one trigger, and it can't be deleted. Its Runs section has three switches (1). You can turn on more than one; a new trigger starts with When data changes on.

When data changes runs the automation for an athlete each time their data changes: a logged workout, a recorded or imported measurement, a calculated assessment, or an integration sync. It does not run when an athlete opens or starts a workout.

On a schedule runs the automation for every athlete on the team. Its Schedule section (2) sets:

The dark strip at the bottom shows the next run, how the last run went, and how many athletes enter. While the automation is inactive, a notice (3) says so, with Turn it on.

When an athlete joins the team runs once for each athlete who joins. Use it for onboarding, such as adding newcomers to a group and starting their first program.

A decision sends each athlete down one of its routes. Routes are checked from top to bottom and the first match wins, so an athlete only ever takes one. Drag a route by its handle to change the order.

Click a route (2 in the decision editor) to set its Name, Color and Conditions. Conditions sit in sets:

The route above reads Readiness value is less than 6 out of 10 (1). Two sets work like this:

A route with no conditions can never match, so every athlete skips it.

Each condition asks What are we measuring?, then a Comparison, then what it's Compared to.

A training load metric is listed by its streams, such as its total or its ratio, not by the load itself, which holds no values of its own.

Teams with Flex program generation also see Subscription entitled, Next unfilled week starts, Program ends, Extension completed and Athlete emailed.

A condition compares one athlete's own data, so it can't compare them to a group's or a position's average. The closest options are Percentile rank, which ranks them against your organization's athletes, and Another metric, which compares one of their metrics to another of theirs.

A filter uses the same conditions as a route. Athletes who match continue to what's below it; everyone else stops there. A filter with no conditions lets every athlete through.

An action does something to each athlete who reaches it. Pick its Action type (1), then fill in the Options (2) for that type. Changing the type clears the options, but keeps the action's name.

Pick the Program, then when Program starts:

Workout window sets when each workout sits on the athlete's calendar, 7:00 AM to 8:00 AM unless you change it. An athlete already enrolled in that program isn't enrolled again. See Programs.

Only teams with Flex program generation have this action. It adds weeks to the program the athlete is already running, carried on from where they are. There's nothing to set.

Pick one or more Groups. If another automation on the team has a condition on one of those groups, a notice warns that adding athletes here may start it too. Groups can also decide which workouts an athlete gets; see Groups.

Pick Groups, Group tags, or both. The athlete leaves every group you picked and every group carrying one of the tags. To keep an athlete in just one "skill level" group, put a Remove from a group action for the skill-level tag before the Add to a group action on each route.

Pick the Survey. The athlete gets a workout called "Survey" on today's calendar holding just that survey, at most once a day per survey. See Surveys.

A Flex decision has no conditions. Give it Context it should weigh for every route, and give each route Criteria in plain words. Flex reads the athlete's profile, groups, current injuries and recent training, and places them on one route, so a route like "if the athlete is injured" works. A Flex decision has no See who goes where.

A Flex action follows the Instructions you write when an athlete reaches it. In both, type @ to mention a group or metric (and in a Flex action, a program or coach) so Flex knows exactly what you mean. See Flex.

New Automation also offers With Flex: say what should trigger it and Flex wires the steps. You can also ask Flex to build or change an automation at any time. An automation Flex builds opens as a Draft: it isn't on the list until you click Save to library, and Discard draft throws it away. A draft can't be turned on until it's saved.

Click Settings and switch Status (1). It saves straight away, and the badge beside the automation's name changes between Active and Inactive. Settings also holds the Name, Add description, and Delete automation.

Click Run log to see every time the automation ran for an athlete, newest first, with Athlete, Run Time, Terminal Node (the step the athlete finished on) and Status (Running, Complete or Error) (1). The log keeps the most recent 500 runs.

Click a run (2) to open its details: a Summary of how it ended, then its Steps in order, with the last one open. Each step has a badge, like the decision's Continued (1) and the action's Action taken (2) above:

A Flex decision or Flex action that used an athlete's health information (the athlete has a current injury, or Flex read their injuries during the run) is flagged. Only staff with PHI access for that athlete see the step's reasoning, actions and conditions. Everyone else still sees the step's name and badge, with "Hidden: this step used athletes' health information, which your role can't view." in place of the details. See Staff access for who holds PHI access.

There's no copy button on an automation. To copy automations to another team, open Transfers from your account menu and include them in a transfer (see Transfers). The metrics and groups they use travel with them. Transfers appears for coaches who lead an organization or a team.