Google Meet
Google Meet API integration with managed OAuth. Create meeting spaces, inspect conference records, retrieve recordings and transcripts, and manage meeting pa...
Jay
@hith3sh
What This Skill Does
Google Meet API integration with managed OAuth for creating meeting spaces, inspecting conference records, retrieving recordings and transcripts, and managing participants. Handles authentication via ClawLink so no manual API key setup is needed.
Replaces manual OAuth configuration and API key management by providing a fully managed connection flow through ClawLink.
When to Use It
- Create a new Google Meet space for an upcoming meeting
- List conference records to review past meetings
- Retrieve recordings and transcripts from a completed meeting
- Get details of a specific meeting space by its ID
- Manage meeting participants via the Google Meet API
Install
$ openclaw skills install @hith3sh/google-meet-meetingsGoogle Meet
Access Google Meet via the Google Meet REST API with managed OAuth authentication. Create meeting spaces, inspect conference records, retrieve recordings and transcripts, and manage participants.
This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Google Meet API access yourself.
Setup in 3 Steps
| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Meet |
|---|---|---|
![]() | ![]() | App-specific connection GIF coming soon |
| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Meet |
How It Works
┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐
│ OpenClaw │────▶│ ClawLink │────▶│ Google Meet │
│ (User Chat) │ │ (OAuth) │ │ (Meet API) │
└─────────────────┘ └──────────────┘ └──────────────────┘
│ │ │
│ 1. Install Plugin │ │
│ 2. Pair Device │ │
│ 3. Connect Meet │ │
│ │ 4. Secure Token │
│ │ 5. Proxy Requests │
│ │ │
▼ ▼ ▼
┌──────────┐ ┌──────────┐ ┌──────────┐
│ SKILL │ │ Dashboard│ │ Google │
│ File │ │ Auth │ │ Meet │
└──────────┘ └──────────┘ └──────────┘
Install
Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.
openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart
Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Google Meet again."
Quick Start
# Create a new meeting space
clawlink_call_tool --tool "googlemeet_create_meet" --params '{}'
# List conference records
clawlink_call_tool --tool "googlemeet_list_conference_records" --params '{}'
# Get a meeting space details
clawlink_call_tool --tool "googlemeet_get_meet" --params '{"name": "spaces/YOUR_SPACE_ID"}'
Authentication
All Google Meet tool calls are authenticated automatically by ClawLink using the user's connected Google account.
No API key is required in chat. ClawLink stores the OAuth token securely and injects it into every Google Meet API request on the user's behalf.
Getting Connected
- Install the ClawLink plugin (see Install above).
- Pair the plugin with
clawlink_begin_pairingif it is not configured yet. - Open https://claw-link.dev/dashboard?add=google-meet and connect Google Meet.
- Call
clawlink_list_integrationsto verify the connection is active.
Connection Management
List Connections
clawlink_list_integrations
Response: Returns all connected integrations. Look for google-meet in the list.
Verify Connection
clawlink_list_tools --integration google-meet
Response: Returns the live tool catalog for Google Meet.
Reconnect
If Google Meet tools are missing or the connection shows an error:
- Direct the user to https://claw-link.dev/dashboard?add=google-meet
- After they confirm, call
clawlink_list_integrationsto verify - Then call
clawlink_list_tools --integration google-meet
Security & Permissions
- Access is scoped to meeting spaces and conference records the authenticated user has access to.
- Write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
- Ending an active conference is a high-impact action and must always be confirmed.
- Recordings and transcripts are subject to the organizer's domain policies — they may not be available for all meetings.
Tool Reference
Meeting Space Management
| Tool | Description | Mode |
|---|---|---|
googlemeet_create_meet | Create a new Meet space with optional configuration | Write |
googlemeet_get_meet | Retrieve details of a Meet space by its identifier | Read |
googlemeet_update_space | Update an existing Meet space's settings | Write |
googlemeet_end_active_conference | End an ongoing conference in a specified space | Write |
Conference Records
| Tool | Description | Mode |
|---|---|---|
googlemeet_list_conference_records | List past conference records, optionally filtered | Read |
googlemeet_get_conference_record_by_name | Get details for a specific conference record | Read |
Participants
| Tool | Description | Mode |
|---|---|---|
googlemeet_list_participants | List all participants in a conference record | Read |
googlemeet_list_participant_sessions | List all join/leave sessions for a participant | Read |
googlemeet_get_participant_session | Get details of a specific participant session | Read |
Recordings
| Tool | Description | Mode |
|---|---|---|
googlemeet_list_recordings | List recording resources for a conference record | Read |
googlemeet_get_recordings_by_conference_record_id | Get all recordings for a specific conference | Read |
Transcripts
| Tool | Description | Mode |
|---|---|---|
googlemeet_get_transcripts_by_conference_record_id | List all transcripts for a conference | Read |
googlemeet_get_transcript | Get a specific transcript by resource name | Read |
googlemeet_list_transcript_entries | List structured transcript entries (speaker, time, text) | Read |
googlemeet_get_transcript_entry | Get a specific transcript entry by resource name | Read |
Code Examples
Create a new meeting space
clawlink_call_tool --tool "googlemeet_create_meet" \
--params '{
"config": {
"accessType": "OPEN",
"entryPointAccess": "anyone"
}
}'
List conference records
clawlink_call_tool --tool "googlemeet_list_conference_records" \
--params '{
"page_size": 20
}'
Get meeting space details
clawlink_call_tool --tool "googlemeet_get_meet" \
--params '{
"name": "spaces/YOUR_SPACE_ID"
}'
List participants in a conference
clawlink_call_tool --tool "googlemeet_list_participants" \
--params '{
"parent": "conferenceRecords/YOUR_CONFERENCE_RECORD_ID"
}'
Get recordings for a conference
clawlink_call_tool --tool "googlemeet_get_recordings_by_conference_record_id" \
--params '{
"conference_record_id": "YOUR_CONFERENCE_RECORD_ID"
}'
End an active conference
clawlink_call_tool --tool "googlemeet_end_active_conference" \
--params '{
"space_name": "spaces/YOUR_SPACE_ID"
}'
Discovery Workflow
- Call
clawlink_list_integrationsto confirm Google Meet is connected. - Call
clawlink_list_tools --integration google-meetto see the live catalog. - Treat the returned list as the source of truth. Do not guess or assume what tools exist.
- If the user describes a capability but the exact tool is unclear, call
clawlink_search_toolswith a short query and integrationgoogle-meet. - If no Google Meet tools appear, direct the user to https://claw-link.dev/dashboard?add=google-meet.
Execution Workflow
┌─────────────────────────────────────────────────────────────┐
│ READ OPERATIONS (Safe) │
│ list → get → call │
│ │
│ Example: List conferences → Get details → Show results │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ WRITE OPERATIONS (Require Confirmation) │
│ describe → preview → confirm → call │
│ │
│ Example: Describe tool → Preview changes → User approves │
│ → Execute update │
└─────────────────────────────────────────────────────────────┘
- For unfamiliar tools, ambiguous requests, or any write action, call
clawlink_describe_toolfirst. - Use the returned guidance, schema,
whenToUse,askBefore,safeDefaults,examples, andfollowupsto shape the call. - Prefer read, list, and get operations before writes.
- For writes or anything marked as requiring confirmation, call
clawlink_preview_toolfirst. - Execute with
clawlink_call_tool. Pass confirmation only after the preview matches the user's intent. - If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.
Notes
create_meetdoes not attach to any calendar event — calendar linking requires a separate Calendar tool call.- Capture
meetingUri,meetingCode, andspace.namefrom the create response immediately for downstream lookups. - Newly created spaces may return incomplete data — retry after 1–3 seconds if needed.
- Recordings and transcripts require that recording/transcription was enabled and permitted by the organizer's domain policies.
- After a meeting ends, recordings and transcripts may take several minutes to process — an empty result may be temporary.
end_active_conferencerequires thespace_nameparameter and immediately drops all participants.- HTTP 429 may occur under rapid calls — apply exponential backoff.
Error Handling
| Status / Error | Meaning |
|---|---|
| Tool not found | The tool name does not exist in the current catalog. Verify with clawlink_list_tools --integration google-meet. |
| Missing connection | Google Meet is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-meet. |
NOT_FOUND | Meeting space or conference record does not exist. Check the name/ID. |
INVALID_ARGUMENT | Invalid parameter or missing required field. Review the tool schema with clawlink_describe_tool. |
| Write rejected | User did not confirm a write action. Always confirm before executing writes. |
Troubleshooting: Tools Not Visible
- Check that the ClawLink plugin is installed:
openclaw plugins list - If the plugin is installed but tools are missing, tell the user to send
/newas a standalone message to reload the catalog. - If a fresh chat does not help, run:
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json openclaw gateway restart - After restart, tell the user to send
/newagain and retry.
Troubleshooting: Invalid Tool Call
- Ensure the integration slug is exactly
google-meet. - Use
clawlink_describe_toolto verify parameter names and types before calling. - For write operations, always call
clawlink_preview_toolfirst.
Resources
- Google Meet API Overview
- Conference Records
- Spaces
- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-meet-meetings
- ClawLink Docs: https://docs.claw-link.dev/openclaw
- ClawLink Verification: https://claw-link.dev/verify
Related Skills
- Google Calendar — For calendar scheduling and event management
Powered by ClawLink — an integration hub for OpenClaw

Top skills in this category
Google Meet
@byungkyuGoogle Meet API integration with managed OAuth. Create meeting spaces, list conference records, and manage meeting participants. Use this skill when users wa...
Klaviyo
@byungkyuKlaviyo API integration with managed OAuth. Access profiles, lists, segments, campaigns, flows, events, metrics, templates, catalogs, and webhooks. Use this...
Twilio
@byungkyuTwilio API integration with managed OAuth. SMS, voice calls, phone numbers, and communications. Use this skill when users want to send SMS messages, make voi...
Gmail OAuth Setup
@kai-jarSet up Gmail API access via gog CLI with manual OAuth flow. Use when setting up Gmail integration, renewing expired OAuth tokens, or troubleshooting Gmail authentication on headless servers.
Gmail
@byungkyuGmail API integration with managed OAuth. Read, send, and manage emails, threads, labels, and drafts. Use this skill when users want to interact with Gmail. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).

