# Create Task

`quo_create-task` · Quo MCP tool · Tasks

Create a task in the connected Quo account, linked to a phone number, conversation, or conversation activity. Provide exactly one of phoneNumberId, conversationId, or activityId.

## Quo Frequently Asked Questions

**What does the Create Task tool do?**

This page documents the Create Task tool (`quo_create-task`). Create a task in the connected Quo account, linked to a phone number, conversation, or conversation activity. Provide exactly one of phoneNumberId, conversationId, or activityId. It is one of the Quo Tasks tools, invoked through your firm's Weave MCP connection and available to members whose access level permits it.

**What is the Quo integration?**

The Quo integration connects your firm's Quo account to Weave. Quo is a cloud phone/SMS platform. This integration exposes calls, messages, contacts, conversations, and tasks as governed MCP tools, scoped per member by access level. It groups 36 tools into 6 categories, exposed through your firm's Weave MCP connection and filtered per member by access level.

**How does my firm connect Quo to Weave?**

An admin connects Quo once for the whole firm by entering your Quo workspace API key in the Weave console. Every member then works through that single connection; there is no per-user Quo login. Your key is encrypted at rest and stays inside Weave's infrastructure.

**Do I need to install or configure anything locally?**

No. Weave is fully hosted, so there is nothing to install, run, or maintain on your own machines. After an admin connects Quo once from the console, each member simply points their AI assistant at your firm's Weave MCP endpoint, and the tools they are allowed to use appear automatically based on their access level.

**Can everyone on my team use every tool?**

No. Tools are exposed per member by access level, so each person only sees the Quo tools their role permits.

**Are changes made through these tools reversible?**

Reads are always safe. Sending a text cannot be undone, once sent it can't be recalled, and it spends the workspace's prepaid SMS credits. Deletes are irreversible: delete-contact and delete-task permanently remove the record from Quo. Most other actions can be reversed with a follow-up tool (for example reopen-task or unassign-task).

**Why can't I send a text to a US number?**

Sending SMS to US numbers requires your Quo account to have completed US Carrier Registration. That is a Quo-side prerequisite; once it is done, send-message works for US recipients.

## Related
- /integrations/quo/tasks/assign-task/
- /integrations/quo/tasks/change-task-due-date/
- /integrations/quo/tasks/link-task-conversation/

## Input

- **title** `string` (required, min length: 1) — Title of the task.
- **description** `string` (required, min length: 1) — Description of the task.
- **phoneNumberId** `string` (min length: 1) — Internal identifier of the phone number to link this task to. Provide exactly one of phoneNumberId, conversationId, or activityId.
- **conversationId** `string` (min length: 1) — Internal identifier of the conversation to link this task to. Provide exactly one of phoneNumberId, conversationId, or activityId.
- **activityId** `string` (min length: 1) — Internal identifier of the conversation activity to link this task to. Provide exactly one of phoneNumberId, conversationId, or activityId.
- **dueDate** `string(date-time)` (pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$) — ISO 8601 due date/time for the task.
- **assignedTo** `string` (min length: 1) — Internal identifier of the user to assign the task to.

## Output

- **data** `object` (required) — The newly created task's identity and link.
  - **taskId** `string` (required) — Internal identifier of the newly created task.
  - **revision** `string` (required) — Revision identifier of the task.
  - **phoneNumberId** `string` — Internal identifier of the phone number the task resolves to — present both when the task was linked directly via phoneNumberId and when it was derived from a conversationId-linked task (live-verified 2026-09-03).
  - **conversationId** `string` — Internal identifier of the linked conversation, present when the task was linked via conversationId.
  - **activityId** `string` — Internal identifier of the linked conversation activity, present when the task was linked via activityId.