What it is
Meeting notes plus action items, pushed in from external tools (transcription services, notetakers, automations). One row per meeting: title, date, attendees, a condensed summary, the action items, and optionally the full verbatim transcript. Agents read these like any other view — a meeting pushed here is immediately queryable and citable in chat. Thetranscript column is search-indexed but excluded from default projections, so heavy meetings don’t weigh down every query.
How it gets data
Ingest-enabled — external ingest is the primary write path (see Ingest API):- One JSON record per request; unknown fields are dropped.
- Idempotent upsert on
(tenant_id, external_id)— use the source tool’s meeting id asexternal_idso re-delivery updates instead of duplicating. tenant_id/workspace_idcome from the API key context, never from the body.
Fields
Create-only: settable when the row is created (via ingest or
data_row_create), not editable afterwards in the app. “API only” = real database column not registered as a visible app column.
Like every workspace table, meeting notes also carry the system columns
id, tenant_id, workspace_id, created_at, and updated_at — set automatically, never sent by integrations.