Use-cases
Users
Industries
Hi! I'm your Kestra AI assistant.Ask me anything about workflows.
EXAMPLE QUESTIONS
The first step is always the hardest. Search or browse to kick-start your next flow.
32 Blueprints
Open a GitHub issue automatically whenever a Kestra workflow fails or warns, so every incident becomes a tracked, labeled ticket.
Trigger CI/CD from GitHub pull request webhooks and post automated comments back, with local JSON testing built in.
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.
Back up every Kestra namespace, flow, file, and KV pair to GitLab on a schedule, with optional releases and merge requests.
Collect logs from every pod in a Kubernetes namespace within a time window, plus namespace events, in one run.
Provision one Amazon S3 bucket per team and register each as a governed AWS_BUCKET asset in Kestra.
Provision AWS Batch on ECS Fargate with Terraform, then run parallel Python workloads on it from one Kestra flow.
Build a Docker image, run it, and provision files with Terraform in one declarative Kestra pipeline.
Deprovision an employee's LDAP entry on offboarding, snapshotting group membership for audit, relocating the account, and removing it from its groups.
Schedule the Aiven CLI to power services and databases off and on, cutting cloud costs without manual clicks.
Ping an HTTP endpoint on a schedule and fire a Slack alert the moment it stops returning 200.
Promote Kestra flows across tenants and environments automatically using the Kestra REST API on a schedule.
Automatically purge expired key-value entries from Kestra's internal KV store across namespaces on a daily schedule.
Run a Python script inside a Kubernetes pod with declarative CPU and memory limits, straight from a Kestra flow.
Send a SendGrid email alert automatically whenever any workflow in your namespace fails or warns.
Send a raw TCP payload to any host and port from Kestra, with a pre-flight port check and a fail-fast assertion.
Ship Kestra execution logs to Datadog every morning for centralized observability, monitoring, and alerting.
Forward Kestra execution logs to Splunk daily via HTTP Event Collector for centralized observability and alerting.
Roll out Argo CD Application updates across a single-tenant fleet in safe, sequential waves gated on real sync and health status.
Pull flows and namespace files from a Git repository into Kestra every hour for GitOps-driven deployments.
GitOps restore that pulls Kestra flows, namespace files, and KV pairs straight from a GitLab repository.
Automatically open a PagerDuty incident whenever any Kestra workflow fails or hits a warning state.