Connect workflows to Kibana Universal Alerting
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability We plan to add this functionality in a future Elastic Stack update. Subject to changes. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Planned
Planned
In Kibana Universal Alerting, workflows define what happens in response to an alert, such as sending a message, calling a webhook, or opening a ticket.
Kibana Universal Alerting starts workflows in two ways: through action policies and through alert lifecycle triggers. Both require an alert.
Kibana evaluates action policies against alerts on a continuous schedule. When an alert passes a policy's eligibility, scope, and frequency gates, Kibana invokes the policy's workflow. For the step-by-step evaluation sequence, refer to How the dispatcher evaluates action policies.
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability We plan to add this functionality in a future Elastic Stack update. Subject to changes. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Preview
Preview
Stack
Planned
Planned
Lifecycle triggers are event-driven triggers that start a workflow immediately when a user resolves, assigns, acknowledges, or snoozes an alert, with no scheduling or gating. Each action emits a named trigger event, such as alerting.actions.alertAssigned.
Lifecycle triggers don't fire on automatic status changes, such as when an alert becomes active or recovers based on rule evaluations. To respond to those changes, use an action policy. For the full list of trigger IDs, refer to Alert lifecycle triggers.
To use workflows, your role must have the appropriate privileges and your subscription must include workflows. Refer to the subscription page for Elastic Cloud and Elastic Stack/self-managed for a breakdown of available features by tier.
You can use both at the same time. Each runs its own workflows without conflict.
| Action policies | Lifecycle triggers | |
|---|---|---|
| How they run | Evaluate alerts on a continuous schedule | React immediately to a specific event |
| Frequency control | Apply eligibility, scope, and frequency gates | Fire exactly once per event, no gates to configure |
| Best for | Recurring notifications and escalation logic that runs as long as a problem persists | One-shot automations, such as opening a ticket when a user assigns an alert or posting a message when a user resolves it |
- Create and configure an action policy: Start routing alerts to workflows.
- About action policies: Understand how action policies gate alerts before invoking a workflow.