List Recordings
google_meet.list_recordings
ActionChat & messagingconnection required
Calls meet.googleapis.com/v2 conferenceRecords.recordings.list.
List the recordings produced by a finished Google Meet conference.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Meet
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- token_uri
- Resolved by
- config.connection_id, else node.connection_id
- Note
- Needs a Meet v2 scope (meetings.space.created / meetings.space.readonly). Connect-with-Google does not request it, so the step fails fast until the connection is minted with one and records it as config.scopes.
Configuration
2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
conference_record Conference record name ('conferenceRecords/abc') or bare id. | string | Yes | — | — | — |
max_results Max recordings. | number | No | 50 | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"max_results": 50
}Output
One shape.
recordings
| Field | Type | Example |
|---|---|---|
recordings Recordings: {name, state, start_time, end_time, drive_file_id, export_uri}. state is FILE_GENERATED once the file exists. | array | — |
count | number | — |
truncated True when Meet had more recordings than max_results collected. | boolean | — |
{
"count": 0,
"recordings": [],
"truncated": false
}See List Recordings run in a workflow.
In a technical demo we add the Google Meet connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.