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

# Retool Metadata Extracted

List of all the metadata that Secoda pulls from Retool

### What does Secoda extract from Retool?

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

* Folders
  * Folder Name
  * Folder Updated At
  * Folder URL
* Global Widgets
  * Global Widget Name
  * Global Widget Description
  * Global Widget Last Updated At
  * Global Widget URL
  * Global Widget Folder
* Apps
  * App Name
  * App Description
  * App Updated At
  * App URL
* Queries
* Lineage
  * Retool Query <-> Retool App
  * Retool Query <-> Tables from other sources
    * Note: These lineage relationships will pass through the Query to the Apps that that Query connects to.

{% hint style="info" %}
To determine lineage from Retool, we parse the queries that we extract from Retool using the APIs.
{% 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/retool-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.