> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your app to Retool

> Connect your app to Retool to manage organization users and groups, browse apps and workflows, and embed existing tools in your Lovable app.

[Retool](https://retool.com/) is a platform for building internal tools. The **Retool** connector lets your Lovable app manage a Retool organization and embed existing Retool apps. It's designed for team administration dashboards and portals that bring those tools together.

**Retool** is available as an [app + chat connector](https://docs.lovable.dev/integrations/app-connectors.md): one shared connection that works in [Chats](https://docs.lovable.dev/features/chats.md), in the project chat while you build, and in your published apps.

With **Retool**, your app can:

* List organization members, add them to groups, and create, deactivate, or delete them
* Manage groups and permissions
* Browse apps, folders, and workflows
* Create single-use URLs to [embed a Retool app](#embed-a-retool-app)

These changes apply to your whole Retool organization. Lovable makes only the change you ask for, and puts a confirmation step in your app before it deletes a member or changes access.

The connector does not run queries inside Retool apps or read data from their connected resources, the databases and APIs those apps pull from.

## Common use cases and example apps

These examples show what you can build with **Retool**, each with a prompt to start from.

| Example app | Example prompt | Description |
| :- | :- | :- |
| **Team directory** | *Use Retool and build an internal directory where my team can search the members of our Retool organization by name or email.* | **Find people in your Retool organization.** The app reads organization members and shows their details in a searchable list. |
| **Onboarding dashboard** | *Use Retool and build a form, open only to our Retool organization admins, that adds a teammate to our organization and a selected group, with a confirmation before saving.* | **Manage onboarding from one form.** The app adds the person and assigns the group a Retool admin selects. |
| **Access review dashboard** | *Use Retool and build a read-only dashboard where our Retool organization admins can review groups and their permissions before changing access.* | **Review who has access to your Retool tools.** The app displays groups and permissions for a Retool admin to check. |
| **Internal tool catalog** | *Use Retool and build a searchable catalog of the apps and workflows in our organization.* | **Browse your existing Retool tools.** The app lists apps and workflows without running them. |
| **Embedded tool portal** | *Use Retool and build a signed-in portal that embeds our published Retool app and gives each person access through the appropriate Retool permission group.* | **Use an existing tool inside your Lovable app.** The app creates an embed URL for the signed-in person, subject to [Retool's embedding requirements](#embed-a-retool-app). |

## How to connect Retool

Who can create **Retool** connections depends on your plan and workspace settings. **App + chat connectors** are available by default. On Business and Enterprise plans, [Who can create connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-create-connections-and-clients) starts at **Admins**.

Some Enterprise workspaces start at **No one**, which disables the connector. An admin or owner changes it in **Connectors → Admin settings → App + chat connectors**.

You can create multiple **Retool** connections using different access tokens, for example, to connect separate organizations or give projects different permissions.

When the connection is created, you can [link it to the projects](https://docs.lovable.dev/integrations/app-connectors.md#link-a-connection-to-a-project) where you want to use it. Anyone building in a project can ask Lovable in the project chat to link their project to it. Linking follows the connection's access rules.

### Prerequisites

Before connecting **Retool**, make sure you have:

* A Retool organization on the Business or Enterprise plan. The Retool API is not available on the Free and Team plans, so you cannot create an access token there. Business covers part of the API, and Enterprise covers all of it.
* An organization address that uses HTTPS and is reachable on the public internet, whether you are on Retool Cloud or host Retool yourself. Lovable calls your organization through the [connector gateway](https://docs.lovable.dev/integrations/app-connectors.md#gateway-based-connectors). If a firewall allows traffic only from specific addresses, allowlist the [gateway IP ranges](https://docs.lovable.dev/integrations/security.md#ip-allowlisting).
* A Retool API access token, as described in Step 1. Only organization admins can create one in Retool, so ask an admin if you are not one.
* Permission to **create connections** in your Lovable workspace (see [Who can create connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-create-connections-and-clients))

> [!NOTE]
>
> API calls through this connector use your Retool organization. Billing is handled directly by Retool, not Lovable. When you host Retool yourself, you pay for the host yourself.

Your access token carries scopes, the permissions it grants. They decide which of these operations your app can use. Check the [Retool API reference](https://docs.retool.com/api) for the ones you need.

### Step 1: Get a Retool access token

A Retool access token grants access to your organization. Choose the scopes your app needs, and no more.

**1. Open your Retool organization**

Sign in to your Retool organization as an organization admin.

**2. Create an access token**

Go to **Settings → Retool API** and click **Create new**. Enter a name and description that identify the connection, for example `Lovable integration`.

**3. Choose scopes**

Retool lists each scope with a **Read** and a **Write** option. Select **Read** on **Users** to list organization members, and **Write** only where your app changes something.

To use the embed example on this page, also select **Retool Embed** under **Apps**. Choose **Embed** instead for a classic app, one made in Retool's original app editor rather than its current one. Retool documents that scope with its embedding guides rather than its scope reference.

See [Retool's authentication and scope guide](https://docs.retool.com/org-users/guides/retool-api/authentication) for the other scopes.

**4. Copy the token**

Copy the token and store it securely. Retool displays it only once.

> [!WARNING]
>
> Your access token functions like a password. Keep it secure and never share it publicly. You need it in the next step.

### Step 2: Connect Retool to Lovable

Create the connection with your organization address and the token from Step 1.

**1. Open Retool in Connectors**

Open [Connectors](https://lovable.dev/dashboard?connectors) and select **Retool**. For the other places to open the catalog from, see [Where to find connectors](https://docs.lovable.dev/integrations/introduction#where-to-find-connectors).

**2. Add a connection**

Click **Connect** on the connector page. The form is split into collapsible sections, **Details**, **Configure connection**, and **Sharing**.

**3. Name the connection**

Under **Details**, Lovable fills in a name for the connection, which you can change. The name is only used inside Lovable to identify the connection.

**4. Configure the connection**

Under **Configure connection**, enter these required fields:

1. **Instance URL**: your Retool organization's HTTPS address, for example `https://your-org.retool.com`, or `https://retool.yourdomain.com` when you host Retool yourself. Lovable uses the address alone, so any path you paste with it is ignored. A port is kept, as in `https://retool.yourdomain.com:3000`.
2. **Access token**: paste the Retool API access token from Step 1.

**5. Choose who can use this connection**

Under **Sharing**, the connection is private to you by default and shows a **Private** label. To share it, click **Share with others**. Then add workspace members by email, or click **Invite entire workspace** to make the connection available to everyone in your Lovable workspace.

See [Who can use connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-use-connections-and-clients) for more information.

**6. Connect**

Click **Connect** at the bottom of the form. Lovable checks the token against the Retool API before saving the connection. The check confirms that the token works and that a Retool organization answered, not that the token carries every scope your app needs.

If Lovable reports that no Retool API answered at this address, the **Instance URL** points at something other than your Retool organization.

Lovable confirms that the connection is created.

When connected, anyone building in a project can ask Lovable in the project chat to link their project to Retool. Linking follows the connection's access rules. Your Lovable apps can then manage your organization and create embed URLs.

## Embed a Retool app

Your Lovable app can create a URL that signs a person into an embedded Retool app, so each person sees the app as themselves. The URL works once and then expires. Your app requests a new one each time someone opens the tool.

Embedding needs the embedding scope on your access token, from Step 1, and sign-in in your own Lovable app. Retool signs in the person your app identifies, so your app has to know who they are first. If your app has no login yet, start with [users and authentication](https://docs.lovable.dev/features/authentication).

Retool supports this flow only for apps published on Retool Cloud under a standard Retool domain, such as `your-org.retool.com`. When you host Retool yourself, or your organization uses a custom domain, you cannot use it.

Retool calls the tools you embed **apps** or **classic apps**, and the setup differs.

Prepare the app and its permission groups, the Retool groups that decide what an embedded person can see, with the guide for yours:

* [Retool apps](https://docs.retool.com/build/apps/guides/manage/embed): publish the app and allow your Lovable app's domain to embed it.
* [Retool classic apps](https://docs.retool.com/classic-apps/guides/app-management/embed-apps): follow the classic-app setup for embedding and custom authentication.

After linking the connection, tell Lovable which Retool app to embed and which permission group each signed-in person should use. Your app passes the person's identity along with the group, so Retool opens the app as that person. Retool counts each of these people as an external user and bills them according to your Retool plan.

## Limitations

The **Retool** connector cannot:

* Run queries inside Retool apps or read data directly from their connected resources
* Trigger workflows through Retool's webhook API, which sits outside the Retool API
* Provision people through Retool's SCIM API. Your app manages members through the Retool API instead.
* Import or convert a Retool app into a Lovable app
* Create or list Retool API access tokens
* Reach an organization on a private network or over plain HTTP. The address must use HTTPS and be reachable on the public internet.
* Let each person using your app connect their own Retool organization. Each connection uses one access token across the projects linked to it.

## Manage your Retool connection

Connections are managed from [**Connectors**](https://lovable.dev/dashboard?connectors): select **Retool**, then open the connection.

* **Unlink projects** to remove Retool access from specific projects while keeping the connection available for others. See [Unlink projects from a connection](https://docs.lovable.dev/integrations/app-connectors.md#unlink-projects-from-a-connection) for the steps.
* **Delete the connection** to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use Retool stop working until a new connection is added. See [Delete a connection](https://docs.lovable.dev/integrations/app-connectors.md#delete-a-connection) for the steps and who can delete.
