Google Meet

Google Meet API integration with managed OAuth. Create meeting spaces, list conference records, and manage meeting participants. Use this skill when users want to interact with Google Meet. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).

MIT-0 · Free to use, modify, and redistribute. No attribution required.
14 · 16.3k · 12 current installs · 14 all-time installs
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description state a Google Meet integration and the skill only requests a Maton API key to call Maton gateway endpoints which proxy to meet.googleapis.com. The requested environment variable (MATON_API_KEY) is appropriate for a managed-OAuth gateway provider.
Instruction Scope
SKILL.md contains concrete HTTP examples and only references MATON_API_KEY and Maton endpoints (gateway.maton.ai, ctrl.maton.ai, connect.maton.ai). All instructions are within the stated purpose (creating spaces, listing records, managing connections). Note: requests are routed through Maton’s domains rather than directly to Google — that means meeting metadata and proxied API payloads pass through a third party.
Install Mechanism
No install spec and no code files beyond SKILL.md/LICENSE — instruction-only skills do not write code to disk during install, which is the lowest-risk install mechanism.
Credentials
Only a single env var (MATON_API_KEY) is required, which is proportional to a gateway-based integration. However, that key is sensitive: it grants access to Maton-managed OAuth flows and thus can be used to act on Google Meet resources for connected accounts.
Persistence & Privilege
The skill is not force-enabled (always:false) and asks for no system config paths or other skills' credentials. The agent can invoke it autonomously (default), so an agent with access to MATON_API_KEY could perform Meet actions — this is expected but worth noting.
Assessment
This skill is coherent for a Google Meet integration that uses Maton as a proxy/gateway. Before installing: (1) Verify you trust maton.ai — all API requests and proxied Google Meet traffic go through their service. (2) Treat MATON_API_KEY as a secret: use a dedicated, least-privilege key or account, and rotate/revoke it if needed. (3) Review Maton's privacy/security policies and audit logs for your account because OAuth tokens and meeting metadata will be visible to them. (4) If you need stronger assurance, prefer direct Google API integrations with credentials you control, or test Maton with a non-production Google account first. (5) Remember this is an instruction-only skill (no local code to inspect beyond the docs), so your trust decision mainly rests on the Maton service rather than on bundled code.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.4
Download zip
latestvk97cbt2kgv8ha5pa1dvfcbggts80w7cq

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🧠 Clawdis
EnvMATON_API_KEY

SKILL.md

Google Meet

Access the Google Meet API with managed OAuth authentication. Create and manage meeting spaces, list conference records, and retrieve participant information.

Quick Start

# Create a meeting space
python <<'EOF'
import urllib.request, os, json
data = json.dumps({}).encode()
req = urllib.request.Request('https://gateway.maton.ai/google-meet/v2/spaces', data=data, method='POST')
req.add_header('Authorization', f'Bearer {os.environ["MATON_API_KEY"]}')
req.add_header('Content-Type', 'application/json')
print(json.dumps(json.load(urllib.request.urlopen(req)), indent=2))
EOF

Base URL

https://gateway.maton.ai/google-meet/{native-api-path}

Replace {native-api-path} with the actual Google Meet API endpoint path. The gateway proxies requests to meet.googleapis.com and automatically injects your OAuth token.

Authentication

All requests require the Maton API key in the Authorization header:

Authorization: Bearer $MATON_API_KEY

Environment Variable: Set your API key as MATON_API_KEY:

export MATON_API_KEY="YOUR_API_KEY"

Getting Your API Key

  1. Sign in or create an account at maton.ai
  2. Go to maton.ai/settings
  3. Copy your API key

Connection Management

Manage your Google OAuth connections at https://ctrl.maton.ai.

List Connections

python <<'EOF'
import urllib.request, os, json
req = urllib.request.Request('https://ctrl.maton.ai/connections?app=google-meet&status=ACTIVE')
req.add_header('Authorization', f'Bearer {os.environ["MATON_API_KEY"]}')
print(json.dumps(json.load(urllib.request.urlopen(req)), indent=2))
EOF

Create Connection

python <<'EOF'
import urllib.request, os, json
data = json.dumps({'app': 'google-meet'}).encode()
req = urllib.request.Request('https://ctrl.maton.ai/connections', data=data, method='POST')
req.add_header('Authorization', f'Bearer {os.environ["MATON_API_KEY"]}')
req.add_header('Content-Type', 'application/json')
print(json.dumps(json.load(urllib.request.urlopen(req)), indent=2))
EOF

Get Connection

python <<'EOF'
import urllib.request, os, json
req = urllib.request.Request('https://ctrl.maton.ai/connections/{connection_id}')
req.add_header('Authorization', f'Bearer {os.environ["MATON_API_KEY"]}')
print(json.dumps(json.load(urllib.request.urlopen(req)), indent=2))
EOF

Response:

{
  "connection": {
    "connection_id": "21fd90f9-5935-43cd-b6c8-bde9d915ca80",
    "status": "ACTIVE",
    "creation_time": "2025-12-08T07:20:53.488460Z",
    "last_updated_time": "2026-01-31T20:03:32.593153Z",
    "url": "https://connect.maton.ai/?session_token=...",
    "app": "google-meet",
    "metadata": {}
  }
}

Open the returned url in a browser to complete OAuth authorization.

Delete Connection

python <<'EOF'
import urllib.request, os, json
req = urllib.request.Request('https://ctrl.maton.ai/connections/{connection_id}', method='DELETE')
req.add_header('Authorization', f'Bearer {os.environ["MATON_API_KEY"]}')
print(json.dumps(json.load(urllib.request.urlopen(req)), indent=2))
EOF

Specifying Connection

If you have multiple Google Meet connections, specify which one to use with the Maton-Connection header:

python <<'EOF'
import urllib.request, os, json
data = json.dumps({}).encode()
req = urllib.request.Request('https://gateway.maton.ai/google-meet/v2/spaces', data=data, method='POST')
req.add_header('Authorization', f'Bearer {os.environ["MATON_API_KEY"]}')
req.add_header('Content-Type', 'application/json')
req.add_header('Maton-Connection', '21fd90f9-5935-43cd-b6c8-bde9d915ca80')
print(json.dumps(json.load(urllib.request.urlopen(req)), indent=2))
EOF

If omitted, the gateway uses the default (oldest) active connection.

API Reference

Spaces

Create Space

POST /google-meet/v2/spaces
Content-Type: application/json

{}

Response:

{
  "name": "spaces/abc123",
  "meetingUri": "https://meet.google.com/abc-defg-hij",
  "meetingCode": "abc-defg-hij",
  "config": {
    "accessType": "OPEN",
    "entryPointAccess": "ALL"
  }
}

Get Space

GET /google-meet/v2/spaces/{spaceId}

Update Space

PATCH /google-meet/v2/spaces/{spaceId}
Content-Type: application/json

{
  "config": {
    "accessType": "TRUSTED"
  }
}

End Active Call

POST /google-meet/v2/spaces/{spaceId}:endActiveConference

Conference Records

List Conference Records

GET /google-meet/v2/conferenceRecords

With filter:

GET /google-meet/v2/conferenceRecords?filter=space.name="spaces/abc123"

Get Conference Record

GET /google-meet/v2/conferenceRecords/{conferenceRecordId}

Participants

List Participants

GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/participants

Get Participant

GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/participants/{participantId}

Participant Sessions

List Participant Sessions

GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/participants/{participantId}/participantSessions

Recordings

List Recordings

GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/recordings

Get Recording

GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/recordings/{recordingId}

Transcripts

List Transcripts

GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/transcripts

Get Transcript

GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/transcripts/{transcriptId}

List Transcript Entries

GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/transcripts/{transcriptId}/entries

Code Examples

JavaScript

// Create a meeting space
const response = await fetch(
  'https://gateway.maton.ai/google-meet/v2/spaces',
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': `Bearer ${process.env.MATON_API_KEY}`
    },
    body: JSON.stringify({})
  }
);

const space = await response.json();
console.log(`Meeting URL: ${space.meetingUri}`);

Python

import os
import requests

headers = {
    'Content-Type': 'application/json',
    'Authorization': f'Bearer {os.environ["MATON_API_KEY"]}'
}

# Create a meeting space
response = requests.post(
    'https://gateway.maton.ai/google-meet/v2/spaces',
    headers=headers,
    json={}
)
space = response.json()
print(f"Meeting URL: {space['meetingUri']}")

Notes

  • Spaces are persistent meeting rooms that can be reused
  • Conference records are created when a meeting starts and track meeting history
  • Access types: OPEN (anyone with link), TRUSTED (organization members only), RESTRICTED (invited only)
  • Recordings and transcripts require Google Workspace with recording enabled
  • IMPORTANT: When using curl commands, use curl -g when URLs contain brackets to disable glob parsing
  • IMPORTANT: When piping curl output to jq or other commands, environment variables like $MATON_API_KEY may not expand correctly in some shell environments. You may get "Invalid API key" errors when piping.

Error Handling

StatusMeaning
400Missing Google Meet connection
401Invalid or missing Maton API key
429Rate limited (10 req/sec per account)
4xx/5xxPassthrough error from Google Meet API

Troubleshooting: Invalid API Key

When you receive a "Invalid API key" error, ALWAYS follow these steps before concluding there is an issue:

  1. Check that the MATON_API_KEY environment variable is set:
echo $MATON_API_KEY
  1. Verify the API key is valid by listing connections:
python <<'EOF'
import urllib.request, os, json
req = urllib.request.Request('https://ctrl.maton.ai/connections')
req.add_header('Authorization', f'Bearer {os.environ["MATON_API_KEY"]}')
print(json.dumps(json.load(urllib.request.urlopen(req)), indent=2))
EOF

Troubleshooting: Invalid App Name

  1. Ensure your URL path starts with google-meet. For example:
  • Correct: https://gateway.maton.ai/google-meet/v2/spaces
  • Incorrect: https://gateway.maton.ai/meet/v2/spaces

Resources

Files

2 total
Select a file
Select a file to preview.

Comments

Loading comments…