Meetings model
The meetings model captures calls and meetings: start time, duration, participants, and optional transcript-derived fields such as summary and sentiment. It powers Meeting occurred timeline activity and meeting-centric analytics.
Typical sources
Meeting models are commonly backed by:
- Zoom
- Gong
- Microsoft Teams (may coexist with Teams conversations)
- UpdateAI
- Fathom
Exact availability depends on your workspace’s connections; see Data connections.
Setup is usually connection-driven: add the integration, authorize, then confirm the Meeting model under Configuration → Data models and refresh.
Query-based configuration
On unified CRM or warehouse connections (for example Salesforce, HubSpot, or a database), you can define a Meeting model with a query if your workspace supports it.
Field reference
Model keys
| Property | Type | Description |
|---|---|---|
account_id | string | Account associated with the meeting (must exist in accounts model). |
meeting_id | string | Stable identifier for the meeting in the source. |
Default properties
| Property | Type | Description |
|---|---|---|
start_time | timestamp | Scheduled or actual start. |
duration | integer | Length in seconds (or source-native unit as documented for your connector). |
sentiment | float | Optional aggregate sentiment when transcripts are analyzed. |
Optional properties
| Property | Type | Description |
|---|---|---|
summary | string | Short summary from notes or transcript analysis. |
attendees | json | List or structure of attendees. |
invitees | json | Invited participants if distinct from attendees. |
source | string | System or provider name for the meeting. |
zoom_meeting_id | integer | Provider-specific meeting id when using Zoom-related pipelines. |
Additional mapped columns may be stored as custom properties where supported.
Verification
After refresh, open an account with known calls and check the timeline for Meeting occurred and any summary or sentiment fields in the UI.