---
title: Triggers and conditions
slug: triggers-and-conditions
docTags: 
createdAt: 2026-09-16T08:57:52.320Z
---

Triggers decide when an Automation Rule should run.

Conditions narrow a trigger so the rule only runs for the events you care about.

![](https://api.archbee.com/api/optimize/LSvaQ8v7MiAYpp8V288yP/c087Q1IaWrwa8UjzEm8oW_automation-trigger-picker.jpg)

## Peach events

Peach events come from activity inside Peach, such as conversations, messages, templates, lists, and flows.

Use Peach events when the automation should react to something Peach already tracks.

## Integration events

Connected integrations can expose their own trigger events.

Use these when an external system should start a Peach automation, but the integration already has a registered event source in Peach.

## Custom Developer API

The full automation editor supports two custom API styles.

| Style                    | Use it when                                            |
| ------------------------ | ------------------------------------------------------ |
| **Automation endpoint**  | The payload is meant for one specific automation rule. |
| **Topic-mapped payload** | Multiple rules may listen to a shared event topic.     |

The direct automation endpoint is generated after the rule is saved.

Topic-mapped payloads are posted to the general events endpoint and must include a topic value that matches the rule's topic condition.

## Condition variables

Some triggers ask for condition variables. These are the values Peach uses to decide whether the incoming event matches.

For example:

- A template-message trigger can filter by template or message status.
- A custom topic trigger can filter by topic name.

Leave optional filters blank when the rule should match any value for that field.

## Payload mappings

Payload mappings tell Peach where to find important data inside an event payload.

Common mappings include:

- Recipient name
- Recipient phone number
- Recipient email
- Template variables
- Deduplication keys

Mappings are especially important for custom API automations and template-sending automations.

## Advanced triggers

Use advanced triggers when a rule needs multiple triggers, exit triggers, or custom data mappings beyond the simple builder.

Advanced triggers are managed from the rule's trigger screen or visual editor context.

Pipeline-specific triggers such as item enrolled, stage changed, completed, or dropped off are covered in [Pipeline automations](#).