Create, update, and delete meetings in the workspace. Use this when the user wants to schedule, edit, or cancel a meeting. To manage participants, agenda/backlog items, or action items, use those dedicated tools. Set `action` to one of: create, delete, update. Then provide the fields for the selected action. action=create: Start a new meeting in the workspace. Use this when the user wants to schedule a meeting; the caller is added as owner automatically. Only `title` is required. `start_time` and `end_time` are optional ISO-8601; set `is_instant: true` for an ad-hoc meeting starting now. The caller is added as owner, so do not re-add them via v1AddMeetingParticipants. Pass `template_id` (from listMeetingTemplates) to seed the meeting from a template: the template is linked at create and applied asynchronously — the create response's `applied_template_ids` will not include it yet; poll v1GetMeeting until the id appears before treating the agenda as seeded. Returns 201 with the meeting `id`; use an `Idempotency-Key` to prevent duplicates. action=delete: Remove a meeting owned by the caller. Use this when the user wants to cancel or delete a meeting. Soft-deletes a meeting keyed by `{id}`; only the owner may delete it (403 for non-owners). Unknown or inaccessible ids return 404. Returns 204. The call is effectively idempotent: a repeat delete 404s, so retries are safe. action=update: Modify an existing meeting. Use this when the user wants to change a meeting's fields such as title or time. Partial update (PATCH) of a workspace-owned meeting. Omitted fields are left untouched. `start_time`/`end_time` are ISO-8601 with timezone; nulling start makes the meeting untimed and end open-ended. `end_time` must follow the effective start. `template_id` applies the template synchronously — its agenda items, participants, and prompts are added additively (existing content is preserved), and re-sending an id already in `applied_template_ids` is a no-op. Body must contain at least one field. 404/403/402/503 for unknown/inaccessible, no edit access, plan-gated `template_id`, or the template backend unavailable.
manageMeetingsCreate, update, and delete meetings in the workspace. Use this when the user wants to schedule, edit, or cancel a meeting. To manage participants, agenda/backlog items, or action items, use those dedicated tools.
Set action to one of: create, delete, update. Then provide the fields for the selected action.
action=create: Start a new meeting in the workspace. Use this when the user wants to schedule a meeting; the caller is added as owner automatically.
Only title is required. start_time and end_time are optional ISO-8601; set is_instant: true for an ad-hoc meeting starting now. The caller is added as owner, so do not re-add them via v1AddMeetingParticipants. Pass template_id (from listMeetingTemplates) to seed the meeting from a template: the template is linked at create and applied asynchronously — the create response's applied_template_ids will not include it yet; poll v1GetMeeting until the id appears before treating the agenda as seeded. Returns 201 with the meeting id; use an Idempotency-Key to prevent duplicates.
action=delete: Remove a meeting owned by the caller. Use this when the user wants to cancel or delete a meeting.
Soft-deletes a meeting keyed by {id}; only the owner may delete it (403 for non-owners). Unknown or inaccessible ids return 404. Returns 204. The call is effectively idempotent: a repeat delete 404s, so retries are safe.
action=update: Modify an existing meeting. Use this when the user wants to change a meeting's fields such as title or time.
Partial update (PATCH) of a workspace-owned meeting. Omitted fields are left
untouched. start_time/end_time are ISO-8601 with timezone; nulling start
makes the meeting untimed and end open-ended. end_time must follow the
effective start. template_id applies the template synchronously — its
agenda items, participants, and prompts are added additively (existing
content is preserved), and re-sending an id already in
applied_template_ids is a no-op. Body must contain at least one field.
404/403/402/503 for unknown/inaccessible, no edit access, plan-gated
template_id, or the template backend unavailable.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Meeting ID | |
| title | No | Meeting title (1-255 characters) | |
| action | Yes | The operation to perform | |
| end_time | No | Scheduled end, ISO 8601 with timezone; omit to leave the meeting open-ended | |
| is_instant | No | Creates the meeting as an instant (start-now) meeting rather than a scheduled one | |
| start_time | No | Scheduled start, ISO 8601 with timezone; omit to create an untimed meeting | |
| template_id | No | ID of the meeting template to apply (get ids from GET /v1/meeting-templates). On create the template is linked and applied asynchronously — poll `applied_template_ids` to confirm; on update it is applied synchronously, additively, and idempotently | |
| detail_level | No | Verbosity of the generated meeting summary: BULLET_POINTS, STANDARD or VERBATIM | |
| Idempotency-Key | No | Optional client-generated idempotency key (max 255 printable ASCII). Repeat requests with the same key replay the original 2xx response. |