Google Workspace (G Suite)

A Webflow site collects form submissions, stores them, and sends email notifications. It does not write those submissions into a spreadsheet, create calendar events, or send mail from a company inbox. Teams that run on Google Workspace end up copying leads by hand into Google Sheets and Gmail. Content drafted in Google Docs and Sheets has no direct path into a Webflow CMS collection either.

Connecting Google Workspace and Webflow automates lead handling, content publishing, registration, and booking across both platforms.

Marketing managers, agency designers, content editors, event coordinators, small-business owners, and ops leads use this setup to automate lead routing, publishing, registration, booking, and sales handoffs.

How to integrate Google Workspace (G Suite) with Webflow

What is Google Workspace (G Suite)? Google Workspace is Google's cloud-based productivity and collaboration suite, formerly called G Suite. It includes Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, and Apps Script, plus admin and security tools such as Admin, Endpoint, and Vault. Apps Script adds low-code automation across those apps and can receive POST requests from external sites.

Teams pair the two when lead handling and content production already run through Google apps. Nursa, a healthcare staffing platform, routes Webflow form submissions through Zapier into Google Sheets for lead categorization and into Gmail for sales alerts.

The Google Workspace-Webflow integration supports three approaches:

• Code Embed elements place Google Forms, Calendars, and published Docs, Sheets, and Slides on a page without code.
• Zapier, Make, n8n, and viaSocket route form submissions into Sheets, Gmail, Calendar, and Drive, and push Sheet rows into CMS collections.
• The Webflow Data API and Google Workspace APIs give you full control over webhooks, CMS writes, and Gmail sends, but require server-side development.

Most implementations combine two or more of these methods depending on the complexity of the setup.

Add Google Workspace content with Code Embed elements

Google generates embed code for Forms, Calendar, and any published Docs, Sheets, or Slides file. You paste that code into a Code Embed element, and the content renders inside an iframe that Google controls. The element accepts up to 50,000 characters and supports HTML, <style>, and <script> tags. Server-side languages are unsupported. This method requires paid Webflow access. Use it when Google should store the data and you want no automation layer in between.

Embed a Google Form

Google Forms writes every response into a linked Google Sheet automatically, so an embedded form needs no connector. Embedded forms handle lead generation, registration, surveys, and quizzes on Webflow pages. Styling is limited to the form's theme controls for color, background, header image, and fonts. File upload questions require respondents to sign in to a Google Account, and so does the "Limit to 1 response" setting.

To embed a form:

1. In Google Forms, open the form, click Send, and select the Embed tab. Some accounts show this under the More menu as Embed HTML.
2. Copy the <iframe> code.
3. In Webflow, open the Add panel (CMD+E or CTRL+E), add a Code Embed element, paste the code, and click Save and close.
4. Publish the site.

Responses appear in the Forms dashboard and the linked Sheet, which the automation tools below can also read.

Embed a Google Calendar

Visitors can see upcoming events through a calendar embedded on an events or booking page. The calendar must be public for visitors to see it, and the embed needs a minimum width and height of 500 pixels each.

To embed a calendar:

1. In Google Calendar settings, select the calendar and check Make available to public under Access permissions for events.
2. Click Integrate calendar, then click Customize under Embed code.
3. Set the size and view options and copy the code.
4. Paste the code into a Code Embed element in Webflow and publish.

Events on private calendars stay hidden even inside the embed, so keep booking calendars separate from internal ones.

Publish a Doc, Sheet, or Slides deck to the web

Schedules, public reports, and price lists maintained in Google Sheets can stay current on the page through a read-only published file. On work or school accounts, an administrator can limit who can access a published file, so confirm that setting first.

To publish and embed a file:

1. Open the file and click File > Share > Publish to web.
2. Select the Embed tab, choose your options, and click Publish.
3. Copy the HTML and paste it into a Code Embed element in Webflow.

Publishing exposes the file to anyone with the URL, and it stays public until you explicitly stop publishing.

Connect with Zapier, Make, n8n, or viaSocket

A new Webflow event, such as a form submission, can start a Google action through Zapier, Make, or viaSocket; each platform has a Webflow connector and connectors for Google Sheets, Gmail, Drive, Calendar, Docs, and Forms. The reverse flow works as well. n8n has a Webflow connector and connectors for Google Sheets, Gmail, Drive, Calendar, and Docs. Zapier and Make are also listed on the Webflow Marketplace, and Google's integrations page names Zapier as working with Google Workspace. A Webflow form needs at least one real submission before you connect it to a Zap. CMS actions through Zapier need a CMS Site plan.

To send Webflow form data to Google Sheets with Zapier:

1. In Zapier, go to Zaps > Create > New Zap.
2. Choose Webflow as the trigger, select Form submission, then choose your site and form.
3. Click Test trigger to pull a recent submission.
4. Choose Google Sheets as the action app, map form fields to columns, and click Publish.

Confirmed Webflow and Google Workspace pairings include:

• Webflow New Form Submission → Google Sheets Create Spreadsheet Row (Zapier template)
• Webflow New Form Submission → Gmail Send Email, up to 20 recipients (Zapier)
• Webflow New Form Submission → Google Calendar Create Detailed Event (Zapier)
• Webflow New Form Submission → Google Drive Upload File (Zapier)
• Google Sheets New or Updated Spreadsheet Row → Webflow Create Live Item or Update Live Item (Zapier template)
• Google Forms Get or Search Responses → Webflow Create Item (Make)
• Webflow Watch Events (webhook-based) → Google Sheets Append Rows (Make)
• Webflow Trigger → Google Sheets append row (n8n workflow template)
• Webflow Collection Item Created → Google Sheets Add New Row (viaSocket)

For relational content, use a dedicated sync app or the Data API.

Sync Google Sheets to CMS collections with Sheetflow or Whalesync

Content teams that maintain a full collection in one spreadsheet can run scheduled or real-time syncs through Sheetflow, Whalesync, or Byteline. These third-party Webflow Marketplace apps connect Google Sheets with the CMS. Marketplace apps go through a quality review. Webflow does not certify or endorse them.

Install the app from its listing, authorize your Google account and Webflow site, then map spreadsheet columns to collection fields.

Each app covers a different slice of the sync problem:

• Sheetflow syncs every 5 minutes, hourly, or daily; handles Reference and Multi-Reference fields, images, and Markdown-to-Rich-Text conversion; and can auto-publish.
• Whalesync runs a two-way sync between Google Sheets and the CMS and supports multi-reference fields.
• Byteline offers one-way or two-way sync.

Synced items render through a Collection List on any page, so editors never open the CMS panel.

Build with the Webflow and Google Workspace APIs

Signature verification and custom field mapping require direct API work. This approach also supports writes to reference fields beyond the capabilities of no-code tools. The Webflow Data API v2 lives at https://api.webflow.com and every request carries an Authorization: Bearer YOUR_TOKEN header; API v1 was deprecated on March 31, 2025. Google APIs require a Google Cloud project and an OAuth consent screen. Authentication uses either an OAuth client ID or a service account. Every path here needs a server, serverless function, or Apps Script project to hold credentials and receive webhooks.

The relevant APIs are:

• Google Sheets API v4 handles reading, appending, and updating spreadsheet values
• Gmail API v1 handles sending mail from a Workspace mailbox
• Google Calendar API v3 handles listing, creating, and watching events
• Google Forms API v1 handles reading responses and push notifications
• The Webflow Data API handles CMS collections and form submissions
• Webflow webhooks support 14 real-time trigger types. Those types include form_submission and collection_item_created; site_publish is another.

Site tokens live under Site settings > Apps & integrations > API access; OAuth apps use the Authorization Code Grant flow with codes valid for 15 minutes.

Send Webflow form submissions to Google Sheets with a webhook

The form_submission event delivers each submission's JSON to your endpoint the moment a visitor submits. Your handler validates the signature, reshapes the fields, and appends a row with the Sheets API. This replaces the Zapier flow when you need custom validation or a direct path between the platforms.

To implement this:

1. Register the webhook with the sites:write scope:

POST https://api.webflow.com/v2/sites/{site_id}/webhooks
Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

{
  "triggerType": "form_submission",
  "url": "https://your-server.example.com/webhook",
  "filter": { "name": "Contact Form" }
}

2. Verify each delivery. Concatenate timestamp:request_body, compute an HMAC-SHA256 with your signing key, and compare it to the x-webflow-signature header. Reject requests whose x-webflow-timestamp is more than 5 minutes old, then return HTTP 200.
3. Read payload.data from the body. A contact form delivers keys such as "First Name", "Last Name", and "email"; map them to an array in your sheet's column order.
4. Append the row using the https://www.googleapis.com/auth/spreadsheets scope:

POST https://sheets.googleapis.com/v4/spreadsheets/{spreadsheetId}/values/{range}:append
    ?valueInputOption=RAW
Authorization: Bearer YOUR_GOOGLE_TOKEN
Content-Type: application/json

A range such as Sheet1!A:Z lets the API find the next empty row, and valueInputOption=USER_ENTERED makes Google parse dates and numbers. If a service account writes the sheet, share the spreadsheet with the service account's email address first. After a non-200 response, the webhook retries three times at 10-minute intervals, then deactivates and sends an email notification.

Publish Google Sheets rows as CMS items with Apps Script

An installable onEdit trigger can run inside Google Sheets and use UrlFetchApp to post an edited row to the Webflow Data API as a live CMS item. Apps Script supplies the runtime. Services that require authorization need an installable trigger because simple onEdit triggers cannot access them. This suits editorial teams who run a content calendar from one shared Sheet.

To implement this:

1. Store the Webflow token securely in Script Properties:

PropertiesService.getScriptProperties().setProperty('WEBFLOW_TOKEN', 'your_token');

2. Create the installable trigger:

ScriptApp.newTrigger('myFunction')
  .forSpreadsheet(SpreadsheetApp.getActive())
  .onEdit()
  .create();

3. Post the row to the live items endpoint with the cms:write scope:

function syncRowToWebflow(collectionId, itemFields) {
  const token = PropertiesService.getScriptProperties().getProperty('WEBFLOW_TOKEN');
  const options = {
    method: 'POST',
    headers: { 'Authorization': 'Bearer ' + token, 'Content-Type': 'application/json' },
    payload: JSON.stringify({ fieldData: itemFields }),
    muteHttpExceptions: true
  };
  UrlFetchApp.fetch('https://api.webflow.com/v2/collections/' + collectionId + '/items/live', options);
}

POST /v2/collections/{collection_id}/items/live publishes the item immediately, while POST /v2/collections/{collection_id}/items creates a staged item you publish later through /items/publish. To update an existing item, store its Webflow item ID in a Sheet column and call PATCH /v2/collections/{collection_id}/items/{item_id}/live. Installable triggers run under the authorization of the user who created them, even when another editor makes the change.

Email form submissions through the Gmail API

Messages sent through the Gmail API use a Workspace mailbox, so replies land in the right inbox and the message can address the submitter directly. Register the same form_submission webhook as above, then build and send an RFC 2822 message from your handler.

To implement this:

1. Build the message string: To: admin@example.com\r\nFrom: noreply@example.com\r\nSubject: New Form Submission\r\n\r\nBody text.
2. Base64URL-encode the entire string.
3. Send it with the gmail.send scope:

POST https://gmail.googleapis.com/gmail/v1/users/{userId}/messages/send
Authorization: Bearer YOUR_GOOGLE_TOKEN
Content-Type: application/json

{ "raw": "<base64url-encoded RFC 2822 message>" }

To send as a specific Workspace user from a service account, a super admin grants domain-wide delegation under Security > Access and data control > API Controls > Manage Domain Wide Delegation. Each request then names that user in the JWT sub claim. gmail.send is a Sensitive scope, so a public app needs Google's verification, which takes 3–5 business days. Verification requires a scope declaration and privacy policy. Applicants also submit a demonstration video. An unverified published app is capped at 100 users unless a Workspace admin marks it Trusted.

What can you build with the Google Workspace Webflow integration?

A shared Sheet can receive leads from a Webflow site while Google apps handle alerts and events. Content can also move in the other direction, from Sheets or Docs into the CMS, without manual copy-paste or a separate CRM.

• Lead tracker in Google Sheets with Gmail alerts: A Webflow contact form appends each submission to a shared Sheet and emails the sales team. Orchard, a real estate company, runs this pattern in Zapier; the team says "This one Zap saves the Orchard team two to three hours a week."
• Google Sheets as a content source for CMS collections: Editors fill rows in a Sheet and the rows publish as blog posts or job listings. Upwork built a Sheet template mirroring its CMS structures and reported "Adding content for six pages was done in 10 seconds!" The Amateur Chess Organization connected Google Spreadsheets to its CMS through Zapier to replicate complex data relationships.
• Embedded Google Forms for registration and data capture: MILKLAB, a plant-based beverage brand, uses Google Forms alongside Jotform and Mailchimp for data capture on its Webflow site. The same embed handles event sign-ups, customer surveys, and quizzes on a landing page.
• Google Docs content hub with gated downloads: Silver Arrow Creative imported 450+ Google Docs files into the Webflow CMS as rich text for the Prohuman Foundation, an education nonprofit, and gated the hub for lead generation.

If you need more control over reference-field mapping or signed webhook delivery, the API integration path covers those cases with full flexibility.