> 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-visualization-tools/metabase/metadata-extracted.md).

# Metabase Metadata Extracted

### What does Secoda extract from Metabase?

{% hint style="info" %}
NOTE: Preview of Metabase resources is available in Secoda if permissions are granted. [Interactive embedding ](https://www.metabase.com/docs/latest/embedding/interactive-embedding#enabling-interactive-embedding-in-metabase)will need to be enabled for Metabase Previews in Secoda to work.
{% endhint %}

* Collections
  * Collection Name
* Dashboard
  * Dashboard Name
  * Dashboard Description
  * Dashboard Owners
  * Dashboard Last Updated Timestamp
  * Dashboard URL
* Cards
  * Card Name
  * Card Description
  * Card URL
* Queries
* Lineage
  * Metabase Card <-> Metabase Dashboard
  * Metabase Query <-> Metabase Card
  * Metabase Query <-> Metabase Dashboard
  * Metabase Card <-> Tables from other sources

{% hint style="info" %}
To determine lineage from Metabase, we use the relationships and dependencies provided from the Metabase APIs as well as our own Query parser to determine lineage to sources outside of Metabase.
{% endhint %}


---

# 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-visualization-tools/metabase/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.