Dbt CLI
Tasks that run dbt via the CLI for building, testing, and managing projects.
DBT
CertifiedIntegrate dbt data transformations into Kestra orchestration pipelines.
Provides dbt integrations for both CLI-driven projects and dbt Cloud jobs so you can orchestrate runs alongside other Kestra tasks. Supply your dbt profiles or Cloud API credentials to execute, monitor, and collect manifests and run results for downstream automation.
DBT
Certified
Integrate dbt data transformations into Kestra orchestration pipelines.
Provides dbt integrations for both CLI-driven projects and dbt Cloud jobs so you can orchestrate runs alongside other Kestra tasks. Supply your dbt profiles or Cloud API credentials to execute, monitor, and collect manifests and run results for downstream automation.
How to use the dbt plugin
The DbtCLI task runs any dbt command inside a configurable container and parses run results automatically.
Authentication
Authentication to your data warehouse lives in the profiles property, which accepts the full content of a profiles.yml file as an inline string. Use {{ secret('NAME') }} to inject credentials at runtime rather than hardcoding them. For a cleaner separation of configuration from flow logic, store profiles.yml as a namespace file and reference it with namespace file functions.
Common properties
All CLI tasks run in a container defined by containerImage. Use an image from ghcr.io/kestra-io/docker-dbt that matches your adapter — dbt-postgres, dbt-bigquery, dbt-snowflake, dbt-duckdb, and others are available. The taskRunner property defaults to Docker and can be overridden for other execution environments.
Tasks
DbtCLI is the primary task and runs any dbt CLI command. For state-based selection across runs, storeManifest and loadManifest persist manifest.json to and from the Kestra KV Store. Dedicated tasks for individual commands (Build, Run, Test, Seed, and others) are also available if you prefer a more explicit task structure.
For dbt Cloud, use TriggerRun — it starts a job and waits for completion by default without requiring a container. Use CheckStatus to poll a run that was triggered outside of Kestra.
