Create, update, and delete follow-up tasks (action items) tied to meetings. Use this for action-item lifecycle; to manage the parent meeting, agenda, or participants, use those dedicated tools. Set `action` to one of: create, delete, update. Then provide the fields for the selected action. action=create: Add a follow-up task to a meeting. Use this when the user wants to track work that came out of a meeting. Creates a follow-up action item in an accessible meeting. `meeting_id` and `title` are required; unknown `meeting_id` returns 404. Optional `status` must be one of `needs_review`, `accepted`, `in_progress`, `blocked`, `completed`, `cancelled`. The 201 body returns the `id` for v1UpdateActionItem or v1DeleteActionItem. Idempotent with `Idempotency-Key`; blind retries can duplicate without it. action=delete: Remove a follow-up task. Use this when the user wants to delete an action item. Soft-deletes an action item keyed by `{id}`. Returns 204 with no body. Unknown or inaccessible ids return 404. The call is effectively idempotent: a second delete of the same id also 404s, so retries are safe. action=update: Change a follow-up task's status or details. Use this when the user wants to update an action item. Partial update (PATCH) — only send fields to change. `status` drives a state machine, so set it explicitly rather than inferring from `is_completed`. This call does NOT honor `Idempotency-Key`; a blind retry may apply the same change twice. Returns 404 for an unknown or inaccessible id.
manageActionItemsCreate, update, and delete follow-up tasks (action items) tied to meetings. Use this for action-item lifecycle; to manage the parent meeting, agenda, or participants, use those dedicated tools.
Set action to one of: create, delete, update. Then provide the fields for the selected action.
action=create: Add a follow-up task to a meeting. Use this when the user wants to track work that came out of a meeting.
Creates a follow-up action item in an accessible meeting. meeting_id and
title are required; unknown meeting_id returns 404. Optional status must
be one of needs_review, accepted, in_progress, blocked, completed,
cancelled. The 201 body returns the id for v1UpdateActionItem or
v1DeleteActionItem. Idempotent with Idempotency-Key; blind retries can
duplicate without it.
action=delete: Remove a follow-up task. Use this when the user wants to delete an action item.
Soft-deletes an action item keyed by {id}. Returns 204 with no body. Unknown or inaccessible ids return 404. The call is effectively idempotent: a second delete of the same id also 404s, so retries are safe.
action=update: Change a follow-up task's status or details. Use this when the user wants to update an action item.
Partial update (PATCH) — only send fields to change. status drives a state machine, so set it explicitly rather than inferring from is_completed. This call does NOT honor Idempotency-Key; a blind retry may apply the same change twice. Returns 404 for an unknown or inaccessible id.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Action Item ID | |
| title | No | Short summary of the work to be done (1-1000 characters) | |
| action | Yes | The operation to perform | |
| status | No | Workflow status: needs_review, accepted, in_progress, blocked, completed or cancelled. Defaults to needs_review | |
| due_date | No | Date the action item is due, as YYYY-MM-DD | |
| meeting_id | No | ID of the meeting the action item belongs to | |
| description | No | Longer description of the action item, in Markdown (max 1000 characters) | |
| is_completed | No | Marks the action item completed (true) or reopens it (false); a convenience alias for status | |
| Idempotency-Key | No | Optional client-generated idempotency key (max 255 printable ASCII). Repeat requests with the same key replay the original 2xx response. | |
| assigned_to_name | No | Display name of an external assignee; only valid with assigned_to_email (max 255 characters) | |
| assigned_to_email | No | Email of the person to assign. A workspace member's email assigns that member; any other email assigns an external person and the item is created with status delegated (unless created completed or cancelled) | |
| assigned_to_user_id | No | Workspace member to assign. Omit both assigned_to_user_id and assigned_to_email to assign the authenticated user; sending both returns 400 |