Quo
for LuumenAI

Read call and message history in Quo, then send or file follow-ups on approval

Connect Quo and your on-call work gets the phone side of the story. Luumen reads calls, voicemails, transcripts, messages, contacts, and tasks to answer questions right away. When something has to change — a text to a vendor, a task assigned, a conversation marked done — it shows the exact action first and waits for your approval. Authentication is by API key.

The Quo toolbox

36 tools: 20 read, 16 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet CallGet one call and its routing, participants, status, and timing details by ID.
  • ReadGet Call VoicemailGet voicemail processing status, transcript, duration, and recording URL for a Quo call.
  • ReadGet ContactGet one contact with default and custom fields by Quo contact ID.
  • ReadGet MessageGet one message by Quo message ID, including its content, related IDs, participants, delivery status, and timestamps.
  • ReadGet Phone NumberGet one Quo phone number and its assignments and restrictions by ID.
  • ReadGet TaskGet one task and its current links, assignee, due date, and completion state.
  • ReadGet UserGet one workspace user by Quo user ID.
  • ReadGet WebhookGet one unified Quo webhook by its numeric ID.
  • ReadGet Webhook DeliveryGet the payload and attempt details for one Quo webhook delivery event.
  • ReadList Call RecordingsList recording segments for a Quo call in chronological order.
  • ReadList CallsList calls between a Quo number and one external participant with optional user and creation-time filters.
  • ReadList Contact Custom FieldsList the workspace's contact custom-field definitions for constructing valid contact values.
  • ReadList ContactsList contacts, optionally filtered by external IDs or source, with stable-v1 phone and custom fields.
  • ReadList ConversationsList inbox conversations with optional phone-number, user, creation-time, update-time, and inactive-state filters.
  • ReadList MessagesList messages exchanged by a Quo phone number and one or more participants, optionally filtered by sender or creation time.
  • ReadList Phone NumbersList Quo phone numbers and their assigned users, calling restrictions, and messaging restrictions.
  • ReadList TasksList workspace tasks with cursor-controlled pagination.
  • ReadList UsersList workspace users and return one cursor-controlled page.
  • ReadList Webhook DeliveriesList one page of delivery events for a unified Quo webhook, optionally filtered by status, event type, or dispatch time.
  • ReadList WebhooksList unified Quo webhooks across call, message, contact, task, and integration event families.
  • WriteCreate ContactCreate a Quo contact with standard fields, optional custom fields, and external source metadata. Approval by default
  • WriteCreate TaskCreate a task linked to exactly one phone number, conversation, or activity. Approval by default
  • WriteCreate WebhookCreate one unified webhook subscription for selected Quo events and return its signing secret, which must be stored securely. Approval by default
  • WriteDelete ContactPermanently delete one Quo contact by ID. Approval by default
  • WriteDelete TaskPermanently delete one Quo task by ID. Approval by default
  • WriteDelete WebhookPermanently delete one unified Quo webhook and revoke its signing secret. Approval by default
  • WriteSend MessageSend an irreversible text message from a Quo number to one or more recipients. Approval by default
  • WriteSend Message and Mark Conversation DoneSend an irreversible text message from a Quo number and move the resulting inbox conversation to Done. Approval by default
  • WriteSet Conversation StatusSet a Quo conversation to read, done, or open. Approval by default
  • WriteSet Task AssigneeAssign or unassign a Quo user on a task. Approval by default
  • WriteSet Task CompletionComplete or reopen a Quo task. Approval by default
  • WriteSet Task Conversation LinkLink or unlink a Quo task and conversation. Approval by default
  • WriteSet Task Due DateSet or remove a Quo task's due date. Approval by default
  • WriteUpdate ContactPatch selected standard, custom, or source fields on an existing Quo contact. Approval by default
  • WriteUpdate TaskReplace both the title and description of an existing Quo task. Approval by default
  • WriteUpdate WebhookPartially update a unified Quo webhook. Approval by default

One prompt, start to finish

What a governed Quo run looks like inside Luumen.

Questions

How does LuumenAI connect to Quo?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Quo on its own?

Read actions answer immediately. Anything that writes — create contact, create task, create webhook, delete contact, and more — is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Quo — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Quo to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.