> 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.md).
# Retool
An overview of the Retool integration with Secoda
{% content-ref url="/pages/xBWopplo5Jv5DfU7a3bp" %}
[Retool Metadata Extracted](/integrations/data-visualization-tools/retool-integration/metadata-extracted.md)
{% endcontent-ref %}
## Getting Started with Session Cookies
There are two steps to get started using Retool with Secoda through session cookies:
1. Retrieve a Retool session cookie
2. Connect Retool to Secoda
### Retrieve Session Cookie
*Secoda uses a series of REST APIs that Retool uses for its platform, which requires a session cookie. To get a session cookie follow these steps:*
1. Login to your Retool workspace and open developer tools by right-clicking and selecting **Inspect**
.png)
2. Click on the **Network** tab and enter `url:.retool.com` in the filter head
%20\(1\).png)
3. Refresh the page and you should see some requests populate
4. Click on `user` network request, navigate to **Headers** tab, scroll down to the **Request Headers** section and copy the `cookie` header.
%20\(1\)%20\(1\)%20\(1\).png)
### Connect to Retool
*After retrieving the session cookie, you can connect Retool to Secoda by following these steps:*
1. In Secoda, head to the **Integrations** page and click **New integration**
2. Select **Retool**
3. Paste the cookie into the **Cookie** text input field
4. Click **Connect**
---
# 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.md?ask=&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.