> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# What can start a workflow, and its steps

> The events that can start a workflow, the steps it can take, how timing works, and how goals stop it for each person.

Every workflow has a trigger (what starts it), steps (what it does) and usually a goal (what stops it). You describe these in plain words and Agents builds them.

## What can start a workflow

* **Registration:** a registration is confirmed (or only someone's first registration), cancelled, or a waitlist spot opens.
* **Trials and intro classes:** booked, rescheduled, cancelled, attended, missed or declined. Declined means the family tapped **Not for us**, or staff marked the trial **Not continuing**. Trials booked by staff with **Add attendee**, or by Agents, start trial workflows too.
* **Classes and attendance:** someone checks in or is marked absent, a class is cancelled or moved, someone stops coming for a number of days, or a set number of hours before each class.
* **Appointments:** booked (or booked with few credits left) or cancelled.
* **Payments:** a payment comes in or fails.
* **People and leads:** a new lead comes in, a lead goes quiet, or a member's birthday.
* **Forms and messages:** a form is sent in, or a text, email or WhatsApp message comes in.

You can limit any trigger to certain programs.

## Steps a workflow can take

Wait. Wait until a set time before the class. Only continue if something is true (a check). Send an email. Send a text. Create a task for your team. Email your team. Ask AI to decide, with a yes or no question (no stops it).

"Right away" or "within the hour" sends with no wait. "The night before" or "the day before" a class sends 24 hours before it starts. Click the timing to change it.

## Your words, sent as written

You write each message once, or Agents drafts it for you to edit. It is sent exactly as saved. Names, programs, class times and links change for each person. They are underlined in the message, and **Personalize** adds another while you edit. Messages about anyone under 18 go to their parent or guardian. The enroll link opens the program's sign-up already filled in for that family.

Messages on the attended or missed trial triggers can include `{{not_for_us_link}}`. It gives the family a one-tap way to say no.

## Goals and checks

A goal ends the workflow early for that person, like "Stops when they enroll". Before every message, the workflow checks the goal again. So a family that enrolled, in any way, never gets another follow-up.

A check like "Only if they haven't enrolled" ends the workflow quietly once it is no longer true.

## Common questions

> [accordion] How do goals work when a workflow runs for children?
>
> A parent's payment ends it only for the children that payment covered. A reply or a form from the parent ends it for every child in the family.

## Related

* [Create a workflow](/docs/agents/workflows.md)
* [Manage a workflow](/docs/agents/manage-workflows.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.