---
title: Automation Rules overview
slug: automation-rules-overview
docTags: 
createdAt: 2026-09-16T08:57:52.290Z
---

Automation Rules let Peach run repeatable work automatically.

The basic pattern is:

1. Something happens.
2. Peach checks whether the event matches a rule.
3. Peach runs the rule's action.

Use Automation Rules for everyday operational work such as assigning conversations, sending follow-up messages, handing a chat to an AI agent, sending templates, or reacting to an API event from another system.

## Where to find automations

You will usually work with automations in one of two places.

| Area                       | Use it for                                                                                            |
| -------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Automation Rules**       | General rules across conversations, integrations, APIs, templates, AI handoffs, and multi-step flows. |
| **Pipeline → Automations** | Pipeline-specific automation setup.                                                                   |

Start in **[Automation Rules](https://app.trypeach.io/wa/playbooks)** when the automation is about conversations, templates, AI handoff, API payloads, or a multi-step flow.

Start in **Pipeline → Automations** only when the automation is pipeline-specific. See [Pipeline automations](#).

## Common examples

- Assign inbound conversations to an agent or team.
- Send a confirmation message after a specific event.
- Hand a conversation to an AI agent.
- Trigger a rule from a custom API payload.
- Build a multi-step flow with waits, branches, and follow-up messages.

## How to think about a rule

Each rule has three main parts.

| Part           | Meaning                                                                                             |
| -------------- | --------------------------------------------------------------------------------------------------- |
| **Trigger**    | The event that starts the rule, such as a message, template status, integration event, or API call. |
| **Conditions** | Optional filters that narrow when the trigger should count.                                         |
| **Action**     | What Peach does when the rule matches.                                                              |

For example:

:::BlockQuote
When a customer sends a message, assign the conversation to the support team.
:::

In this rule, the incoming message is the trigger, any message filters are conditions, and the assignment is the action.

## Related guides

- [Create an Automation Rule](#)
- [Automation actions](#)
- [Triggers and conditions](#)
- [Pipeline automations](#)
- [Advanced and visual flows](#)
- [Custom API and payload mapping](#)
- [Manage automations via MCP](docId\:IS2W33m5-b6n6v-Xu2n3g) 
- [Manage, test, and troubleshoot automations](#)