Read-only dbt Cloud workflow for reviewing one run and one documented run artifact such as run_results.json, manifest.json, or catalog.json. It does not trigger jobs, cancel runs, retry runs, mutate dbt Cloud resources, read service tokens or credentials, or call arbitrary dbt API routes.

How it works 8 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (8 steps)

■ run ?

■ artifact_names ?

■ artifact ?

■ steps default

Apply default

■ step_count count

Count items in steps

■ step_table to_table

Format results as a data table

■ summarize ?

■ card to_summary

Format results as a summary card

Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Summarize the dbt Cloud run and artifact. For run_results.json, call out failed, errored, skipped, or slow models/tests and likely owner follow-up. For manifest.json or catalog.json, summarize project shape and useful diagnostics. Do not invent models, failures, or timing data outside the artifact.

run id setting = 0

dbt cloud setting =

account id setting = 0

max length setting = 1000

artifact path setting = run_results.json