DatabasesPro+

Supabase

Connect SharaForms to Supabase so every submission creates a row in your database. Load tables and columns dynamically, map form fields, and configure column types.

Create a form Supabase API docs

Setup steps

1
Find your project URL and API key
Open your Supabase dashboard and select your project. Go to Project Settings (gear icon) > API. Copy the "Project URL" and either the "anon public" key or the "service_role" key.
2
Choose the right API key
Use the "anon public" key if your table has Row-Level Security (RLS) policies that allow inserts — this is the most secure option. Use "service_role" only if RLS is disabled or you need to bypass it. The service_role key has full access, so keep it secret.
3
Enter credentials in SharaForms
Paste your project URL and API key into the Supabase integration fields. The table dropdown will load automatically once both are entered.
4
Select a table and map columns
Choose the target table. Each form field gets a dropdown of available columns. Map the fields you want to sync to the right columns.
5
Set column types
For each mapped column, select the data type that matches (Text, Integer, Boolean, JSON, etc.). This ensures the data is inserted correctly into your Supabase table.
6
Test with a submission
Submit the form and confirm a new row appears in your Supabase table with the correct values and types.

Requirements

✔A Supabase project with at least one table.
✔An API key from your project (see setup step 1).
✔Pro plan access for Supabase integrations.

What this integration can do

•Dynamic table and column discovery after entering credentials.
•Per-field column mapping with explicit type casting.
•Supports text, integer, float, boolean, JSON, date, timestamp, and array types.
•Row-Level Security compatible with anon key.

Recommended setup flow

→Find your Supabase project URL and API key.
→Add the Supabase integration in your form.
→Select a table, map form fields to columns, and set types.
→Save and test with a live submission.

Practical tips

✦The anon key with RLS is the recommended approach for production — it limits what the integration can access.
✦If a column in your table is NOT NULL, make sure your form sends data for it or the insert will fail.
✦Use JSON type for complex or nested data that doesn't fit into a single text or number column.

Need another route? Visit the full integrations index to compare native integrations, connected-account flows, and external automation platforms before you commit to a setup.

Discover our other Integrations