dbt Cloud jobs
TaskBeacon reads the latest runs of each watched dbt Cloud job: a successful run is OK with its duration, an errored or cancelled run is Failed with dbt's status message, and a run in progress shows as Running (Late when it takes much longer than usual).
1. A read-only service token
- In dbt, Account settings → Service Tokens → + Create service token.
- Give it the narrowest permission set your plan offers: Job Viewer (Enterprise and Enterprise+) or Read-only (Enterprise, Enterprise+ and the legacy Team plan). On the Developer and Starter plans service tokens only get the Semantic Layer permission set, so they can't read job runs. Limit it to the projects you want watched.
- Copy the token (it is shown only once).
Note the Access URL from Account settings (e.g. ab123.us1.dbt.com) and the account ID (the number after /accounts/ in dbt's address). If your account limits API access by IP address, add TaskBeacon's server address to the allowlist (write to us for it).
2. Connect in TaskBeacon
Jobs → ▾ → Add integration… → dbt Cloud, paste the token, access URL and account ID (optionally only some job IDs), then Choose what to watch. Set each job's schedule in TaskBeacon (Edit) like the dbt job's, so a run that didn't start shows as Missed.
dbt allows plenty of API requests (5,000 a minute per account in 2026); if it ever answers "too many requests", we wait at least five minutes, dbt's cooldown.
Not yet tested on a real installation — tell us how it went (support@taskbeacon.io).
Use cases: dbt Cloud job failure alerts, and runs that never started. More questions: FAQ.