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

# Build Your First Automation

> Create a welcome email that sends automatically when someone joins—in under 5 minutes

<Info>
  **Where to find this**: Tools → Automations → Create Automation
</Info>

By the end of this guide, every new member will automatically receive a welcome email with instructions to [book their first session](/scheduling/overview). You'll also [tag](/people/tags-filters) them as an "Active Member" so you can easily find them later.

No templates, no shortcuts—we're building from scratch so you understand how it works.

## What You're Building

| Trigger       | Condition         | Actions                                 |
| ------------- | ----------------- | --------------------------------------- |
| Purchase Made | Is a subscription | 1. Send welcome email with booking link |
|               |                   | 2. Add "Active Member" tag              |

***

## Step-by-Step Instructions

<Steps>
  <Step title="Open the Automation Builder">
    Go to **Tools → Automations** and click **Create Automation**.

    The builder is one long page with a section for each part of the automation—**Details**, **Triggers**, **Data Sources**, **Conditions**, **Actions**, **Logs**, and **Settings**—and a side menu that jumps between them. Nothing is saved until you click **Create** in the header. If a new automation opens with anything already filled in, replace or remove it as you follow the steps below.

    <Frame>
      <img src="https://mintcdn.com/coachiq/-uT2neGZ0HTX27CL/images/automation-builder-sections.png?fit=max&auto=format&n=-uT2neGZ0HTX27CL&q=85&s=648c9049f02d67aa51a18ba971aec5f0" alt="The automation builder: side menu, Details, Triggers and Data Sources sections" width="2880" height="1800" data-path="images/automation-builder-sections.png" />
    </Frame>
  </Step>

  <Step title="Name It">
    In **Details**, enter a label like **New Member Welcome**. This is the name you'll see in the Automations list and in Execution Logs, so make it specific.
  </Step>

  <Step title="Choose Your Trigger">
    In **Triggers**, choose **Purchase Made**.

    This trigger fires whenever someone buys any [product](/payments/product-overview)—memberships, credit packs, camps, or one-time sessions. The buyer becomes the **user** that every later section refers to.

    <Frame>
      <img src="https://mintcdn.com/coachiq/t0r9cjm0Rx9xJoHY/images/trigger-options.png?fit=max&auto=format&n=t0r9cjm0Rx9xJoHY&q=85&s=e2f37d68fa3aa9ca22c2f082c0130fef" alt="CoachIQ automation trigger selection menu showing available triggers" width="1498" height="1148" data-path="images/trigger-options.png" />
    </Frame>
  </Step>

  <Step title="Add a Condition">
    We only want this automation to run for new members, not every purchase. Let's add a filter.

    In **Conditions**, click **Add Condition** to create your first rule group, then choose **Is a subscription** in the **Field** dropdown.

    Now this automation will only fire when someone purchases a subscription product—not one-time buys like camps or drop-in sessions.

    <Frame>
      <img src="https://mintcdn.com/coachiq/pVtDE0YddygGyYMh/images/condition-options.png?fit=max&auto=format&n=pVtDE0YddygGyYMh&q=85&s=b919671f0877c2f70c07f1a80a9f3fe3" alt="Adding the subscription condition" width="1510" height="1392" data-path="images/condition-options.png" />
    </Frame>

    <Tip>
      Conditions are optional, but they help you target the right people. Rules sit inside **And**/**Or** groups, so you can add several and choose whether all of them or any one of them must be true. Skip **Data Sources** for now—this automation doesn't need extra information.
    </Tip>
  </Step>

  <Step title="Add Your First Action — Send Email">
    In **Actions**, click **Add Action** and select **Send an Email**.

    Fill in the fields:

    | Field           | What to Enter                                    |
    | --------------- | ------------------------------------------------ |
    | **Target User** | User from trigger (the default)                  |
    | **Subject**     | `Welcome to the team, {{field.user.firstName}}!` |
    | **Message**     | See template below                               |

    Here's a welcome email you can copy and paste. Replace the bracketed line with the booking link for your main training session:

    ```
    Hey {{field.user.firstName}},

    You're officially part of the team! 🎉

    Here's how to get started: book your first session here: [paste your session's booking link]
    If you have any questions, just reply to this email—I'm here to help.

    See you soon,
    [Your Name]
    ```

    <Note>
      **Dynamic fields** like `{{field.user.firstName}}` automatically insert each member's actual name. Type `@` in the subject or message to insert one from a list instead of typing it. Your email stays personal without extra work.
    </Note>

    <Frame>
      <img src="https://mintcdn.com/coachiq/JXXmA_QvX_9KCgui/images/automation-actions.png?fit=max&auto=format&n=JXXmA_QvX_9KCgui&q=85&s=d0c9a9f122a24db992d5315ecef566be" alt="Configuring the send email action" width="1566" height="1858" data-path="images/automation-actions.png" />
    </Frame>
  </Step>

  <Step title="Add a Second Action — Add Tag">
    Let's also tag new members so you can target them with future automations.

    Click **Add Action** and select **Add a Tag to a User**.

    | Field           | What to Enter                                |
    | --------------- | -------------------------------------------- |
    | **Target User** | User from trigger                            |
    | **Tag**         | Select "Active Member" (or create a new tag) |

    Now every new subscriber automatically gets tagged, making it easy to send announcements or check engagement later.

    <Frame>
      <img src="https://mintcdn.com/coachiq/t7IbJ7SAz9G5Mnrk/images/add-tag-action.png?fit=max&auto=format&n=t7IbJ7SAz9G5Mnrk&q=85&s=1b9b51c2dfea976637f93a60aa83c269" alt="Adding a tag to the user" width="1560" height="958" data-path="images/add-tag-action.png" />
    </Frame>
  </Step>

  <Step title="Create, Test, Then Enable">
    Click **Create** in the header to save the automation. It is saved with **Enabled** off, so nothing runs yet.

    Work through the [test checklist](#test-before-you-enable) below, then open **Settings** and switch **Enabled** on.

    <Check>
      **That's it!** Your automation is now live. The next person who purchases a subscription will automatically receive your welcome email and get tagged as an Active Member.
    </Check>
  </Step>
</Steps>

<Note>
  Some screenshots on this page show an earlier layout of the builder with a blank canvas and a **Select Trigger** button. The steps above describe the current builder; the concepts are the same.
</Note>

***

## Test Before You Enable

Message, SMS, booking, credit, and purchase actions have real effects the moment they run, so check your work before switching an automation on:

1. **Build with Enabled off.** A new automation starts disabled; leave it that way while you edit.
2. **Use a test account.** Make sure the email will land somewhere you can read it—your own test profile, not a real member.
3. **Click Test Run** in the header and read the filled-in email. Test Run really sends, so it will email whoever it targets.
4. **Check Execution Logs** to see which conditions passed and what each action returned.
5. **Then switch Enabled on** in **Settings**, deliberately, once you're happy.

***

## Verify It's Working

A few ways to confirm your automation is running:

* **Check Execution Logs**: Open the automation and scroll to **Logs** for a record of every run, who it was for, and what each action did
* **Make a test purchase**: Use a test account to subscribe and see if the email arrives
* **Wait for your next signup**: You'll see it appear in the logs

***

## What You Just Learned

You now understand the building blocks of every automation:

* **Triggers** start automations when something happens (a purchase, booking, [form submission](/tools/forms/overview), or a schedule)
* **Conditions** filter who it applies to (only subscriptions, only first-time buyers)
* **Actions** are what CoachIQ does automatically (send [messages](/inbox/inbox-overview), add tags, manage credits)
* **Data Sources** (optional) fetch extra information, like a credit balance, for conditions and messages to use

Every automation in CoachIQ—no matter how complex—uses this same pattern.

***

## What's Next?

<CardGroup cols={2}>
  <Card title="Automation Playbook" icon="book" href="/tools/automations/automation-playbook">
    Browse ready-to-use automations for trial conversions, member retention, credit reminders, and more.
  </Card>

  <Card title="Scheduled Automations" icon="calendar" href="/tools/automations/scheduled-automations">
    Learn how to run automations on a schedule—like weekly check-ins for inactive members or credit expiration alerts.
  </Card>
</CardGroup>

## Related articles

<CardGroup cols={2}>
  <Card title="Builder Reference" icon="wrench" href="/tools/automations/builder-reference">
    What each section of the builder does, including Test Run and Execution Logs
  </Card>

  <Card title="Triggers & Actions Reference" icon="list" href="/tools/automations/triggers-actions-reference">
    Every trigger, condition, data source, action, and dynamic field
  </Card>

  <Card title="Forms Overview" icon="file-lines" href="/tools/forms/overview">
    Build forms that trigger automations on submission
  </Card>

  <Card title="Creating Your First Scheduler" icon="calendar" href="/scheduling/creating-your-first-scheduler">
    Set up the sessions your automations will reference
  </Card>

  <Card title="Inbox Overview" icon="inbox" href="/inbox/inbox-overview">
    Where automated emails and in-app messages are delivered
  </Card>

  <Card title="Tags and Filters" icon="users" href="/people/tags-filters">
    Organize members with tags that automations can add or remove
  </Card>
</CardGroup>
