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

# Automations

> Rules that trigger follow-up emails, activities, and CRM updates automatically after calls.

## What are Automations?

Automations are if-then rules that run after a call ends. Instead of manually moving a deal, creating a follow-up task, or sending an email, you define the rule once and Avero executes it every time the condition is met.

**Example:** If a call outcome is "No answer" → create a follow-up call activity in Pipedrive for tomorrow at 10:00.

## Creating a rule

1. Go to **Settings → Automations**.
2. Click **New rule**.
3. Choose a **trigger** (when the rule fires).
4. Add one or more **actions** (what happens).
5. Save and toggle the rule on.

## Triggers

| Trigger | Description |
| - | - |
| **Call outcome: Connected** | Fires after a completed conversation |
| **Call outcome: No answer** | Fires when the contact didn't pick up |
| **Call outcome: Left voicemail** | Fires after a voicemail was left |
| **Qualification result** | Fires when ICP fit matches a threshold (e.g. ≥ 3/5) |
| **Deal stage change** | Fires when Pipedrive moves the deal to a specific stage |

## Actions

| Action | What it does |
| - | - |
| **Send email** | Sends from your connected email account using a template |
| **Create activity** | Adds a call, meeting, or task in Pipedrive |
| **Update deal field** | Writes a value to any Pipedrive deal field |
| **Move deal stage** | Moves the deal to a specified pipeline stage |
| **Add deal label** | Tags the deal for filtering |
| **Enroll in sequence** | Starts a multi-step email sequence |

## Email sequences

A sequence is an ordered list of emails sent with a set delay between each step. Common use cases:

* 3-touch no-answer nurture (Day 0, Day 2, Day 5)
* Post-demo follow-up series
* Re-engagement for stalled deals

Each step uses a template. Templates support variables pulled from Pipedrive:
`{{contact.first_name}}`, `{{deal.name}}`, `{{rep.name}}`, `{{deal.pipeline_stage}}`

<Tip>
  Sequences pause automatically if the contact replies or the deal moves to a different stage.
</Tip>

## Conditions

Rules can include conditions to narrow when they fire:

* **Pipeline** — only run for deals in a specific pipeline
* **Deal value** — only run above or below a threshold
* **Deal stage** — only run if the deal is in a specific stage
* **Custom field** — match any Pipedrive custom field value

## Rule execution order

If multiple rules match the same event, they run in the order they're listed. Drag rules to reorder them.

## Audit log

Every automation execution is logged — you can see which rule fired, what action was taken, and whether it succeeded. Go to **Automations → History** to review.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.