480+ Blueprints, ready to build.

The first step is always the hardest. Search or browse to kick-start your next flow.

Incident & Ticketing Notification

12 Blueprints

Sort by:

Page on-call responders in QQ (Tencent Cloud IM) whenever any flow in a Kestra namespace ends in FAILED or WARNING.

Send a Zulip alert to a stream whenever any flow in a namespace fails, with retry and a bounded timeout.

Broadcast a LINE alert to your followers only when a flow breaches its duration SLA, using a MAX_DURATION SLA label.

Broadcast a LINE alert to your Official Account followers whenever any flow in a namespace fails.

Open a Jira incident ticket, alert your on-call team in Slack, generate a timeline report, and log every incident to PostgreSQL in one flow.

Automatically open a Zendesk incident ticket whenever any workflow in your namespace fails or warns.

Automatically open a high-priority HubSpot ticket whenever a Kestra workflow fails or finishes with a warning.

Automatically open a Jira issue whenever any Kestra workflow fails or hits a warning, so incidents get tracked the moment they happen.

Post a daily Kestra pipeline status digest with real 24h execution counts to a Tencent Cloud IM / QQ team channel.

Notify a QQ approver group that an approval is pending, pause for a human decision, then post the outcome or an expiry notice.

Send a Discord alert automatically whenever any production workflow in a Kestra namespace fails or finishes with a warning.

Broadcast an outcome-aware LINE update to your followers every time one business-critical Kestra flow reaches a terminal state.