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

# Automations

> Scheduled rules that watch your pipeline and act when something matches.

An automation runs on a schedule, checks your pipeline against a filter you define, and takes an action when deals match.

Where [Signals](/signals) extract patterns *from* your context, automations watch the *state* of your pipeline and do something about it.

You can build automations in the Tempo web app — click **Automations** in the left sidebar — or over MCP from a connected AI platform. The **Automations** page has two tabs: **Automations** for the rules themselves, and **Run History** for past runs.

## Review run history

Open **Run History** to check whether an automation ran and what it found. The table shows the **Automation**, **Run Date**, number of **Opportunities**, and **Status** for each run.

Select a row to open the run details. Use the opportunity count to distinguish a successful run with no matches from a run that processed matching deals.

## What you'd use one for

* Post to Slack or email every Monday with deals closing this quarter that have not moved a stage
* Create a private Google Doc after each weekly pipeline review
* Flag opportunities over a threshold amount with no activity in two weeks
* Alert a channel when a deal in late stage has a close date in the past
* Remind a team about deals missing a champion or economic buyer

## How an automation works

Three parts:

<Steps>
  <Step title="A schedule">
    When the automation runs — a cron expression or a recurrence rule, in a timezone you choose.
  </Step>

  <Step title="A filter">
    Which deals it cares about. Built from opportunity, account, and contact fields with comparison operators, and combinable with and / or / not.
  </Step>

  <Step title="One or more actions">
    What happens when deals match. An automation can send a Slack message or email, or create a Google Doc, using literal text or a rendered [Canvas](/canvas) template.
  </Step>
</Steps>

## Scope

| Scope        | Visible to        | Use for                                   |
| ------------ | ----------------- | ----------------------------------------- |
| **Personal** | Just you          | Your own pipeline hygiene and reminders   |
| **Team**     | Your organization | Shared pipeline reviews, team-wide alerts |

## Safety model

Automations are built to be hard to fire accidentally:

* New automations are always created **disabled**. Nothing runs until you explicitly enable one.
* **Editing configuration disables the automation again.** A half-edited automation cannot run.
* Enabling **validates dependencies** — if the Slack channel is not connected, or the automation lacks execution authority, enabling fails with a specific blocker.

## Where to go next

<CardGroup cols={2}>
  <Card title="Build your first automation" icon="play" href="/automations/quickstart">
    A stalled-deal Slack alert, end to end.
  </Card>

  <Card title="Filter reference" icon="filter" href="/automations/reference">
    Every field, operator, and action available.
  </Card>
</CardGroup>