Insert form data directly into Supabase tables. Connect your native Framer forms to Supabase in 30 seconds with zero client-side API key leaks.
When the rest of your product runs on Supabase, Framer form data belongs in your own Postgres tables, next to users and orders, where SQL, views and row level security already work. FramerSend inserts one row per submission into the table you name, through Supabase's REST API, with each form field going to the column of the same name.
Forms and tables rarely line up perfectly, so the connector is forgiving. If Supabase reports an unknown column, FramerSend checks which columns exist, matches field names to them in lowercase or snake_case (with a few German and Spanish aliases), and puts the leftover answers into a catch-all column such as a jsonb column named data. The key you use, ideally the service role key, stays on FramerSend's server and never reaches the Framer site.
What gets created: One new row in the table you name, inserted with POST /rest/v1/{table} and Prefer: return=minimal. Rows are never updated or upserted.
| Framer form field | Supabase |
|---|---|
| Every form field | Column with the same nameThe first attempt sends the fields exactly as received, with no email cleanup or name splitting. |
| Fields whose names do not match a column | Lowercase or snake_case columnUsed only after Supabase reports an unknown column. First Name can land in first_name; umlauts become ae, oe, ue and accents are dropped. |
| E-Mail-Adresse, Vorname, Nachname, Telefonnummer, Nombre, Apellido… | email, first_name, last_name, phone…A short list of German and Spanish aliases is tried when a column is missing. |
| Anything still unmatched | Catch-all columnStored as one JSON object in the first of data, payload, metadata, form_data, submission, fields, raw_data, content, notes or message that exists. A jsonb column called data is the simplest. |
| Unmatched fields with no catch-all column | Not stored in SupabaseIf some fields matched, the row is inserted with those columns and the rest stay in Dashboard → 4. Logs. If nothing matched at all, the submission fails with a clear error instead of inserting an empty row. |
| File uploads | Link textThe file is stored first and its URL is inserted instead. |
| Submission time | Not addedGive the table a created_at column with default now(). |
Create the table
In the Supabase SQL editor, for example: create table submissions (id bigint generated always as identity primary key, created_at timestamptz default now(), name text, email text, message text, data jsonb); Add columns for the fields you want to query, and let data catch the rest.
Copy the project URL and key
From your project's API settings, copy the Project URL (https://xxxx.supabase.co) and a key. The service_role key is recommended because it bypasses row level security; the anon key works only with an INSERT policy on the table.
Connect Supabase in the plugin or dashboard
Search for Supabase in the FramerSend plugin inside Framer, or use Dashboard → 2. Connect CRM. Enter the URL, key and table name, then click Test. Test reads the table through the REST API and confirms it exists in the public schema.
Paste the webhook URL into Framer
In Framer, select the form, open Form → Send to → Add… → Webhook, paste the FramerSend webhook URL (https://www.framersend.com/api/submit/ followed by your form ID) and publish the site.
Check the first row
Submit the live form once and open the table in Supabase's table editor. If some answers sit in data instead of their own columns, rename the fields in Dashboard → 3. Field Mapping or add the columns.
Missing Supabase Project URL, API Key, or Table Name.
Cause: Shown by Test when a field is empty.
Fix: Fill all three fields.
Table "…" not found in your Supabase public schema.
Cause: Shown by Test when the table name does not exist in the public schema.
Fix: Check the spelling and case of the table name and that it lives in public.
Supabase error (…): …
Cause: Shown by Test for other refusals, usually a key from another project or a mistyped URL. Supabase's reply follows.
Fix: Copy the Project URL and key from the same project again.
Supabase: none of your form fields match a column in table "…", and it has no catch-all column (for example a jsonb column named "data").
Cause: Supabase reported an unknown column and none of the form fields matched an existing column, even after the lowercase, snake_case and alias checks.
Fix: Add a data jsonb column or the listed text columns, then click Retry on the failed row in Dashboard → 4. Logs.
Supabase: table "…" is missing columns for your form fields (…).
Cause: After matching, Supabase still reported a missing column. Its reply is in the brackets.
Fix: Add the column it names or a data jsonb column, then click Retry.
Supabase (HTTP …): …
Cause: Supabase refused the insert for a reason other than a missing column; its reply follows. Typical causes are row level security blocking the anon key, a NOT NULL column without a default that the form does not fill, a value of the wrong type, or a unique constraint.
Fix: Read the reply on the failed row, adjust the policy, default or column type, or switch to the service_role key, then click Retry.
No Edge Function to write. The do-it-yourself route is an Edge Function that receives the form and inserts the row. FramerSend does the insert; a function is still better when you need custom validation or several tables per submission.
Forgiving column matching. An automation platform maps every column by hand. FramerSend sends fields by name and, when a column is missing, falls back to snake_case matching and a jsonb catch-all.
Secret stays server-side. The service role key is stored on FramerSend's server. Never place it in a Framer code component, where every visitor could read it.
No per-row billing. Zapier and Make count runs against your plan. FramerSend has no submission limit.
Full comparison: FramerSend vs Zapier
Zero code or third-party plugins required
Authenticate Supabase credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to Supabase properties using our visual dropdown UI.
Paste your webhook URL into your Framer form under Send to → Webhook and publish. Submissions flow automatically.
Every plan includes Supabase and 100+ other connectors. Pay monthly, yearly, or once. Try it free for 14 days, no card needed.
For one Framer site
For freelancers and small studios
For agencies with many client sites
14-day free trial of every connector, no card needed. Form fields and FramerSend file uploads stay free forever with a free account.
Start freeEncrypted API vault, real-time delivery, and unlimited submissions
Automatically capture and route leads from your Framer forms.
Trigger automated workflows when form submissions arrive.
Keep all your form data in one place, synced in real-time.
The service_role key is recommended: it bypasses row level security and stays on FramerSend's server. The anon key works if the table has an INSERT policy for it.
No. Add columns for the fields you query often and a jsonb column named data; FramerSend puts the remaining answers there as one JSON object.
If some fields matched, the row is inserted with those columns and the other answers stay in FramerSend's Logs. If none matched, the submission fails with an error that lists the columns to add, and you get an alert email.
No. Every submission is a plain insert, so a unique constraint on email makes repeat submissions fail rather than update.
No. This connector writes rows to a table. Supabase Storage is a separate connector that stores uploaded files in a bucket.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Supabase and add your credentials. They are stored server-side and never exposed in your Framer site, which only gets a public form URL.
Yes, all API credentials are encrypted at rest. The client-side code in Framer only exposes a public Form ID, keeping your private keys entirely secure.
No. FramerSend provides unlimited form submissions across all license tiers so your live website forms never get blocked during high-traffic spikes.