Quo, formerly OpenPhone, is a business phone platform for managing calls, messages, contacts, conversations, tasks, users, and webhooks.
Assign an existing workspace task to a user. Supply the task ID and user ID; returns the task ID and revision number. Uses POST /tasks/{taskId}/users with Quo-Api-Version 2026-03-30, the new workspace API counterpart to the legacy /v1 task assignee API.
Create the organization's A2P (10DLC) draft registration with business and contact details and message types for autofill. This does not submit the draft for carrier approval. An organization can have at most one registration; Quo returns 409 if one already exists.
Create a Quo contact with standard fields, optional custom fields, and external source metadata.
Add a note to a Quo workspace contact using POST /contacts/{contactId}/notes with Quo-Api-Version 2026-03-30. Supply a contact ID and 1–2000 characters of text. Mentions using @USxxx, @GRxxx or @ORxxx are automatically detected and resolved. Returns the created note, its attachments and author.
Add a property to a Quo workspace contact using POST /contacts/{contactId}/properties with Quo-Api-Version 2026-03-30. Supply the contact ID, property type and a non-null value; optionally supply a label. Returns the created property and timestamps. This versioned workspace contact API differs from the legacy /v1 contact custom-fields API.
Create a legacy v1 Quo webhook for call.summary.completed events and return its configuration and webhook key. Optionally filter by phone number IDs and select the creating user; omission uses the workspace owner. Uses the legacy /v1 API rather than the versioned workspace webhook API.
Create a legacy v1 Quo webhook for call.transcript.completed events and return its configuration and webhook key. Supply a callback URL and events; optionally select phone number IDs, creating user, label, and status. Uses POST /v1/webhooks/call-transcripts rather than the versioned workspace webhook API. If the creating user is omitted, defaults to the workspace owner.
Create a legacy v1 Quo webhook for call.completed, call.ringing, or call.recording.completed events. Supply a destination URL and events; optionally select phone numbers, creating user, label, and status. Uses POST /v1/webhooks/calls rather than the versioned workspace webhooks API. Returns the created webhook configuration and key.
Create a legacy v1 Quo webhook for message.received and/or message.delivered events. Supply a callback URL and event list, with optional phone-number filters, label, status and creator. Uses POST /v1/webhooks/messages without the workspace API version header. Returns the created webhook and its key.
Create a task linked to exactly one phone number, conversation, or activity.
Create one unified webhook subscription for selected Quo events and return its signing secret, which must be stored securely.
Create a contact in the Quo workspace using POST /contacts with Quo-Api-Version 2026-03-30, rather than the legacy /v1 contacts API. Requires a first name and optionally accepts company, role, source, external ID and attribution. Quo returns 409 if the source and external ID already identify an existing contact.
Create a Quo workspace task, optionally linked to a conversation, using POST /tasks with Quo-Api-Version 2026-03-30, rather than the legacy /v1 tasks API. Supply a title and description; omit conversation_id for an org-wide task visible to every organization member. Optionally set a conversation ID, due timestamp and assigned user. Returns the task ID and revision. Quo returns 402 if the open-task limit is reached.
Permanently delete one Quo contact by ID.
Delete a note from a Quo workspace contact by its contact ID and note ID. Uses DELETE /contacts/{contactId}/notes/{noteId} with Quo-Api-Version 2026-03-30. Returns an empty object on the documented 204 No Content success.
Delete a property from a Quo workspace contact by its contact ID and property ID. Uses DELETE /contacts/{contactId}/properties/{propertyId} with Quo-Api-Version 2026-03-30. Returns an empty object on the documented 204 No Content success.
Delete a legacy v1 Quo webhook by its WH-prefixed ID. Uses DELETE /v1/webhooks/{id} rather than the versioned workspace API. Returns an empty object on the documented 204 No Content success.
Permanently delete one Quo task by ID.
Permanently delete one unified Quo webhook and revoke its signing secret.
Delete a contact from your Quo workspace by its unique contact ID. Uses DELETE /contacts/{contactId} with Quo-Api-Version 2026-03-30, rather than the legacy /v1 contact API. Returns an empty object on the documented 204 No Content success.
Delete a workspace task by its task ID. Uses DELETE /tasks/{taskId} with Quo-Api-Version 2026-03-30 rather than the legacy /v1 task API. Returns an empty object on the documented 204 No Content success. The provider does not document whether this is equivalent to setting status=deleted through the task status endpoint or can be restored.
Delete the due date of a Quo workspace task using DELETE /tasks/{taskId}/due-date with Quo-Api-Version 2026-03-30. This uses the new workspace API rather than the legacy /v1 task API. Supply the task ID. Removes the due date without deleting the task. Returns the task ID and revision.
Get the organization's A2P (10DLC) registration. Organizations have at most one registration. Returns a 404 rather than a null data field when no registration exists yet.
Get one call and its routing, participants, status, and timing details by ID.
Get the summary, suggested next steps, and processing status of a Quo call, including structured job results for calls handled by Sona. Call summaries are only available on Business and Scale plans.
Get a detailed transcript and processing status for a Quo call, including speaker identifiers and segment timing. Supports regular calls and calls handled by Sona. Call transcripts are only available on Business and Scale plans.
Get voicemail processing status, transcript, duration, and recording URL for a Quo call. Returns a not-found error when the call has no voicemail.
Get one contact with default and custom fields by Quo contact ID.
Retrieve a single contact note by contact_id and note_id, including its text, attachments, timestamps and author ID. Uses GET /contacts/{contactId}/notes/{noteId} with Quo API version 2026-03-30.
Retrieve a single contact property by contact_id and property_id, including its type, label, value and timestamps. Uses GET /contacts/{contactId}/properties/{propertyId} with Quo API version 2026-03-30. This versioned workspace contact API differs from the legacy /v1 contact custom-fields API.
Get a legacy v1 Quo webhook by its WH-prefixed ID, including its status, destination URL, key, event subscriptions, and resource IDs. Uses the legacy /v1 API rather than the versioned workspace API.
Get one message by Quo message ID, including its content, related IDs, participants, delivery status, and timestamps.
Retrieve the Quo workspace organization associated with the connected API key, including its name, subscription status, and creation and update timestamps. Uses GET /organization with Quo-Api-Version 2026-03-30. No organization ID or other parameters are needed.
Get one Quo phone number and its assignments and restrictions by ID.
Retrieve automatic call recording and inbound/outbound recording disclosure settings for a Quo workspace phone number by ID. Uses GET /phone-numbers/{phoneNumberId}/settings with Quo-Api-Version 2026-03-30 on the workspace API, rather than the legacy /v1 phone-number API. Returns the data envelope without changing any settings.
Get one task and its current links, assignee, due date, and completion state.
Get one workspace user by Quo user ID.
Get one unified Quo webhook by its numeric ID.
Get the payload and attempt details for one Quo webhook delivery event.
Get one workspace call by ID, optionally including its summary and voicemail. Uses GET /calls/{callId} with Quo-Api-Version 2026-03-30, rather than the legacy /v1 call API. Returns all call participants, including system actors.
Retrieve one contact in your Quo workspace by its unique contact ID. Uses GET /contacts/{contactId} with Quo-Api-Version 2026-03-30, rather than the legacy /v1 contact API. Returns the data envelope with contact identity, source, name, company, role, timestamps, and actor ID.
Get one workspace message by its ID, including attached media, delivery status, participants, conversation, and timestamps. Uses GET /messages/{messageId} with Quo-Api-Version 2026-03-30 rather than the legacy /v1 message API.
Retrieve a phone number in your Quo workspace by its ID, optionally including calling/messaging restrictions and business hours. Uses GET /phone-numbers/{phoneNumberId} with Quo-Api-Version 2026-03-30, rather than the legacy /v1 phone-number API. Returns the data envelope; assigned users are available from the separate phone-number users endpoint.
Using API 2026-03-30, get one task by ID, including links, assignment, due date, status, and integer revision. Uses GET /tasks/{taskId} with Quo-Api-Version 2026-03-30 rather than the legacy /v1 task API. Returns the documented data envelope; status is open, completed, or deleted.
Using API 2026-03-30, retrieve one user in your Quo workspace by user ID. Uses GET /users/{userId} with Quo-Api-Version 2026-03-30, rather than the legacy /v1/users/{userId} API. Returns the data envelope containing the user's profile, workspace role, and creation/update timestamps.
Link an existing workspace task to a conversation. Supply the task ID and conversation ID; returns the task ID and revision number. Uses POST /tasks/{taskId}/conversations with Quo-Api-Version 2026-03-30, the new workspace API counterpart to the legacy /v1 task conversation link API.
List recording segments for a Quo call in chronological order.
List one page of a Quo call's transcripts using API version 2026-03-30. Transcripts are ordered by recording start time ascending (oldest first). Paused and resumed calls may have multiple recordings and transcripts. Returns recording IDs and user or system actor IDs, unlike the legacy v1 GET_CALL_TRANSCRIPT action. Pass next_cursor as after to continue.
List calls between a Quo number and one external participant with optional user and creation-time filters. Returns one page and a cursor for the next.
List the workspace's contact custom-field definitions for constructing valid contact values.
List one page of a contact's notes, including text, attachments, timestamps and author IDs. Uses GET /contacts/{contactId}/notes with Quo API version 2026-03-30. Pass next_cursor as after with the same contact_id to retrieve the next page; a null next_cursor means there are no more notes.
List one page of a contact's properties, optionally filtered by type, including labels, values and timestamps. Uses GET /contacts/{contactId}/properties with Quo API version 2026-03-30. Pass next_cursor as after with the same contact_id and filters for the next page; null means no more pages. This versioned workspace contact API differs from the legacy /v1 contact custom-fields API.
List one page of shares for a workspace contact using GET /contacts/{contactId}/shares with Quo API version 2026-03-30. This versioned workspace-contact API is distinct from the stable /v1 contact API. Each share identifies a user, organization, or group and its creation timestamp. Pass next_cursor as after for the next page.
List contacts, optionally filtered by external IDs or source, with stable-v1 phone and custom fields. Returns one page and a cursor for the next page.
List inbox conversations with optional phone-number, user, creation-time, update-time, and inactive-state filters. Returns one page and a cursor for the next page.
List all legacy v1 Quo webhooks for a user via GET /v1/webhooks. Omit user_id to use the workspace owner. Returns the data envelope with WH-prefixed webhook IDs, creator, organization, key, event subscriptions, phone number filters, and timestamps. This legacy API sends no Quo-Api-Version header and differs from List Webhooks, which lists unified webhooks via /webhooks. The legacy endpoint has no pagination.
List messages exchanged by a Quo phone number and one or more participants, optionally filtered by sender or creation time. Returns one page and a cursor for the next page.
List one page of members assigned to a workspace phone number, ordered by user ID. Uses GET /phone-numbers/{phoneNumberId}/users with Quo API version 2026-03-30. This workspace API is distinct from the stable /v1 phone-number API. Returns each member's email, nullable names, organization role, and group ID. Pass next_cursor as after for the next page.
List Quo phone numbers and their assigned users, calling restrictions, and messaging restrictions.
List workspace tasks with cursor-controlled pagination.
List one page of workspace phone numbers assigned to a specific user. Uses GET /users/{userId}/phone-numbers with Quo API version 2026-03-30, distinct from the stable /v1 phone-number API. Optionally include regional calling and messaging restrictions. Assigned members use the separate phone-number users endpoint. Pass next_cursor as after for another page.
List workspace users and return one cursor-controlled page.
List one page of delivery events for a unified Quo webhook, optionally filtered by status, event type, or dispatch time.
List unified Quo webhooks across call, message, contact, task, and integration event families.
List one page of recordings for a Quo workspace call using the new-generation API (Quo-Api-Version: 2026-03-30), distinct from the v1 List Call Recordings action. Segments are sorted by startTime ascending (oldest first); pausing and resuming a call can produce several segments. Pass next_cursor as after to continue. Returns recording metadata and signed audio URLs, not audio files.
List one page of workspace calls, newest first, including group calls. Uses GET /calls with Quo API version 2026-03-30, unlike the /v1 one-to-one List Calls action. Every filter is optional. Participant filters match only originating/receiving numbers, not additional group parties. Include summaries or voicemails optionally. Pass next_cursor as after for another page.
List one page of workspace contacts using GET /contacts with Quo API version 2026-03-30. Unlike the stable /v1 List Contacts action, this version returns flat name, company, role and actor fields rather than defaultFields/customFields. Optionally filter by external ID or source, using equality or an any-of list for each. Pass next_cursor as after with the same filters to retrieve the next page.
List one page of the organization's workspace conversations, most recently created first by default. Uses GET /conversations with Quo API version 2026-03-30, unlike the /v1 List Conversations action. All filters are optional; filter by Quo number or creation/update time and choose a sort order. Pass next_cursor as after to retrieve another page.
List one page of the workspace's messages across all conversations, newest first. Uses GET /messages with Quo API version 2026-03-30, unlike the /v1 List Messages action that requires a phone number and conversation participants. All filters are optional. Recipient filters match the exact recipient set. Pass next_cursor as after to retrieve another page.
List one page of phone numbers in your Quo workspace. Uses GET /phone-numbers with Quo API version 2026-03-30, unlike the /v1 List Phone Numbers action. Optionally filter by an E.164 phone number and include regional calling and messaging restrictions. Assigned users are retrieved through the separate phone-number users endpoint. Pass next_cursor as after for another page.
List one page of workspace tasks using GET /tasks with Quo API version 2026-03-30, distinct from the legacy /v1 List Tasks action. All filters are optional. Pass next_cursor as after to retrieve another page.
Using API 2026-03-30, list one page of workspace users, including names, email addresses, roles, picture URLs, and creation/update timestamps. Uses GET /users with Quo API version 2026-03-30, unlike the /v1 List Users action. Pass next_cursor as after to retrieve another page.
Mark a workspace conversation as done, removing it from the inbox without sending a message. Returns the updated conversation. Uses POST /conversations/{conversationId}/mark-as-done with Quo-Api-Version 2026-03-30, rather than the legacy /v1 conversation status API.
Mark a Quo workspace conversation as open, returning it to the inbox without sending a message. Uses POST /conversations/{conversationId}/mark-as-open with Quo-Api-Version 2026-03-30 rather than the legacy /v1 conversation API. Returns the updated conversation.
Mark a Quo workspace conversation as read, clearing its unread indicator without sending a message. Returns the updated conversation in the data envelope. Uses POST /conversations/{conversationId}/mark-as-read with Quo-Api-Version 2026-03-30, rather than the legacy /v1 conversation API.
Attempt to re-deliver a message that previously failed to send. Only messages with a failed status and no permanent error code can be retried. Permanently failed messages and messages with an undelivered status cannot be retried. Returns an empty object when accepted; acceptance does not confirm delivery. Uses POST /messages/{messageId}/retry with Quo-Api-Version 2026-03-30.
Queue a new attempt for an existing Quo webhook delivery. The retry is processed asynchronously: acceptance does not mean the destination received it successfully. Use the delivery detail endpoint to inspect the new attempt. Pass the delivery id from the delivery list or webhook-id header, not the payload eventId. Returns an empty object on HTTP 202 Accepted. Uses POST /webhooks/{webhookId}/events/{deliveryId}/retry with Quo API version 2026-03-30.
Search for available Quo phone numbers by area code, substring, country, city, region, or toll-free status. Returns up to the requested limit in data.phoneNumbers; this endpoint does not expose a continuation token. Uses GET /phone-numbers/available with Quo-Api-Version 2026-03-30. Searches available numbers rather than listing existing workspace numbers.
Send an irreversible text message from a Quo number to one or more recipients. This consumes messaging credits and may require carrier registration.
Send an irreversible text message from a Quo number and move the resulting inbox conversation to Done. This consumes messaging credits and may require carrier registration.
Dispatch a canonical sample of the selected event type to an existing Quo webhook URL to validate the receiver. Returns the rendered sample payload for preview, not proof of successful delivery. Delivery is asynchronous; use the webhook delivery detail endpoint to inspect the attempt. The returned event ID is fixed sample data, not a per-delivery message ID. Uses POST /webhooks/{webhookId}/events/test with Quo-Api-Version 2026-03-30.
Dispatch a text message from a Quo phone number ID to 1–10 E.164 numbers or short codes; multiple recipients create a group message. This creates an irreversible message dispatch and can consume prepaid credits. Optionally set inbox_status='done' to move the conversation to Done; omission uses the default open inbox behavior. Returns an accepted message, not proof of delivery. Uses POST /messages with Quo-Api-Version 2026-03-30, rather than the legacy /v1 API.
Set a Quo conversation to read, done, or open.
Assign or unassign a Quo user on a task.
Complete or reopen a Quo task.
Link or unlink a Quo task and conversation.
Set or remove a Quo task's due date.
Submit the organization's A2P (10DLC) draft registration for carrier approval. Quo validates all fields, paid subscription status, draft state, and autofill completion before attempting payment; any payment outcome other than completed returns 402. Submission incurs carrier-registration charges: the documented one-time fee is $19.50 paid to the Carrier Registry, with recurring monthly fees of $1.50 for most businesses, $3 for non-profits, or $2 for sole proprietors. Resubmission after rejection costs $15; rejected or failed registrations require resubmission and re-trigger billing. Success returns the updated registration, not carrier approval: draft=false with status=pending means awaiting approval. Outbound texting to US numbers remains unavailable until approval. Requires acknowledgment that forbidden message topics will not be sent.
Unassign a user from a Quo workspace task using DELETE /tasks/{taskId}/users with Quo-Api-Version 2026-03-30. This uses the new workspace API rather than the legacy /v1 task API. Supply the task ID and the assigned user ID. Removes the assignment without deleting the task or user. Returns the task ID and revision.
Unlink a conversation from a Quo workspace task using DELETE /tasks/{taskId}/conversations with Quo-Api-Version 2026-03-30. This uses the new workspace API rather than the legacy /v1 task API. Supply the task ID and the linked conversation ID. Removes their link without deleting the task or conversation. Returns the task ID and revision.
Merge selected fields into the organization's existing A2P (10DLC) draft registration. Omitted fields, including nested fields, remain unchanged. Explicit null clears only alternate_name, ticker, exchange, or address.line2. Autofill-triggering fields require message_types. Returns 404 when no registration exists and 409 when it is no longer a draft. Does not submit the registration for carrier approval.
Patch selected standard, custom, or source fields on an existing Quo contact. Omitted fields remain unchanged; explicit null can clear individual fields, while null email, phone-number, or custom-field lists are sent as empty lists.
Update an existing Quo workspace contact note's text using PATCH /contacts/{contactId}/notes/{noteId} with Quo-Api-Version 2026-03-30. Supply the contact ID, note ID, and replacement text of 1–2000 characters. Returns the updated note, attachments, timestamps and author.
Update an existing Quo workspace contact property's label, value, or both using PATCH /contacts/{contactId}/properties/{propertyId} with Quo-Api-Version 2026-03-30. Supply contact_id, property_id and at least one of name or value; omitted fields remain unchanged and explicit nulls are sent to the provider. Returns the updated property with its type and timestamps. This workspace properties API differs from the legacy /v1 contact custom-fields API.
Update a workspace phone number's display name and business hours using Quo's 2026-03-30 API (PATCH /phone-numbers/{phoneNumberId}, distinct from legacy /v1 phone-number reads). Provide at least one change. Omitted fields retain stored values; null schedule or day clears it. Returns the updated number in the data envelope. With user tokens, only owners and admins can update: assigned members receive 403 and unassigned users receive 404.
Update automatic call recording and inbound/outbound recording notifications for a workspace phone number using Quo's 2026-03-30 API (PATCH /phone-numbers/{phoneNumberId}/settings, distinct from legacy /v1 phone-number reads). Provide at least one setting; only supplied settings change. Null is not accepted. Returns updated settings in the data envelope.
Replace both the title and description of an existing Quo task. Both fields are required because Quo treats this as a full textual update.
Partially update a unified Quo webhook. Only explicitly supplied fields are changed; explicit null clears resource filters or the label where supported.
Update a workspace contact by ID using Quo's 2026-03-30 API generation (PATCH /contacts/{contactId}, distinct from the legacy /v1 contact API). Updates first/last name, company, role, and source metadata. Omitted fields remain unchanged; explicit null clears a field. Returns the updated contact in the data envelope.
Update a Quo workspace task's title and description using PATCH /tasks/{taskId} with Quo-Api-Version 2026-03-30. This is the new workspace API counterpart to the legacy /v1 task update. Supply the task ID and both title and description, as required by the versioned API schema. Returns the task ID and its revision number.
Update a Quo workspace task's due date using PATCH /tasks/{taskId}/due-date with Quo-Api-Version 2026-03-30. This is the new workspace API counterpart to the legacy /v1 task due-date operation. Supply a task ID and a non-null ISO 8601 date-time; this operation does not remove a due date. Returns the task ID and its revision number.
Set a Quo workspace task's status to completed, open, or deleted using PATCH /tasks/{taskId}/status with Quo-Api-Version 2026-03-30. This is the new workspace API status operation, distinct from legacy /v1 task completion actions. Requires a task ID and the desired status. Returns the task ID and its revision number. Setting deleted is a deletion-state transition; the provider does not document whether it is equivalent to DELETE /tasks/{taskId} or can be restored.
The Quo integration connects your Dench AI CRM directly to Quo, so agents can read and act on your Quo data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
102 actions are available for agents to invoke on your behalf. Every call runs through Quo's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Quo and click Connect — you'll authorize access through Quo's own sign-in flow. No API keys or code required.
Ask an agent to use Quo in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Quo integration connects your AI CRM to Quo, so AI agents can work with your Quo data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Quo integration currently exposes 102 actions, including Assign Workspace Task User, Create A2P Registration, Create Contact, Create Contact Note, Create Contact Property, and Create Legacy Call Summary Webhook. Agents invoke them on your behalf from chat or from automations.
No. You connect Quo from your Dench workspace using Quo's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Quo's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Quo connection from your workspace settings at any time.