> 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

List of all the metadata that Secoda pulls from Metabase

### 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secoda.co/integrations/data-visualization-tools/metabase/metadata-extracted.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.