Skip to main content
Where to find this: Tools → Automations
This is your complete reference for building automations in CoachIQ. Use it to look up available options when you’re in the automation builder.
New to automations? Start with Build Your First Automation for a hands-on walkthrough, and see the Builder Reference for what each section of the builder does.
An automation has up to four parts. The builder shows them as sections on one page:

All Triggers

Triggers determine when your automation runs. There are 12. Each trigger has different condition fields available to filter who it applies to, and every trigger also exposes the user fields (ID, email, phone, first name, last name) of the person the event happened to.
Fires when a new user is added to your account.
Fires when someone purchases any product.
Fires when someone books a session.
Fires at the scheduled start time of a booking.
This trigger executes at the booking’s scheduled start time, not when someone checks in.
Fires when a booked session ends.
This trigger fires at the booking’s scheduled end time. It is the trigger to use for “after the session” follow-ups, such as tagging someone who has finished a trial.
Fires when someone cancels a booking.
Fires when someone submits a form.
Fires when a tag is added to a user.
Fires when a tag is removed from a user.
Fires when someone cancels their subscription.
Runs on a schedule and finds all users matching your conditions. See Scheduled Automations for details.Schedule Options:Every schedule also has a timezone, set on the trigger itself, and a send mode that controls whether a matching person is messaged only the first time they match or on every run. See How Scheduled Automations Run.Available Conditions (minimum 1 required):
At least one condition is required for scheduled automations.
Fires when an external system sends a request to this automation’s webhook URL. Use it to start an automation from another tool (a website form builder, a CRM, a payment platform).Once the automation has been created, the builder displays the webhook URL to send to. Treat that URL as a secret.The payload’s fields are also available as dynamic fields in your actions, for example {{payload.userId}}.

Conditions

Conditions decide whether the automation continues for a given event. Each rule has three parts: a field (from the trigger, the user, or a data source), an operator, and a value. Some curated rules, such as Is a subscription or User’s first booking ever, fix the operator and value for you.

Operators

The builder narrows the operator menu to what makes sense for the field: numbers get equality, greater/less than, and empty checks; dropdowns get equality, contains, and empty checks.

And / Or groups

Rules live inside groups. Each group is either:
  • And — every rule in the group must be true
  • Or — any one rule in the group is enough
Click Add Condition to create the first group, Add Rule to add a rule to the current group, and Add And/Or to nest a new group inside it. Nesting lets you express things like “(bought a membership or a credit pack) and has no future booking”. If an automation has no conditions at all, it runs for every trigger event. Scheduled Check is the exception: it requires at least one condition.

Data Sources

Data sources fetch extra information before the conditions run, so you can filter on it and use it in messages. Add one when the trigger alone doesn’t carry what you need. There are six. Unless you pick a specific person, each one looks up the user from the trigger.
Finds open slots on a session.Outputs: the list of slots, the slot count, and the first available slot.
Fetches a person’s bookings.Outputs: the list of bookings, the count, the next booking, and the last booking.
Fetches a person’s credit balance in one credit bank.Outputs: the balance, the credit bank ID, and the credit bank label.
Fetches a person’s purchases.Outputs: the list of purchases, the count, active subscriptions, one-time purchases, whether they have an active subscription, and whether they own a given product.
Fetches a person’s tags.Outputs: the list of tags, the count, the tag IDs, and the tag labels.
Fetches responses to a form.Outputs: the list of responses, the count, and the latest response (its answer, question, form, and date).
Data source outputs appear as field options in Conditions and in any message field. In a message, type # to pick one from the list rather than typing it by hand.

All Actions

Actions determine what happens when your automation runs. There are 17. You can add multiple actions to a single automation; they run in order. Most actions have a Target User. It defaults to User from trigger; click Change to pick a specific person instead. The messaging and tag actions also offer trigger user and their guardians, which runs the action once for the athlete and once for each linked parent in your group. (A parent who triggers an automation is always a single target; the expansion never adds children.)
Sends an email to a user.
Send an Email has no attachment picker. To send someone a booking, product, or form link by email, paste the link into the message. The in-app, SMS, and announcement actions below can attach a session, product, or form directly.
Sends a text message to a user’s phone.
SMS attachments are text links only—no images or files. Keep the message under 160 characters to stay in one segment.
Sends a message to the user’s inbox within CoachIQ.
Posts an announcement to one person or a group of users.
Use announcements for broadcast messages (like weekly schedules) instead of individual messages.
Adds a tag to the user for organization and targeting.
Removes a tag from the user.
Sets the value of a custom profile field on the user.
Useful for stamping a date (“Trial completed on…”) or a status (“Onboarding: done”) onto the profile so you can filter on it later.
Adds session credits to the user’s account.
If you select a specific product bank and the user doesn’t own that product, credits are added to Master Credits instead.
Removes session credits from the user’s account.
Grants a user a product without payment.
Removes a product from a user’s account.
Gives a user access to a program.
Removes a user’s access to a program.
Books a user into a session. This is a staff-managed booking: it works even when the session is not self-bookable, but it still respects the scheduler’s booking window, athlete limits, slot capacity, and coach conflicts.
Cancels a user’s booking.
Pauses the automation before continuing to the next action.Continuation Conditions (optional):
If a continuation condition isn’t met, the automation stops for that user.
Sends data to an external URL for integrations.
The webhook payload automatically includes full trigger context (user data, event details, etc.).

Dynamic Fields

Dynamic fields let you personalize messages with real data from your automations. In any message field, type # to insert a field option from the trigger or a data source, or @ to insert a CoachIQ field such as the athlete’s first name. The builder inserts the token in the exact syntax shown below.
If you copy and paste a field instead of inserting it, include the double curly braces {{ and }} exactly as shown.

User Fields

Available in all automations, for the person the event happened to:

Trigger Fields

Each trigger adds the fields of the thing that happened. Insert them with # to see the exact list for your trigger:

Booking Fields

Available in booking-related and Scheduled Check automations:
Use {{field.booking.session.title}} in booking confirmations to remind users which session they registered for.

Credit Fields

Available in automations that check credit status:
Credit fields are primarily available in Scheduled Check automations. Using them in other automation types may return empty values. For an exact balance in any automation, add a User credits data source instead.

Data Source Fields

Each data source you add contributes its outputs as field options. Insert them with #. The most useful ones:

Example Usage

Here’s how to use dynamic fields in a message:
This would send:

Build Your First Automation

Step-by-step beginner guide

Automation Playbook

Ready-to-copy recipes

Scheduled Automations

Time-based automation guide

Builder Reference

What each section of the automation builder does

Forms Overview

Build forms that power the Form Submitted trigger

Responses and Automations

See how form responses connect to automation triggers

Product Overview

Set up products that power purchase and subscription triggers

Attach Products

Attach products to messages sent by automations

Scheduling Overview

Manage sessions referenced by booking triggers and actions

Creating Your First Scheduler

Set up schedulers used in Add Booking to User actions

Inbox Overview

Where automated in-app messages are delivered

Announcements

Learn about the announcement action for broadcast messages

Tags and Filters

Manage the tags used in trigger conditions and tag actions

People Overview

Manage member profiles that automations interact with