dbt Cloud (Edge)

Last updated on Nov 18, 2026

dbt Cloud is a platform for developing, testing, scheduling, and documenting the data transformations that you write in dbt. You organize your work in projects, run it in environments through jobs, and review the result of each run.

Hevo uses the dbt Cloud Administrative API to replicate the account details, projects, environments, repositories, connections, jobs, runs, run results, users, groups, permissions, and notifications of your dbt Cloud account to the Destination of your choice. To ingest data, you must provide Hevo with a service token and the access URL of your dbt Cloud account.


Supported Features

Feature Name Supported
Capture deletes Yes
History mode No
Custom data (user-configured tables & fields) No
Data blocking (skip objects and fields) Yes
Resync (objects and Pipelines) Yes
API configurable Yes

Handling of Deletes

Hevo captures the deletes of the dbt Cloud objects as follows:

Deletes Captured Objects
In each run, by comparing the data All objects except Run and its child objects.

Hevo ingests all the records of these objects in each run, and marks the records that are no longer returned by dbt Cloud as deleted by setting the value of the metadata column __hevo__marked_deleted to True. For example, a job that you delete in dbt Cloud is marked as deleted in the next run.
Not captured Run and its child objects. A run that is deleted in dbt Cloud remains in the Destination.

Source Considerations

  • Hevo ingests the data of the dbt Cloud account that the service token belongs to. A service token belongs to one account, so to replicate data from another dbt Cloud account, create a separate Pipeline with a service token from that account.

  • In each run, Hevo ingests the 100 most recent ingested runs again to update the runs that were still in progress. If more than 100 newer runs are created before a run finishes, for example, when a long-running job overlaps many short jobs, the status, duration, and results of that run are not updated in the Destination.

  • Some objects contain data only if your dbt Cloud plan includes the related feature:

    • Audit Log Event: The audit log, available on the Enterprise plans.

    • Webhook Subscription and Webhook Event: Webhooks, available on the Starter and Enterprise plans.

    • IP Restriction and IP Restriction CIDR: IP restrictions, available on the Enterprise+ plan.

    If your plan does not include a feature, Hevo creates the related tables, but they do not contain any data.

  • The Run Step, Run Artifact, Run Result, and Run Result Timing objects contain data only for the runs that dbt Cloud started. A run that is cancelled before it starts has no steps or artifacts. Similarly, a run that fails before dbt executes any model, test, or other node has no run results.

  • dbt Cloud allows 5,000 Administrative API requests per minute for each account. If the limit is exceeded, Hevo waits and retries the request. Read API rate limits.


Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Nov-16-2026 2.54 New document.

Tell us what went wrong