> 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/tableau-integration/metadata-extracted.md).

# Tableau Metadata Extracted

List of all the metadata that Secoda pulls from Tableau

### What does Secoda extract from Tableau?

{% hint style="info" %}
NOTE: Preview of Tableau resources is available in Secoda if permissions are granted.
{% endhint %}

* Published Datasources
  * Name
  * Description
  * Columns
  * Owners
* Embedded Datasource
  * Name
  * Columns
  * Owners
* Workbooks
  * Name
  * Description
  * Owners
  * URL
  * Updated At
  * Number of Views
* Dashboard
  * Name
  * Description
  * Owners
  * URL
  * Updated At
  * Number of Views
* Sheets
  * Name
  * URL
  * Owners
  * Number of Views
* Fields
  * Name
  * Description
  * Type
* Custom SQL Table (Custom SQL Tables are referred to as Queries in Secoda)
* Lineage
  * Tableau Datasources <-> Tables from other sources
  * Tableau Fields <-> Columns from other sources
  * Tableau Datasources <-> Tableau Workbooks
  * Tableau Workbooks <-> Tableau Sheets
  * Tableau Dashboards <-> Tableau Sheets
  * Tableau Workbooks <-> Tableau Dashboards

{% hint style="info" %}
To determine lineage from Tableau, we parse the queries that we extract from Tableau using the APIs along with the lineage returned by Tableau directly
{% 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/tableau-integration/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.
