Google Meet

How to integrate Google Meet with Webflow

Connecting Google Meet to Webflow lets you build scheduling workflows, meeting directories, and video conferencing functionality directly into your site. Visitors can book consultations, register for events, or access recurring office hours without leaving your Webflow pages.

Webflow sites connect to Google Meet through automation platforms like Zapier that create meetings from form submissions, static hyperlinks for recurring meeting rooms, or direct API integration using the Google Calendar API for custom scheduling workflows.

Use automation platforms

Automation platforms create Google Meet meetings automatically when visitors submit Webflow forms. This method requires no coding and handles authentication, meeting creation, and participant notification through pre-configured workflows. Zapier offers the most mature solution with a ready-to-use template specifically designed for Webflow form submissions.

The following use cases work with automation platforms:

• Consultation booking forms trigger scheduled meetings with client details pre-populated in the event
• Demo request automation creates sales demo sessions and delivers meeting links via email
• Interview scheduling generates candidate interview links with hiring team attendees
• Support session creation schedules troubleshooting meetings with urgency-based routing

IFTTT also supports basic if-then workflows connecting Webflow forms to Google Meet for simpler automation needs, though with fewer customization options than Zapier.

These platforms handle Google OAuth authentication and manage API rate limits automatically. You configure trigger conditions (which form, which fields) and action parameters (meeting duration, attendees, description) through visual interfaces. Zapier's pre-built template creates Google Meet meetings from new Webflow form submissions without custom configuration.

Embed static meeting links

Static meeting links connect visitors directly to recurring Google Meet rooms using Webflow's native link component. This approach works for public meetings, scheduled classes, or shared team rooms where the same meet.google.com URL serves all participants. You create a Google Meet room once, copy the URL, and add it as a standard hyperlink in your Webflow content.

Follow these steps to embed a static link:

1. Create a Google Meet room in your Google Calendar or at meet.google.com
2. Copy the meeting URL (format https://meet.google.com/abc-defg-hij)
3. Select text or button in Webflow
4. Paste the Meet URL in the link settings panel
5. Publish your site

This method works for the following scenarios:

• Weekly office hours with a permanent room link displayed on your site
• Group training sessions where students access the same virtual room
• Team collaboration spaces embedded in internal dashboards or resource pages
• Public Q&A sessions where all participants join through a shared link

This method requires no authentication, APIs, or third-party services. The meeting link remains functional as long as the Google Meet room exists. You update links manually in Webflow if you need to change the meeting room.

Build with Google Calendar and Google Meet APIs

The Google Calendar API automatically generates Google Meet links when you create calendar events with conference data by including a conferenceData object with conferenceSolutionKey.type: "hangoutsMeet". This method gives you complete control over meeting creation logic and CMS integration. You can build custom workflows that respond to Webflow form submissions, update CMS collections with meeting data, or schedule events based on availability rules.

The Calendar API approach works better than the Meet API v2 for most Webflow integrations. Meet API v2 creates "spaces" without scheduled times or calendar entries, making them difficult to manage for timed appointments. Calendar events provide start times, end times, participant lists, and automatic Meet link generation through the conferenceData object in a single API call, with the Meet link accessible via the hangoutLink field or conferenceData.entryPoints[].uri.

Critical limitation for real-time CMS sync: Webflow does not accept inbound webhooks for CMS creation. Calendar event synchronization to Webflow CMS requires a custom backend service that receives Google Calendar webhook notifications and proxies data to Webflow's CMS API. This architecture is detailed in Webflow's webhooks documentation.

Create meetings from form submissions

Form submission workflows connect Webflow's Forms API to Google Calendar's event creation endpoint. When visitors submit forms, your backend service fetches submission data, creates a calendar event with conference data (including the conferenceData.conferenceSolutionKey.type: "hangoutsMeet" parameter), and the Calendar API automatically generates a Google Meet link that can be optionally stored back in Webflow via the CMS API.

The API workflow follows these steps:

1. Fetch form submissions with GET /forms/{form_id}/submissions to retrieve visitor details like name, email, and preferred time
2. Create calendar event with POST /calendars/{calendarId}/events including conferenceData object to generate scheduled meeting with automatic Meet link
3. Store Meet link with POST /collections/{collection_id}/items to create Webflow CMS item containing meeting details
4. Publish content with POST /collections/{collection_id}/items/publish to make meeting information visible on live site

Sample calendar event creation payload:

{
  "summary": "Product Consultation with Jane Smith",
  "start": {
    "dateTime": "2025-11-15T14:00:00-07:00",
    "timeZone": "America/Los_Angeles"
  },
  "end": {
    "dateTime": "2025-11-15T15:00:00-07:00",
    "timeZone": "America/Los_Angeles"
  },
  "attendees": [
    {"email": "jane.smith@example.com"}
  ],
  "conferenceData": {
    "createRequest": {
      "requestId": "unique-request-id-12345",
      "conferenceSolutionKey": {
        "type": "hangoutsMeet"
      }
    }
  }
}

The API response includes conferenceData.entryPoints[] containing the generated Meet link. Extract entryPoints[0].uri to get the join URL, which will be in the format https://meet.google.com/[code].

Google Calendar API requires OAuth 2.0 with scopes https://www.googleapis.com/auth/calendar or https://www.googleapis.com/auth/calendar.events for creating and managing calendar events. Webflow requires Bearer token authentication with scopes forms:read (read form schemas and submissions) and cms:write (create, update, and delete CMS content). Full setup instructions are available in the Google Calendar API authentication guide and Webflow scopes reference.

Sync calendar events to Webflow CMS

Calendar API push notifications deliver webhook events when calendar entries change. Your backend service receives these notifications via HTTP headers (including X-Goog-Resource-State indicating the event type), fetches updated event data using the resource URI, and synchronizes meeting details to Webflow collections via the CMS API. This method works for dynamic event listings, upcoming meeting displays, or conference record archives.

Critical limitation: Push notifications do not contain the full event payload in the request body. You must make a GET request to retrieve complete calendar event data including Google Meet conference information. Webflow does not accept inbound webhooks, so you need a custom backend service that receives Google Calendar notifications and proxies data to Webflow's CMS API.

Create a notification channel with POST /calendars/{calendarId}/events/watch:

{
  "id": "unique-channel-identifier",
  "type": "web_hook",
  "address": "https://your-backend.com/calendar-webhook"
}

Google sends POST requests to your webhook URL with the X-Goog-Resource-State header indicating the event type:

• exists — Event created, updated, or modified (triggers CMS create/update)
• not_exists — Event deleted (triggers CMS archival)
• sync — Initial synchronization message (setup confirmation)
• reload — Resource requires full reload (requires full synchronization workflow)

The CMS synchronization workflow follows these steps:

1. Receive webhook with X-Goog-Resource-State: exists
2. GET request to X-Goog-Resource-URI fetches complete event data
3. Extract fields like summary, start.dateTime, hangoutLink, conferenceData.conferenceId
4. Create CMS item with meeting details
5. Publish item to make visible on live site

The Google Calendar Events Resource reference documents all available payload fields including hangoutLink (direct Meet URL) and conferenceData.entryPoints[] (join methods with phone dial-in details).

Access meeting recordings and transcripts

Google Meet provides automated recording and transcript capabilities as premium features. The Google Meet API v2 provides access to conference records, participant data, recordings, and transcripts after meetings conclude. These endpoints work for post-meeting analytics, content archival, or compliance workflows rather than meeting creation.

Conference record endpoints include:

• GET /v2/conferenceRecords lists all completed meetings
• GET /v2/conferenceRecords/{conferenceRecord}/participants returns attendee information
• GET /v2/conferenceRecords/{conferenceRecord}/recordings fetches recording files
• GET /v2/conferenceRecords/{conferenceRecord}/transcripts retrieves transcript documents

These recordings and transcripts can be stored in Webflow collections for searchable content libraries, training resource centers, or client deliverables portals. The Meet API v2 requires OAuth 2.0 with scopes like https://www.googleapis.com/auth/meetings.space.readonly for viewing meeting data. Full scope requirements are documented in the Meet API authentication guide.

What you can build

Integrating Google Meet with Webflow lets you build scheduling workflows, meeting directories, and video conferencing functionality. Automation platforms handle simple form-to-meeting workflows without code, while API integration supports custom implementations requiring backend development.

• Consultation booking sites: Build contact forms that automatically schedule meetings, send calendar invites, and display upcoming appointments in a CMS powered schedule page using automation platforms like Zapier
• Course registration platforms: Create class enrollment forms that generate Google Meet links and display them in student dashboards with start times and join buttons (requires Calendar API integration for dynamic CMS sync)
• Event listing pages: Display Google Calendar events on Webflow pages with titles, descriptions, timestamps, and Meet join links (requires custom backend service to proxy Calendar API webhooks to Webflow CMS due to Webflow's webhook limitations)
• Support request portals: Build help request forms with urgency levels that trigger scheduled Google Meet troubleshooting sessions through automation platforms, creating tickets in Webflow collections that include meeting links, customer details, and priority status