FYTT's automation tool enables you to automate important decisions and workflows. Using automations, you can visually map out decision trees that will execute automatically in response to changes in athlete data.

When an automation is triggered for a given athlete, they will traverse the nodes in the tree based on your conditional logic, and your specified actions will be executed along the way.

This gives coaches an intuitive and flexible way to create automated decision trees, which can drastically improve coaching efficiency and the quality of athlete training.

Automations are team-specific, so every team has its own automations section. You can access the automations for a given team from the automations icon in the team navigation bar.

The first node for every automation is a "trigger" node. Automations are triggered for a given athlete based the settings defined in this node. You have several options for configuring the trigger node:

It usually makes sense to have just one trigger type active, but you can configure it in whatever manner makes the most sense for your use case.

With a responsive trigger, the automation is executed for an athlete whenever their metric data is updated. This means that the automation runs when metric measurements are recorded from the metrics hub, from the athlete dashboard, from the API, or from a metric test or survey in a workout (via phone, tablet, digital whiteboard, etc.).

Timed triggers allow you to trigger the automation on a regular schedule. The timing of the trigger can be configured in several ways:

When a timed trigger is activated, the automation is triggered for every athlete on the team, and actions are executed according to the automation's logic.

You can check the "join team" option on the trigger node to trigger the automation whenever an athlete joins the team. This can be useful for triggering onboarding workflows, like deploying an introductory program or sending out a survey.

Decision nodes allow you to create branching logic so that athletes are filtered down one of any number of routes based on conditional logic. To add a decision node, click on the "plus" icon of a terminal node, then select the "decision node" option.

It's usually a good idea to give the decision node a brief name to describe what decision is being evaluated.

By default, every decision node has at least two routes, and the last route will be followed if none of the conditions for the other routes are met. For all routes except the last, you can add conditional logic to determine whether a given athlete should follow the route.

You can combine conditions to create conditional blocks. The logic for all conditions in a block must evaluate to true in order to meet the criteria.

The logic above is equivalent to the following:

You can create multiple conditional blocks for a route. If the logic for any of the blocks evaluates to true, the athlete will follow the route.

The logic above is equivalent to the following:

You can add as many routes as you need to create the different branches of the decision node.

Once you're done building out the logic for each route, you'll see the routes mapped out in the automation.

The end goal of an automation is to automate the execution of some action to help you be more efficient. To add an action to a route, click the "plus" icon in the terminal node of the desired route, then select the "action" type.

This adds an action node to the route, which you can configure with a number of different action types:

If an athlete hits a "start program" node, the selected program will be assigned to the individual athlete. Since programs always start on Sundays, you can specify whether you want the program to start as of the "last Sunday" or starting on the "next Sunday" from when the the action is triggered. You can also specify a start and stop time for the program's sessions if applicable.

You can use the "add to group" action type to add athletes to one or more groups if they hit the node.

You can use the "remove from group" action type to remove athletes from one or more groups if they hit the node.

Additionally, you can chose to remove athletes from all groups with a given tag. This is useful if you want to ensure that an athlete is removed from any group with the given tag before adding them to another group.

For example, suppose you have a decision node that determines an athlete's skill level. The end goal of the automation is to assign an athlete to just one of the "skill level" groups. To accomplish this, you could add a "remove from group" action as the first step in each route before the action that adds athletes to a different group.

This logic would ensure that an athlete doesn't get added to multiple skill level groups.

You can use the "send a survey" action node to add a survey to an athlete's schedule if they hit the given node. Here's some common use cases for the survey node: