> For the complete documentation index, see [llms.txt](https://docs.smaq.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smaq.io/documentation/get-started/tutorials/run-your-first-automation.md).

# Run your first automation

Automations are scheduled (or on-demand) jobs that monitor your accounts and email you the findings. The simplest and most-used one is the **Metrics Alert.**

### Prerequisites

* A project with at least one of: Google Ads, Meta Ads, or GA4 connected.
* Editor or Owner role on the project.

***

### Step 1 — Open the Automations page

In the side menu, click **Automations**. You'll see a list of any existing automations (a Daily Brief may already be configured if you signed up via [pre-signup audit](/documentation/get-started/quick-start/pre-signup-audit.md)).

Click **New automation**.

<figure><img src="/files/XA4UfnJEYkeHZoqGtkHM" alt=""><figcaption></figcaption></figure>

### Step 2 — Pick the type

<figure><img src="/files/qtsjfMpbYCjOmj0VtLbn" alt=""><figcaption></figcaption></figure>

Pick Metrics Alert from the Type dropdown.

The form re-renders to show the Metrics Alert configuration: which metric to monitor, and the threshold.

<figure><img src="/files/98hP4KBmtzkweGGL17pe" alt=""><figcaption></figcaption></figure>

### Step 3 — Set the schedule

* **Frequency**: Daily (you can also pick Weekly or Monthly).
* **Time**: 8:00 AM (or whenever you want the email).
* **Timezone**: Pick yours.

> **\[Screenshot needed]** Schedule section of the form showing Daily, 8:00 AM, and a timezone selected.

### Step 4 — Set recipients

Type each email address into the **Recipients** field and press **Enter**. Add as many as you need.

### Step 5 — Save and run

1. Click **Save** at the bottom of the form.
2. You'll land back on the Automations list with your new automation visible.
3. Click **Run** on the automation card to generate it immediately (a useful check that everything works before tomorrow morning).

> **\[Screen video needed]** Clicking Run on a freshly-saved Daily Brief, watching the status change to "Running," then "Completed," then opening the snapshot. \~30 seconds.

### Step 7 — Check the result

Click the automation in the list to open it. You'll see:

* **Logs** tab — every run with status and timestamp.
* **Snapshots** tab — the email content from each run, viewable in the app even if the email got lost in spam.

Open the latest snapshot to read the brief.

### Step 8 — Tune the cadence

If daily is too noisy:

* Switch the frequency to **Weekly** (most teams find weekly is the sweet spot).
* Or create a **Weekly Brief** automation in addition to the Daily Brief — different audiences, different schedules.

### What's next

* [Dashboard Summary](/documentation/features/automations/dashboard-summary.md) — schedule recurring summaries of a specific dashboard.
* [Metrics Alert](/documentation/features/automations/metrics-alert.md) — get pinged when a metric crosses a threshold.
* [Automation reference](/documentation/features/automations/reference.md) — see all 28 automation types and what each does.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.smaq.io/documentation/get-started/tutorials/run-your-first-automation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
