Connect Webflow forms to Google Sheets withease

It connects your client's Webflow forms to a Google Sheet in your client's own Google account. Every form submission becomes a new row, with a tab for each form. You create a project, send your client a link, and paste one webhook URL into Webflow.

Webflow developers and agencies who build sites for clients and want form submissions in a Google Sheet without paying for, or maintaining, an automation platform.

Those platforms sit in the middle: every submission passes through their servers, counts as a task, and stops arriving if the account lapses or hits its limit. Here, Webflow sends each submission straight to a small Google Apps Script in your client's spreadsheet. There's no middleman, no task counter and no monthly plan to keep paying.

Your first client setup is free. After that you pay once, never monthly: Lifetime Freelancer ($49, 10 client setups) or Lifetime Agency ($75, 25 client setups).

One client spreadsheet connected: it counts when your client finishes setup, not when you create the project. Unused setups never expire, and every connection keeps working even after your setups run out; the limit only applies to new clients.

1. Create a project: project name, your client's Google email and the names of their Webflow forms.
2. Send your client the link the app gives you.
3. When the client is done, copy the webhook URL into Webflow (Site settings → Apps & Integrations → Webhooks → Form submission) and publish.

You can send a test submission from the project page before going live.

Open the link, sign in with Google, create a new spreadsheet or paste a link to an existing one, and approve the script once. It takes about two minutes, and the page shows them each step. You see their progress live on your project page.

No. The app creates and deploys the script for them. The only extra step Google requires is turning on the "Google Apps Script API" switch the first time. If it's off, the page shows a short animation and a button that opens the right setting.

No, never. Your client signs in with Google themselves. The spreadsheet is shared with you as an editor, so you can check submissions while you build the site.

Yes. Your client pastes its link during setup. Existing tabs with matching form names are reused, and existing data is never cleared or reordered. If Google won't let the app share an existing sheet with you, the client is shown how to share it by hand.

No. Use a normal Webflow Form Block, with no custom code and no custom action. Webflow's spam filter, success and error messages and form inbox all keep working.

From the form's fields. Each field's Name in Webflow becomes a column the first time a submission arrives. Every row also gets "Submitted at" and "Form".

The sheet follows on the next submission. New fields get new columns; existing columns are never removed. A renamed form keeps its tab, which is renamed to match.

Yes. Each form gets its own tab, named after the form. Give every Webflow form a unique name (Webflow calls every new form "Email Form").

Yes, from the project page, without a new script or a new webhook. Removing a form stops new submissions to it; its tab and data stay in the sheet.

Yes. Create a project for each spreadsheet. Each one gets its own webhook URL, and each script only writes the forms listed in its project.

No. Submissions go from Webflow straight to the script in your client's Google account. They never pass through this app.

Project details: the project name, your client's name and email, the form names, and once set up, the spreadsheet and script IDs, the webhook URL and its key. Your client's Google access is used during setup only and isn't stored.

No. Nobody types a Google password, API key, client ID or client secret into this app: you sign in on Google's own page, and Google gives the app a limited permission. The only Google permission we keep is your Google Sheets access, so you can add or remove forms later without bothering your client. It's stored encrypted, and you can revoke it any time in your Google account (Security → Your connections to third-party apps & services).

No. Your client signs in on Google's own page too and never enters a password, API key or secret here. Their permission is used only during the two-minute setup, to create the sheet and its script, and expires after about an hour. It's never saved, and the app keeps no access to their Google account afterwards. What we do keep is the project's details: their email, the spreadsheet and script IDs and the webhook key. Their form submissions never reach us.

The URL never appears in your website's code, because Webflow's servers call it, not visitors' browsers. It carries a long secret key, and the script rejects any request without it. The script can only access its own spreadsheet.

Your client. The spreadsheet and the script live in their Google account, and they can see, edit or delete both at any time.

Submissions keep arriving. Once setup is done, Webflow talks directly to your client's script; this app is no longer involved. Deleting a project here doesn't touch the sheet, the script or the Webflow webhook.

There's no task counter or per-submission charge. Google applies its own daily usage limits to Apps Script, which are far above what a typical website's forms receive.

Free. Up to about 25,000 submissions a day on a free Gmail account, 250,000 on Google Workspace."

The script handles submissions one at a time, so rows never overwrite each other, and it ignores a submission it has already written if Webflow sends it twice.

Remove the webhook in Webflow (Site settings → Apps & Integrations → Webhooks). The sheet and its data stay with your client.