Save every Gravity Forms submission as a row in your Supabase database

Each Gravity Forms submission on your WordPress site is inserted as a new row in a Supabase table called leads, with name, email and phone columns, so your form data sits in Postgres where your apps can query it.

Gravity Forms

Supabase

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.4k sites Databases & Sync Free to import

The Save every Gravity Forms submission as a row in your Supabase database workflow on the FlowMattic canvas, with 2 steps across Gravity Forms, Supabase — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Gravity Forms stores entries inside WordPress, which is fine until another app or a report needs to read them. Putting each entry into Supabase gives you a Postgres table that your own code, dashboards or SQL can use directly. This workflow writes every submission there.

The Gravity Forms trigger runs on each new form submission and makes the entry's fields available to map. The Supabase step then uses Insert Row. As shipped, it targets a table named leads and sends JSON with three columns: name, email and phone, each filled from the form.

Your Supabase project needs that table and those columns, or you change the table name and JSON to match your own schema. The form field references in the JSON may not match your form's fields, so run a test submission and remap them. Every submission adds a new row, and Task History shows Supabase's response for each run.

Lead capture for a custom sales app

Your sales team works in an app built on Supabase. Gravity Forms enquiries from the WordPress site land in its leads table without an export.

Reporting on form entries with SQL

An analyst queries the Supabase leads table to count enquiries by week, instead of downloading Gravity Forms entries as CSV files.

Agency site feeding a client's backend

An agency builds the marketing site in WordPress while the client's product runs on Supabase, and new form entries arrive in the client's database.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Gravity Forms New Form Submission
Starts each time someone sends a Gravity Forms form on your WordPress site. Each submitted field is passed on so it can be placed in the Supabase row.
Step 2Action
Supabase Insert Row
Inserts a row into the Supabase table leads, sending name, email and phone as JSON built from the form. Change the table name or columns to fit your schema, remap the form fields after a test, and connect Supabase.

What you need

FlowMatticCore
Gravity Forms PluginPlugin
Supabase AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Create the leads table in Supabase with name, email and phone columns before you turn the workflow on, or the insert will fail for a missing table or column.
Add more keys to the JSON in the Insert Row step, such as a source or form name, and create matching columns in Supabase to keep them.
Running several forms? Check after import whether the trigger lets you pick one form. If it doesn't, add a Filter after it on a field that identifies the form you want.

Questions about this workflow

Do I need a table called leads in Supabase?

As imported, yes. The Insert Row step writes to leads with name, email and phone columns. You can point it at another table by changing the table name and the JSON keys.

What if a Gravity Forms submission repeats an email already in Supabase?

Insert Row always tries to add a new row. If your table has no unique rule on email, you get a second row. If it does, Supabase rejects the insert and Task History shows the error. Use FlowMattic's Upsert Row action instead to update matches.

Does Gravity Forms still keep its own entry?

Yes. The workflow runs after the form is submitted and only copies the data to Supabase, so Gravity Forms saves the entry and sends its notifications as usual.