Google Meet
Ingest Google Meet conference records and participants into the workspace knowledge graph. Each conference resolves to the same `meeting` node Calendar wrote, so invite + attendance live side-by-side.
Google Meet
Conference records + participants merge into Calendar's `meeting` nodes.
The Meet connector scans historical Google Meet conference records via the Meet API v2. Each conference record becomes a meeting node with the host's space identifier and start / end times; each participant (Google-signed-in users, anonymous users with a display name, and phone-only callers) resolves to a person node and is wired to the meeting with had_participant / attended edges.
When paired with the Calendar connector, the Meet conference record dedupes against the same meeting node the calendar invite wrote — so "the invite" and "the actual call" share one neighborhood in the graph.
What gets ingested
| Source | Node type | Edge type | Direction |
|---|---|---|---|
| Conference record | meeting | — | — |
| Signed-in participant | person | had_participant / attended | Meeting ↔ Person |
| Anonymous participant | person (keyed on display name) | had_participant / attended | Meeting ↔ Person |
| Phone-only caller | person (keyed on display name) | had_participant / attended | Meeting ↔ Person |
Phone-only callers won't dedupe against email-keyed people from your other connectors — but the relationship still lands in the graph, which is what matters for retrieval.
Real use cases
- Did Alice actually show up? — Calendar tells you she was invited; Meet tells you she joined. The
had_participantedge confirms attendance independently of the invite. - Cross-source meeting timeline — combined with Zoom, Calendar, and Gmail, one
personnode has every email exchange, every calendar invite, every Meet attendance, and every Zoom call. The agent doesn't have to reconcile — it just traverses.
Settings
| Key | Type | Default | Description |
|---|---|---|---|
backfill_days | number | 90 | How far back to scan the Meet conference-records API. |
OAuth scopes
meetings.space.readonly— read conference-record metadata and participant listsuserinfo.email— resolve the connecting user's email
Read-only. The connector cannot create, modify, or delete Meet spaces.
Google Calendar
Ingest calendar events, attendees, and locations into the workspace knowledge graph. People you meet about become first-class entities your AI agents can query across surfaces.
Zoom Meetings
Ingest Zoom meetings, attendees, and recorded transcripts into the workspace knowledge graph. The connector infers action items, deliverables, decisions, problems, and opportunities as typed nodes and wires them to the people they belong to.