Browse your dbt Cloud account from Raycast: models, sources, lineage, jobs, runs, projects, and environments.
| Command | Description |
|---|---|
| Quick Search | Search projects, jobs, environments, and runs in one place |
| Show Projects | Browse projects with their repository and connection details |
| Show Environments | Browse environments and their jobs, models, and sources |
| Show Jobs | Browse jobs by project, view their runs and performance, and trigger them |
| Show Job Runs | Show recent job runs with status filtering, durations, and run details |
| Trigger Job | Trigger a job run, with confirmation |
| Browse Models (Catalog) | Browse models with their columns, tests, lineage, and compiled SQL |
| Browse Sources | Browse sources with freshness status and downstream models |
| Explore Lineage | Explore upstream and downstream lineage, with an interactive diagram |
| Show Job Performance | Each job's success rate, run counts, and build durations over 7–30 days |
| Show Model Performance | The slowest models, with their execution time and status across runs |
Every project, environment, job, run, model, and source view has a Go To section that moves up and down the dbt hierarchy without leaving Raycast: from a job up to its environment and project or down to its runs and performance, and from a model to its last run, last job, lineage, and performance. The matching dbt Cloud page is always one action away under Open in dbt Cloud.
Shortcuts follow one scheme across every command: the modifier says where the action goes, and the letter says what it acts on.
| Modifier | Does | Letters |
|---|---|---|
| ⌘⌥ | Go to / view inside Raycast | P project · E environment · J job · R runs · M models · S sources · L lineage · D details · G performance |
| ⌥⇧ | Open the dbt Cloud page | P project · E environment · J job · R run · L lineage · D docs · S settings |
| ⌘⇧ | Copy | C ID · . name · , path or URL |
Other actions: ⌘⇧T trigger a job, ⌘⌥X cancel a run, ⌘D open the lineage diagram, ⌘⌥C expand upstream lineage into CTEs, ⌘⇧L copy a SELECT of all columns, ⌥⇧B open BigQuery (BigQuery projects only), ⌘1–3 change the job performance window.
ab123.us1.dbt.com, ab123.eu1.dbt.com, or ab123.au1.dbt.com, pick the matching [w/ Account Prefix] option:
the catalog and lineage commands need your account's own Discovery API host.ab123)The extension exposes tools to Raycast AI, so you can ask things like:
@dbtcloud find models related to orders@dbtcloud what are the upstream dependencies of fact_revenue?@dbtcloud trigger the nightly jobTriggering a job always asks for confirmation first.
Catalog, source, and lineage data comes from the dbt Cloud Discovery API; jobs, runs, and environments come from the Administrative API. Browse Models and the AI tools read each project's production environment, falling back to staging, unless you pick an environment.