New to Kestra?
Use blueprints to kickstart your first workflows.
Failure notifications to Slack to monitor the health of production workflows
Get instant Slack alerts when any Kestra flow in a namespace fails or warns. One Flow trigger covers every workflow, with a link to the failed execution.
Categories
id: slack-failure-alert
namespace: company.monitoring
triggers:
- id: listen
type: io.kestra.plugin.core.trigger.Flow
dependsOn:
- when: "{{ trigger.namespace startsWith 'company.analytics' }}"
states:
- FAILED
- WARNING
tasks:
- id: send
type: io.kestra.plugin.slack.notifications.SlackExecution
url: "{{ secret('SLACK_WEBHOOK') }}"
executionId: "{{ trigger.executionId }}"
Catch failures the moment they happen instead of discovering broken pipelines hours later. This blueprint posts a Slack alert whenever any flow in the company.analytics namespace finishes in a FAILED or WARNING state, so on-call engineers and data teams get notified in the channel they already watch. The alert carries the executionId, giving everyone a direct link to the failed execution page for fast triage and root-cause analysis.
How it works
- A
io.kestra.plugin.core.trigger.Flowtrigger namedlistenwatches the execution state of other flows across the whole instance. - A single
dependsOnentry gates the trigger:states: [FAILED, WARNING]fires only on those outcomes, and thewhenexpression{{ trigger.namespace startsWith 'company.analytics' }}scopes it tocompany.analyticsand all of its child namespaces. - When a matching execution ends, the
sendtask (io.kestra.plugin.slack.notifications.SlackExecution) posts to Slack via an incoming webhookurl, passingexecutionIdso the message includes execution context and a link.
What you get
- Centralized failure alerting defined once, not copy-pasted into every flow.
- Coverage of an entire namespace tree, including new flows added later.
- A clickable path from the Slack message straight to the failed execution.
- Both hard failures and soft warnings surfaced in one place.
Who it's for
- Data and platform engineers running production pipelines.
- On-call and SRE teams that triage incidents from Slack.
- Analytics teams who need to know the instant a scheduled job breaks.
Why orchestrate this with Kestra
Slack itself has no awareness of your workflows, and most schedulers can only alert on the single job they ran. Kestra's event-driven Flow trigger reacts to the execution state of any flow in a namespace, so one declarative YAML definition replaces per-flow notification boilerplate. You also get retries, full execution lineage, and a searchable history, capabilities a plain webhook or a tool's built-in scheduler cannot provide on their own.
Prerequisites
- A Kestra instance with the Slack plugin available.
- A Slack incoming webhook URL for the target channel.
Secrets
SLACK_WEBHOOK: the Slack incoming webhook URL used by thesendtask.
Quick start
- Create a Slack incoming webhook and copy its URL.
- Store that URL as the
SLACK_WEBHOOKsecret in Kestra. - Adjust the
whenexpression's namespace prefix to your own. - Add the flow and let the trigger watch your executions.
- Force a test failure to confirm the alert lands in Slack.
How to extend
- Add or remove entries in the
stateslist (for example, alert only onFAILED). - Swap
SlackExecutionforSlackIncomingWebhookto send a fully custom message payload. - Extend the
whenexpression to filter by flow id or labels. - Route to multiple channels by adding additional notification tasks.
Links
- Plugin docs: https://kestra.io/plugins/plugin-slack
- Orchestrate Slack with Kestra: https://kestra.io/orchestration/slack
Tasks
Orchestrate with Kestra
Orchestrate Slack with KestraShare this Blueprint
Create a Blueprint
Go to the developer platformMore Business Blueprints
More Core Blueprints
