Previous
Triggers, conditions, and actions
Last Updated
>
A closer look at every building block, and how to combine them in one rule.
This guide covers each building block in more detail so you can build exactly the workflow you need.
Triggers
A pull request is opened or merged.
A deploy succeeds or fails.
A chat message matches a keyword.
A schedule, like every weekday at 9:00.
A webhook is received from your own systems.
Conditions
Conditions limit when an automation runs. Filter by repository, branch, environment, label, or message content, and combine several conditions with AND or OR.
Actions
Send a chat message.
Create or update a ticket.
Call an API or send a webhook.
Ask AI Assist to summarize an event.
Run another automation.
Putting it together
When a deploy to production fails, and the service is marked critical, create an incident and notify the on-call channel.
Tip: more specific conditions mean fewer surprises. If an automation runs too often, add a condition.
