Meet
Meet has 6 operations in gum's generated catalog. Start with search when you know the task, use describe to inspect request fields and scopes, then dispatch through the command that matches the operation risk class.
| Count | Value |
|---|---|
| Family | Workspace communication |
| Operations | 6 |
| Risk classes | 5 read, 1 write |
| Auth strategies | 6 byo_oauth |
Start here
gum search "meet"
gum describe meet.conferenceRecords.get
gum read meet.conferenceRecords.get --args '{"name":"<name>"}' --output jsonFor write-class operations, gum requires the write command and an explicit write gate:
gum describe meet.spaces.create
gum write meet.spaces.create --allow-write --args '{"fields":"id"}'Operations
| Operation | Risk | Auth | Summary |
|---|---|---|---|
meet.conferenceRecords.get |
read |
byo_oauth |
Fetch a conference record by resource name (conferenceRecords/<id>). |
meet.conferenceRecords.list |
read |
byo_oauth |
List past conference records for meetings the caller organized (filter, pageSize). |
meet.conferenceRecords.recordings.list |
read |
byo_oauth |
List the recordings of a conference record (parent=conferenceRecords/<id>). |
meet.conferenceRecords.transcripts.list |
read |
byo_oauth |
List the transcripts of a conference record (parent=conferenceRecords/<id>). |
meet.spaces.create |
write |
byo_oauth |
Create a new Meet meeting space; returns the meetingUri + space name. |
meet.spaces.get |
read |
byo_oauth |
Fetch a meeting space by resource name (spaces/<id>) or meeting code. |
Next
- Use API workflows for search, describe, invoke, and error handling.
- Use Auth guides for service-specific Google setup.
- Use Command index for CLI flags and generated help.
