> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-transformation-tools/readme-1/dbt/metadata-extracted.md).

# dbt Cloud Metadata Extracted

{% hint style="info" %}
dbt is a secondary integration that adds additional metadata on to your data warehouse or relational database tables. Before connecting dbt make sure to connect a data warehouse or relational database first. These include Snowflake, BigQuery, Postgres, Redshift, etc.
{% endhint %}

## What does Secoda extract from dbt Cloud?

* Models Metadata:
  * Description
  * URL
  * Compiled SQL
  * Updated Time
* Columns Metadata:
  * Description
  * Tags
  * Updated Time
* Tests:
  * Name
  * Description
  * URL
  * Tags
  * Status
  * Error
  * Compiled code
* Jobs:
  * Name
  * URL
  * Job Runs
    * Status
    * Start Time
    * End Time
* Metrics (Referred to as Dictionary terms in Secoda) on dbt v1.5 or less:
  * Name
  * Type
  * Dimensions
  * Time Grains
* Lineage:
  * dbt Jobs <-> external Tables
  * dbt Exposures <-> external Tables
* Groups (Groups are referred to as `USER_GROUPS` in Secoda)
* Contracts (dbt Contracts are referred to as `TEST` in Secoda)
* Exposures
  * Type: dashboard, notebook, analysis, ml, or application
  * Name
  * Description
  * Tags
  * Owner
  * URL
* Monitors
  * See [Monitors](/features/monitoring.md#monitors-as-code)on how to implement monitors in your model yml


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.secoda.co/integrations/data-transformation-tools/readme-1/dbt/metadata-extracted.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.