Automation Rules overview

automation rules let peach run repeatable work automatically the basic pattern is something happens peach checks whether the event matches a rule 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 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 #