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

# Automations

> Run actions automatically when records change, on a schedule, or when a payment is received

Helm automations watch your tables and act for you — update records, send emails and notifications, call webhooks, or hand work to an AI agent. Each automation pairs one trigger with up to 10 actions and can be switched on and off at any time.

## Triggers

| Trigger                              | Fires when                                                                                                             |
| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
| **When a record is created**         | A new record is added to the table                                                                                     |
| **When a record is updated**         | A record changes — optionally only when specific watched fields change                                                 |
| **When a record is deleted**         | A record is removed                                                                                                    |
| **When a record matches conditions** | A record starts matching the conditions you set                                                                        |
| **When a record enters a view**      | A record newly appears in a chosen view                                                                                |
| **At a scheduled time**              | On a schedule — presets for every hour, daily at 9:00, Mondays at 9:00, or a custom cron expression with your timezone |
| **When a payment is received**       | Your workspace receives a payment through [Sontairo Finance](/finance/overview) — from a payment link or a hosted site |

## Actions

Actions are grouped into Records, Notify, and Integrations:

| Action                | What it does                                                                           |
| --------------------- | -------------------------------------------------------------------------------------- |
| **Update record**     | Changes field values on the triggering record                                          |
| **Create record**     | Adds a record to any table in the base                                                 |
| **Delete record**     | Removes the triggering record                                                          |
| **Send notification** | Sends an in-app notification with a title and message                                  |
| **Send email**        | Sends an email (to, subject, body)                                                     |
| **Send webhook**      | POSTs the event as JSON to an HTTPS URL                                                |
| **Run AI agent**      | Runs a headless AI agent with your connected tools; the run lands in your chat history |

Text settings support tokens like `{{trigger.fieldName}}` that fill in values from the triggering record. Payment triggers expose tokens such as `{{trigger.amount}}`, `{{trigger.currency}}`, and `{{trigger.customerEmail}}`.

## Testing and run history

* **Test run** executes the automation against the table's most recent matching record so you can check the wiring before enabling it.
* New automations start **off**; flip the switch in the editor header when you're ready.
* The **Run history** drawer shows each run's status (success, failed, or skipped), what triggered it, how long it took, and a step-by-step log of every action.

<Info>
  Automations don't chain: an action that updates a record will not fire other automations, so loops can't happen. Scheduled automations process up to 50 records per run.
</Info>