Notifications and actions for the experimental alerting system
Rules in the experimental alerting system don't send notifications directly. Instead, they produce alert episodes, and you use workflows and action policies to decide what happens next.
- Workflows are the delivery layer. They define what happens when the system decides to act, such as sending a message, calling a webhook, or triggering an automation.
- Action policies are the gating layer. They evaluate active alert episodes on a continuous schedule and invoke workflows based on match conditions, grouping, and frequency settings.
To send notifications or run actions from an alerting v2 rule:
- Build a workflow that defines the action to take.
- Create an action policy that routes alert episodes to that workflow.
Tip
If you need an action to fire exactly once in response to a specific alert episode state change (such as opening a ticket when an episode is assigned) use an alert episode lifecycle trigger instead of an action policy. Refer to Connect workflows for a comparison of both approaches.
- Connect workflows - How action policies and lifecycle triggers invoke workflows at runtime.
- About action policies - How action policies evaluate and gate alert episodes.
- Create an action policy - Configure policy type, match conditions, grouping, frequency, and destinations.
- Action policy reference - Available match condition fields, grouping modes, and frequency options.
- Manage action policies - Enable, disable, snooze, edit, or delete policies.
- Reduce notification noise - Suppress alerts using acknowledgment, snooze, and maintenance windows.