Save each new Builder.io form submission to a Google Sheets spreadsheet

Each time a visitor submits a form on your Builder.io site, this workflow writes the submitted values into a new Google Sheets row, giving you one running list of every response.

Builder.io

Google Sheets

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 2.6k sites Free to import

The Save each new Builder.io form submission to a Google Sheets spreadsheet workflow on the FlowMattic canvas, with 2 steps across Builder.io, Google Sheets — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Builder.io lets you build pages and forms visually, but the answers people send still have to end up somewhere your team can read, sort and share. Copying them out by hand is slow and easy to forget. This workflow places every new submission in a spreadsheet as it arrives.

The Builder.io trigger fires when a new submission is made from a form. FlowMattic receives the submitted values and hands them to the next step. The Google Sheets step then adds one new row to the spreadsheet and sheet you pick, with each column filled from the form field you mapped to it.

There is no filtering in the template, so every submission becomes a row. The sheet grows in the order entries come in, and you can share it with people who never log in to Builder.io. Task History keeps a record of each run, including the data that was sent to Google Sheets.

Landing page leads for a sales team

A campaign page built in Builder.io collects names and email addresses. Sales reps work through the shared sheet instead of waiting for someone to export entries.

Product feedback forms

A feedback form on your Builder.io site sends every comment to a sheet, where your product team can sort by topic or add their own notes column.

Waitlist for a launch

Visitors join a waitlist through a Builder.io form, and the spreadsheet becomes the list you later import into your email tool.

How this workflow runs

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

Step 1Trigger
Builder.io New Form Submission
Fires when someone submits a form on your Builder.io content. The submitted values are passed on so you can map them in the Google Sheets step.
Step 2Action
Google Sheets Add New Row
Writes one row per submission into a Google Sheets spreadsheet. Connect your Google account, pick the spreadsheet and sheet, then map each column to a Builder.io form value.

What you need

FlowMatticCore
Builder.io AccountAccount
Google Sheets 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.

Give the sheet a header row before you map, with one column per form field plus a column for the submission time, so each value has a clear place.
Add a Filter after the trigger if you only want some entries in the sheet, for example ones where a particular field is not empty.
Submit a test entry on your Builder.io form after import so FlowMattic captures real field names, then finish the column mapping using that data.

Questions about this workflow

Will past Builder.io submissions be added to the sheet?

No. The trigger reacts to new submissions, so only entries made after the workflow is turned on reach Google Sheets.

Does every Builder.io form submission create a row?

Yes, as imported. Nothing in the template checks the entry first. Add a Filter between the two steps if you want to leave some out.

Can I send the same submission to a second spreadsheet?

Yes. Add another Google Sheets Add New Row step after the first one and map it to the other spreadsheet.

What happens if Google Sheets returns an error?

Task History shows the run with the error on the Google Sheets step, along with the data that was sent, so you can see what went wrong and fix the mapping or connection.