> 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

### 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 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/retool-integration/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.