Quo API (OpenPhone): What You Can Automate With Carly
Quo, formerly OpenPhone, records what happens on your business line: every call, text, voicemail, summary and transcript.
Its API, webhooks and MCP server let something else act on all of that the second it happens. That something can be Carly.
The quick answer: Connect Quo to Carly with Quo’s official MCP server or a Quo API key, then point Quo’s webhooks at a Carly workflow. From there, a missed call from a new number gets a text back and a booked meeting, every call summary and transcript lands on the right HubSpot, Salesforce or Pipedrive deal, a new lead’s first text becomes a contact, a deal and an owner, and your team gets a voicemail digest every morning. Quo’s API and MCP are on every Quo plan, and you can connect Quo on the Carly integrations page in a few minutes. If what you actually want is an AI that answers your line and calls new leads back on its own, that’s Carly Phone, and the Carly team sets it up with you.
Six Quo automations worth setting up
Each of these runs on a real Quo event or a schedule. None of them needs code.
1. A missed call from a new number gets a text back and a booked meeting
Josh runs Brightline Plumbing. A homeowner calls at 7:15pm, nobody picks up, and they don’t leave a voicemail. In Quo, that’s a missed call sitting in the inbox until morning, by which time they’ve called two other plumbers.
With Carly: Quo fires call.completed with an unanswered status. Carly checks the number against HubSpot, sees it’s new, and texts the caller from your Quo number within a minute: “Sorry we missed you, this is Brightline Plumbing. Is this about a repair quote? Emily has Thursday at 10am or 2pm open.” When they reply, Quo fires message.received, and Carly books the time on Emily’s real Google or Outlook calendar and sends the invite.
Quo’s API can’t place a phone call, so the follow-up here is a text. If you want an AI that calls the lead back, qualifies them and books them while they’re on the line, see Carly Phone on a call.
2. Every call summary and transcript lands on the CRM deal
Quo’s own CRM integrations log calls to records that already exist. With a Carly workflow on call.summary.completed and call.transcript.completed, you choose exactly where it goes and what it looks like:
- The summary and next steps are written as a note on the open deal, not just the contact
- The deal stage moves when the call says it should (“they approved the quote” moves it to Closed Won)
- Budget, timeline and decision-maker are pulled out of the transcript into the deal’s own fields
- The full transcript is attached in Salesforce, which Quo’s native Salesforce integration doesn’t sync
HubSpot, Salesforce and Pipedrive are all native Carly connectors, so the CRM side needs no setup beyond signing in.
3. A voicemail triage digest at 8am
Claire runs the front desk at a physical therapy clinic with three Quo numbers. Monday mornings start with 14 voicemails.
With Carly: a workflow runs every weekday at 8am. It pulls the previous day’s missed calls and voicemail transcripts from Quo, sorts them (new patient, reschedule, billing question, urgent), drafts a reply text for each, and emails Claire one list in priority order. She approves the texts she likes and they go out from the clinic’s Quo number.
4. A text from a new lead becomes a contact, a deal and an owner
When message.received arrives from a number that isn’t in your CRM, Carly:
- Reads the text and works out what they want
- Creates the contact in your CRM with the phone number and whatever they shared
- Opens a deal in the right pipeline
- Assigns an owner by your rule (territory, service line, or round-robin across the team)
- Creates a matching Quo contact and a Quo task for that owner, so the rep sees it in the inbox they already live in
Quo’s native HubSpot and Pipedrive integrations don’t create contacts or deals from Quo, which is why this one saves the most typing.
5. A follow-up email after every call
Quo has calls and texts but no email. Michael finishes a discovery call, Quo generates the summary a few minutes later, and Carly drafts the recap email in Michael’s Gmail or Outlook: what was discussed, the next steps from the summary, the proposal attached if one was promised, and a link to book the next meeting. It lands as a draft for Michael to send, or it sends on its own if you prefer.
6. A weekly call report in Slack
Every Friday at 4pm, Carly pulls the week from Quo and posts one message to your team channel:
- Calls answered, missed and handled by Sona, per number and per teammate
- Voicemails that still haven’t been returned
- The most common reasons people called, pulled from the summaries
- New leads that came in by phone or text and whether each one has a deal
Quo sends Slack notifications for individual texts, missed calls and voicemails. This is the rollup a manager actually reads.
| Automation | Quo trigger | What Carly does | Runs on |
|---|---|---|---|
| Missed-call text-back and booking | call.completed, message.received | Texts back, books the right teammate | Webhook |
| Summary and transcript to the deal | call.summary.completed, call.transcript.completed | Writes notes, updates fields and stage | Webhook |
| Voicemail digest | Missed calls and voicemails | Sorts, drafts replies, emails the list | Weekdays at 8am |
| New lead from a text | message.received | Creates contact, deal, owner and Quo task | Webhook |
| Follow-up email | call.summary.completed | Drafts the recap in Gmail or Outlook | Webhook |
| Weekly call report | The week’s calls and voicemails | Posts totals and open items to Slack | Fridays at 4pm |
Want the phone side automated too, with an AI that answers, qualifies and books on the call itself? Book a call with the Carly team.
How to connect Quo to Carly
There are two ways to give Carly access to Quo. Pick one.
Option A: Quo’s MCP server. In Carly, go to Integrations → MCP servers and add Quo’s server:
Carly opens Quo’s sign-in page, you approve access, and that’s the whole procedure. Carly acts as the Quo user who signed in and sees what that user can see.
Option B: a Quo API key. In Quo, a workspace owner or admin goes to Workspace Settings → API and creates a key. Name it “Carly” so you know which integration it belongs to. Paste your API key into Carly on the integrations page.
Then add the real-time trigger. For anything that should happen the moment a call ends or a text arrives:
- In Carly, create a workflow with a webhook trigger and copy its URL
- In Quo, go to Settings → Webhooks → Create webhook, paste the URL and pick the events (for example
call.completed,message.receivedorcall.summary.completed) - Use Quo’s “Send Test Request” to confirm the workflow fires
For the digest and the weekly report, skip the webhook and put the workflow on a schedule, such as every weekday at 8am. Carly’s workflows are free Zapier-style workflows with ready-made templates, and Carly connects to thousands of apps, so the other end (HubSpot, Salesforce, Pipedrive, Slack, Gmail, Outlook, Google Calendar) is already covered. Connect Quo here.
What Quo’s own integrations already cover
Search “OpenPhone HubSpot integration” and you’ll find Quo’s native connector, which is good at one job: logging. Here’s the line between what Quo does natively and what needs a workflow, per Quo’s help center as of September 2026.
| Quo native HubSpot / Pipedrive / Salesforce | Carly workflow on Quo events | |
|---|---|---|
| Log calls, texts, voicemails to the matching contact | Yes | Yes |
| Show on the associated deal | Yes, using existing associations only | Yes, and can move the stage |
| Create a contact or deal for a new number | No | Yes |
| Assign an owner | No | Yes, by your rules |
| Transcripts in Salesforce | No | Yes |
| Next steps in Salesforce | No, summary only | Yes |
| Follow-up email after the call | No | Yes |
If you’re weighing plans, our Quo pricing breakdown has the per-seat math, and the Quo review covers what users say about the rest of the product.
Quo API, webhooks and MCP: the reference
Everything below is from Quo’s developer docs as of September 2026.
Two API versions
| v1 | 2026-03-30 | |
|---|---|---|
| How it’s versioned | /v1 in the URL | Quo-Api-Version header, required on every request |
| Calls, recordings, summaries, transcripts, voicemails | Read | In development |
| Send and list texts | Yes (SMS only, up to 10 recipients) | Mostly in progress |
| Contacts | Create, read, update, delete | Plus properties, notes and shares |
| Tasks, users, conversation status | Yes | Yes |
| Webhooks | Legacy system | New system (below) |
Quo says v1 remains fully supported and new endpoints ship in the dated version. For anything touching calls today, v1 is the one.
Keys and limits. Keys are created in Workspace Settings → API by an owner or admin. Each key has full access to the workspace API, with no scopes, so give every integration its own key. The rate limit is 10 requests per second per key, with no daily quota.
Texting costs. Texts sent through the API, Zapier, Make or the MCP server cost $0.01 per segment from prepaid credits, even though the same texts sent from the Quo app are free. US numbers also need carrier registration before API texts deliver.
Webhooks
In Settings → Webhooks you can pick the events most workflows need: message.received, message.delivered, call.ringing, call.completed, call.recording.completed, call.summary.completed, call.transcript.completed, plus contact and task events.
Quo’s newer webhook system, created through the dated API, offers around 30 event types in total, including call.missed, call.answered, call.forwarded, call.voicemail.completed, call.menu.selected (which phone-menu option the caller pressed) and message.undelivered. It follows the Standard Webhooks format (the same one Svix uses), retries failed deliveries 8 times over about 27 and a half hours, and allows up to 50 webhooks per workspace. Events can arrive out of order, so a transcript may land before its summary.
A trimmed call.summary.completed payload:
{
"type": "call.summary.completed",
"data": {
"resource": {
"callId": "AC123",
"summary": ["Customer asked for pricing details."],
"nextSteps": ["Send follow-up email."],
"handledByAiAgent": false
},
"context": {
"phoneNumberId": "PN123",
"contacts": { "ids": ["CT123"], "lookupStatus": "matched" }
}
}
}A lookupStatus of none means Quo found no matching contact in Quo. Summaries and transcripts need Quo’s AI call summaries and transcription turned on.
The Quo MCP server
Quo hosts an official MCP server at https://mcp.quo.com/mcp. It signs in with OAuth, so there’s no key to paste, and it’s also listed as an official connector in Claude and ChatGPT. It has 16 tools:
- Workspace: list users, list inboxes
- Texts: fetch messages, send a text, send a group text (2 to 10 people), send bulk texts (2 to 40 separate messages)
- Calls: fetch call transcripts, fetch missed calls with voicemail transcripts and recordings
- Contacts: list, get, create, update
- Tasks: list, create, update
- Feedback: send product feedback to Quo
Reading is free. Sends use the same $0.01 per segment credits as the API. For the difference between Quo’s own AI features and what runs through MCP, see our Quo AI guide.
What the Quo API can’t do
Neither API version can:
- Place, transfer, hold or record a call
- Build or change call flows, phone menus, ring groups or business hours
- Buy, port or configure numbers
- Configure Sona, Quo’s AI agent
- Register your business for texting (A2P 10DLC)
- Send MMS or schedule a text
The first one matters most. If the goal is an AI that dials a new lead within minutes, qualifies them and books the meeting on the call, that has to be the phone system itself. Our AI outbound calling guide covers how that works, and our Quo phone system overview covers what Quo’s call routing does on its own. Carly Phone does it as part of Carly, and it’s priced on a short call. See Carly Phone on a call.
FAQ
Is the OpenPhone API the same as the Quo API?
Yes. OpenPhone renamed itself Quo in September 2025, and the API moved to Quo’s domain. Older OpenPhone tutorials still work for v1, though some point at the old api.openphone.com host.
Can the Quo API make outbound calls?
No. Neither version can place or control a call. The API reads calls after they happen and sends texts. For AI-placed calls to new leads, you need a phone system with an AI voice agent built in, such as Carly Phone.
What’s the difference between Quo’s MCP server and its API?
The MCP server is for an AI assistant working on your behalf: it signs in as you with OAuth and exposes 16 ready-made tools. The API is for scheduled or code-driven work with a key. Carly can use either one, and adds the triggers and schedules neither has on its own.
How do Quo webhooks connect to Carly?
Create a Carly workflow with a webhook trigger, copy its URL, then add it in Quo under Settings → Webhooks and pick the events you want. The workflow runs every time one of those events fires.
Does Quo integrate with HubSpot without Carly?
Yes. Quo’s native HubSpot integration logs calls, texts, recordings and summaries to matching HubSpot contacts and their deals. It doesn’t create contacts or deals, assign owners, or send follow-up email. Those are the parts a Carly workflow adds.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
