Integration · Data orchestration
Dagster + OrchestrAI
Catalog exported 2026-09-02 · Dagster website
Launch Dagster jobs, materialize assets, and inspect runs from chat, with termination gated by confirmation.
OrchestrAI exposes 10 Dagster operations: 6 are low-risk (read-only or low-impact), and 4 create or modify resources and run only after you confirm the plan. 2 of them also carry a step-level approval gate.
What teams use it for
Data engineers use OrchestrAI with Dagster to find which assets went stale, materialize them, and watch the run to completion. Launching a job and materializing assets are medium risk and run once you ask. Terminating a running job waits for confirmation, and deleting a run record is rated high because it changes history. There is no operation for schedules, sensors, or code locations, so manage those in the Dagster UI or in code.
Every Dagster operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Get Asset Materialization |
Get asset materialization info | Low risk | No |
Get Dagster Asset |
Get asset details | Low risk | No |
Get Dagster Run |
Get run details | Low risk | No |
List Dagster Assets |
List all asset definitions | Low risk | No |
List Dagster Jobs |
List all jobs | Low risk | No |
List Dagster Runs |
List job runs | Low risk | No |
Materialize Dagster Assets |
Materialize assets | Creates resources | No |
Run Dagster Job |
Launch a job run | Creates resources | No |
Terminate Dagster Run |
Terminate a running job | Creates resources | Yes |
Delete Dagster Run |
Delete run record | Modifies existing | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
What you connect
A Dagster credential (stored as dagster).
Connected-service tokens are envelope-encrypted with a per-record key wrapped by a cloud KMS.
Prompts that work
- Which Dagster assets in the marketing group have not materialized since yesterday?
- Materialize the customer_ltv and customer_segments assets now
- Terminate the run for daily_refresh that has been going for four hours
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Does OrchestrAI ask before materializing Dagster assets?
- Yes. Materializing assets and launching jobs are medium-risk operations, so the plan is shown and waits for your confirmation before anything runs. Terminating a run additionally carries a step-level approval gate.
- Can OrchestrAI delete Dagster run history?
- Yes, but deleting a run record is a high-risk operation that waits for explicit confirmation because it removes data from the run store.
- How does OrchestrAI authenticate to Dagster?
- You add a Dagster credential once in the connections screen. It is envelope-encrypted with a per-record key wrapped by a cloud KMS and is only decrypted inside the run that needs it.
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.