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

# Automations

> Triggers that run your workflows on their own.

Automations are tasks Quaso runs without you in the loop. Describe the workflow once in chat, say when it should fire, and Quaso executes it in the background: browsing sites, processing files, and acting on your connected apps.

## Triggers

| Trigger                  | Example                                                                                                       |
| ------------------------ | ------------------------------------------------------------------------------------------------------------- |
| **Schedule**             | "Send me a daily briefing every morning at 9am."                                                              |
| **App events**           | Gmail (new mail, label applied), Google Calendar, Google Drive, Notion, HubSpot, GitHub (PRs, issues, pushes) |
| **Webhooks**             | "When Stripe sends a payment webhook, log the line item in my accounting sheet."                              |
| **RSS feeds**            | "Watch this feed and email me a weekly digest."                                                               |
| **Email & text replies** | Talk to your agents on the go; replies land back in the automation.                                           |

One automation can hold several triggers. An inbox assistant might run a daily briefing, draft replies on new mail, and star important messages, all from the same definition.

## Monitors and alerts

A common pattern: watch something and get notified when it changes.

* Price changes on a competitor's pricing page
* New job postings matching a filter
* A dashboard metric crossing a threshold

Quaso checks on your schedule and pings you in Slack or by email only when there is something to report.

## Runs and visibility

Every run produces a full transcript: what Quaso browsed, what it extracted, and what actions it took. Open any run to inspect it, or reply to refine the automation's behavior for next time.