Approval-gated dbt Cloud job trigger workflow. It reads the selected job for context, then enqueues exactly one run using that job's configured defaults and an explicit cause. It does not create or update jobs, override steps by default, retry/rerun failed runs, cancel runs, mutate projects/environments, or call arbitrary dbt API routes.

How it works 3 steps

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

Process (3 steps)

■ job ?

■ triggered_run ?

■ card to_summary

Format results as a summary card

Settings 4 configurable

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

cause setting = Triggered from Recued after user approval

job id setting = 0

dbt cloud setting =

account id setting = 0