Google Meet + Konnectify
Google Meet Integration with Konnectify
Automate communications workflows by syncing Google Meet spaces, conference analytics, participants, recordings, transcripts, and calendar scheduling with Konnectify.
Spaces Conferences Participants Recordings Transcripts Calendar 2 Triggers 17 Actions
What is Google Meet?
Google Meet is Google’s video conferencing platform for hosting meetings, creating meeting spaces, and collaborating with participants in real time. With Konnectify, you can automate meeting operations and reporting—tracking conferences, participants, recordings, and transcripts, and scheduling meetings through Google Calendar.
This integration is best suited for comms and operations teams that want consistent meeting governance, auditable conference records, and automated post-meeting workflows.
New to Google Meet?
Learn about Meet and Google Workspace plans, and start hosting meetings.
Visit Google MeetWhat you can automate
• Create and manage Meet spaces (meeting links and settings)
• Track conference lifecycle events (started/ended) for reporting
• Pull conference records for audits and analytics pipelines
• List participants and sessions for attendance insights
• Fetch recording and transcript metadata (where enabled)
• Schedule meetings in Google Calendar with attendees and details
API & Authentication
Authentication: OAuth 2.0 authorization
Konnectify connects to Google using OAuth 2.0. During connection, you’ll sign in to Google and grant the requested permissions. Konnectify stores the resulting access token securely and can refresh it (offline access) so your workflows continue running without repeated manual logins.
Permissions & capabilities
- Meet spaces: create and update meeting spaces and manage space settings (scope includes Meet spaces creation).
- Conference insights: list and fetch conference records, participants, sessions, and related metadata.
- Calendar scheduling: create events on Google Calendar with attendees, location, and description (Calendar scope).
- Recordings & transcripts: list and fetch recording/transcript metadata, and list transcript entries (availability may depend on Workspace configuration).
Important: plan restrictions & API limits
Google Workspace features such as recordings and transcripts may require specific Meet/Workspace editions, admin settings, and meeting policies. Google APIs also enforce rate limits and quotas—Konnectify will retry transient failures, but high-volume polling workflows should be designed with appropriate intervals and filtering.
How to connect Google Meet to Konnectify
Prerequisites
- A Konnectify account with permission to create and run workflows
- A Google account in a Workspace where Meet API access is permitted
- A Google OAuth Client ID and Client Secret (from Google Cloud Console)
- Admin policies enabled (as needed) for recordings/transcripts and Meet access
Add Google Meet to a Workflow
- Open Konnectify and create a new Workflow (or edit an existing one).
- Click Add step and search for Google Meet.
Authorize via OAuth 2.0
- When prompted, enter your Client ID and Client Secret.
- Complete the Google consent screen and grant the requested permissions (Meet + Calendar).
Configure the Trigger or Action
- Select a Trigger (e.g., conference started/ended) or an Action (e.g., create space, list participants).
- Provide any required identifiers such as space resource name or conference record name.
Warning
Google Meet resources often use canonical resource names (for example spaces/AAA-BBBB-CCC). Ensure you pass the full resource name exactly as returned by list/get actions to avoid 404/permission errors.
Test the Workflow
- Run a test to validate authentication and inputs.
- Review the output payload to confirm resource names and fields you’ll use in later steps.
Activate the Workflow
- Turn on the Workflow to start processing in real time (or on the polling interval).
- Monitor runs and adjust polling frequency to match your operational needs and quotas.
Triggers 2
This integration includes 2 polling triggers. Polling triggers periodically check Google Meet for new/updated records and emit events into your workflow.
Conferences 2 triggers
Conference StartedPolls conferenceRecords.list and emits conference records.
Conference EndedPolls conferenceRecords.list and emits only ended conference records.
Actions 17
Use actions to create spaces, query conference analytics, fetch participants and sessions, and work with recording/transcript metadata. Calendar scheduling is also available for end-to-end meeting automation.
Spaces 4 actions
Create SpaceCreates a Meet space using the Meet REST API.
Get SpaceGets one Meet space (for example spaces/AAA-BBBB-CCC).
Update SpaceUpdates meeting-space settings using spaces.patch.
End Active ConferenceEnds currently active conference in the specified space.
Conferences 3 actions
Get Conference RecordFetches a single conference record.
List Conference RecordsLists conference records from Meet REST API.
Tip: Use List Conference Records first to capture the correct resource name, then call Get Conference Record.
Participants 4 actions
Get ParticipantGets one participant by participant resource name.
List ParticipantsLists participants for a conference record.
Get Participant SessionGets a single participant session.
List Participant SessionsLists participant sessions under a participant resource.
Recordings 2 actions
Get Recording (Beta)Gets one recording metadata record.
List Recordings (Beta)Lists recording metadata resources.
Transcripts 4 actions
Get Transcript (Beta)Gets one transcript metadata record.
List Transcripts (Beta)Lists transcript metadata resources.
Get Transcript Entry (Beta)Gets one transcript entry.
List Transcript Entries (Beta)Lists transcript entries under a transcript resource.
Calendar 1 action
Schedule Event In CalendarCreates a new event on a specific calendar with attendees, location, and description.
Note: This action requires additional configuration fields (for example calendar and event details).
Popular automations
Examples you can build with Google Meet + Konnectify using the available triggers and actions:
Auto-log conference details when a meeting starts
When a conference starts, enrich the event with full conference metadata for analytics, audits, or downstream notifications.
Conference Started → Get Conference Record → Get Space
Capture attendance when a conference ends
On meeting end, pull participants and their session details to generate attendance and engagement summaries.
Conference Ended → List Participants → List Participant Sessions
Automatically discover recordings for completed conferences
After a meeting ends, list recordings and fetch recording metadata to drive archival, compliance, or internal sharing workflows.
Conference Ended → List Recordings → Get Recording
Provision a new Meet space and schedule it in Calendar
Create a dedicated Meet space, then schedule a Calendar event that includes the meeting details for attendees.
Create Space → Schedule Event In Calendar
FAQ
How does authentication work for Google Meet in Konnectify?
The integration uses OAuth 2.0. You provide a Google OAuth Client ID/Secret, sign in to Google, and grant permissions. Konnectify stores tokens securely and can refresh them (offline access) so workflows keep running.
Which Google Workspace plans are supported?
Support depends on your Workspace edition and admin policies. Core space and conference record access is generally available where the Meet API is enabled. Features labeled Beta (recordings/transcripts metadata) may require additional licensing and settings (for example, recording/transcription enabled for the organizer).
Are triggers real-time or polling?
Both available triggers are polling triggers. They periodically call conferenceRecords.list and emit records that match the trigger criteria (started or ended). Adjust the polling interval to balance freshness with API quota usage.
How do I prevent duplicates?
This version of the integration does not include dedicated “upsert” actions. For duplicate prevention, use stable identifiers from the payload (for example, the conference record resource name) and apply workflow logic such as deduplication steps, idempotency keys, or “check-before-create” patterns in downstream systems.
What happens if Google rate-limits my workflow?
Google APIs enforce quotas and may return rate-limit responses. Konnectify typically retries transient errors with backoff. If you consistently hit limits, reduce polling frequency, narrow the data you pull (for example, fetch only what you need), and stagger workflows across time windows.
Can I connect multiple Google accounts or workspaces?
Yes. Create multiple Konnectify connections—each authorized with a different Google identity (or Workspace). Then select the appropriate connection per workflow step to keep environments separated (e.g., Sales Workspace vs. Support Workspace).
Why can’t I see recordings or transcripts for a conference?
Recording/transcript metadata availability depends on meeting settings and Workspace policies. Confirm that recording and/or transcription was enabled for the meeting, that the organizer’s plan supports it, and that your OAuth consent includes the required permissions. Also note these endpoints are labeled Beta in this integration and may behave differently as Google evolves the API.
Ready to automate your Google Meet workflows?
Connect Google Meet to Konnectify and orchestrate meeting operations—from spaces and conference records to scheduling.
Get started free →