Does Retool integrate with Supabase?
Yes — via PostgreSQL connector
Yes. Retool connects to Supabase by creating a PostgreSQL resource pointed at your Supabase database, using the credentials from the Supabase dashboard. From there Retool reads and writes tables directly. Many teams also add a REST API resource to hit Supabase's auto-generated endpoints. The one common snag is IPv6 — see known issues.
| Integration method | Native (PostgreSQL resource) — Retool connects to Supabase as a standard PostgreSQL resource using your project's Postgres credentials. There is no dedicated Supabase tile — you create a PostgreSQL resource and point it at Supabase. You can also call Supabase's auto-generated REST/RPC endpoints via a REST API resource for row-level-security-aware access. |
|---|---|
| Sync direction | Two-way: Retool can both read (SQL/GUI queries, dashboards) and write (insert, update, delete) against your Supabase Postgres tables. |
| Plan required | Works on Supabase and Retool free tiers. No paid plan is required to connect; paid tiers only matter for usage limits and features like Retool's outbound static IPs. |
| Setup time | ~15 minutes unverified estimate |
How to connect Retool to Supabase
- In Retool, go to Resources and click "Create new" → "Resource", then choose the PostgreSQL tile.
- In the Supabase dashboard open Project Settings → Database and copy the connection details (host, port 5432, database name, user, password).
- Important: use Supabase's connection pooler (Supavisor, "Session" mode) connection string rather than the direct connection — the direct host is IPv6-only and Retool cannot reach it (see known issues).
- Paste the values into Retool's PostgreSQL resource, enable SSL, and click "Test connection".
- Save the resource, then build queries in an app or optionally add a separate REST API resource for Supabase's REST/RPC endpoints.
Known friction points
- Supabase's direct database connection is IPv6-only, and Retool cannot connect to it over IPv6. The fix is to use the Supabase connection pooler (Supavisor, Session mode) connection string, or add Supabase's dedicated IPv4 add-on. [source]
- When also configuring Supabase Storage access through Retool, the custom S3 endpoint URL is a frequent point of misconfiguration. [source]
FAQ
- Does Retool integrate with Supabase?
- Yes. Retool connects to Supabase through a standard PostgreSQL resource using your Supabase database credentials, letting you read and write tables. There is no dedicated Supabase connector — you use the PostgreSQL tile, and optionally a REST API resource for Supabase's generated endpoints.
- Why won't my Retool–Supabase connection work even though the credentials are correct?
- Most often this is the IPv6 issue: Supabase's direct database host is IPv6-only and Retool can't reach it. Use the Supabase connection pooler (Supavisor, Session mode) connection string, or enable Supabase's dedicated IPv4 add-on.
- Do I need a paid plan to connect Retool and Supabase?
- No. The free tiers of both products are enough to create the connection. Paid plans only add higher usage limits and features such as Retool's static outbound IP addresses.
✓ Last verified: 2026-06-10 · Every claim on this page links to a primary source. If the integration changed, the page is out of date — check the sources below.
Sources
- Retool docs — Connect to PostgreSQL (accessed 2026-06-10)
- Retool community — Connecting Supabase to Retool (IPv6) (accessed 2026-06-10)
- Retool community — Connecting to Supabase via PostgreSQL resource (accessed 2026-06-10)