Developer Tools · Integration
dbt Cloud
Add dbt Cloud to your product for your customers, and give your AI agents governed access to it.
Embed a dbt Cloud integration so your customers can work their own projects, jobs, runs, and environments from inside your product, with governed agent access to the same records. Run events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost. fastn handles per-customer authorisation and API upkeep, so onboarding another dbt Cloud account is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own dbt Cloud account so job and run state is visible inside your product.
Trigger a job run from your product when upstream data lands, instead of waiting for a schedule.
Read run status and logs so failures surface where your users already work.
React to a run completing or failing, with events replayable after downtime.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a failed run's logs and summarises what broke.
An agent triggers a job run within governed permissions, with the action audited.
An agent reacts to a failed run and opens the follow-up issue for the owning team.
Example prompt
Show the last five runs of this job and summarise why any of them failed.
Set up dbt Cloud in 4 steps
- 01Open the dbt Cloud connector from your fastn dashboard.
- 02Have each customer authenticate their own dbt Cloud account with least-privilege scopes.
- 03Map the projects, jobs, and environments your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the dbt Cloud integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a dbt Cloud integration without building it. Your customers connect their own dbt Cloud account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a dbt Cloud update is not your on-call problem.
- One integration serves your product and your agents. The same governed dbt Cloud connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Works well with
Snowflake
BigQuery
DatabricksOften used alongside
Tools the same teams tend to run next to dbt Cloud, across other categories.
Slack
Airtable
PostgreSQL
Anthropic Claudedbt Cloud integration FAQ
How do I add a dbt Cloud integration to my product?
Enable the dbt Cloud connector in your fastn dashboard, then let each customer authenticate their own dbt Cloud account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no dbt Cloud client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own dbt Cloud account?
Yes. Every connection is scoped to the individual customer, so each authorises their own dbt Cloud account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this dbt Cloud integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a failed run's logs and summarises what broke.
Who maintains the dbt Cloud integration?
fastn does. When dbt Cloud changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to dbt Cloud events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in dbt Cloud?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the dbt Cloud integration?
A common starting point: connect their own dbt Cloud account so job and run state is visible inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the dbt Cloud integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding dbt Cloud does not change your per-connector cost. You can start free with 3 connected accounts.
Add dbt Cloud to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.