---
title: "Connect DocuPipe and Quo - APIANT.ai"
description: "When \"Document Processed\" fires in DocuPipe, your agent runs \"Add contact\" in Quo, or \"List Phone Numbers\" in Quo to \"Upload Document\" in DocuPipe."
canonical: "https://apiant.ai/connect/docupipe-to-quo"
---

# Connect DocuPipe and Quo

When **Document Processed** fires in [DocuPipe](https://apiant.ai/connections/docupipe), your agent runs **Add contact** in [Quo](https://apiant.ai/connections/quo), or **List Phone Numbers** in Quo to **Upload Document** in DocuPipe. Describe the whole flow and it is built, tested on every scenario and kept running.

DocuPipe **1** trigger DocuPipe **15** actions Quo **1** trigger Quo **21** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want DocuPipe and Quo to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What DocuPipe and Quo can do together

### From DocuPipe to Quo

- When **Document Processed** in DocuPipe then **Add contact** in Quo
- When **Document Processed** in DocuPipe then **Add task** in Quo

### From Quo to DocuPipe

- When **List Phone Numbers** in Quo then **Upload Document** in DocuPipe
- When **List Phone Numbers** in Quo then **Analyze document** in DocuPipe

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with DocuPipe and Quo

## Triggers and actions 2 triggers · 36 actions

- Trigger

**Document Processed**

Triggers when a document finishes parsing and OCR is complete.

- Action

**Add schema**

Creates a new extraction schema in DocuPipe from a JSON schema you supply, and returns its schema ID.

- Action

**Analyze document**

Asks DocuPipe a list of plain-language questions about one document and starts the analysis, returning the analysis ID to fetch the answers with.

- Action

**Classify Document**

Sends one or more documents to DocuPipe to be sorted into your classes, and returns the job that is doing the work.

- Action

**Delete document**

Removes a document from your DocuPipe account.

- Action

**Delete schema**

Removes an extraction schema from your DocuPipe account.

- Action

**Extract Data From Document**

Pulls structured data out of a document using one of your schemas, and returns the extraction to fetch the results with.

- Action

**Find documents by criteria**

Finds documents in your DocuPipe account whose file name or document ID matches what you search for.

- Action

**Get Document**

Returns one document from your DocuPipe account, with its file details, processing status, parsed text and your own metadata.

- Action

**Get Extraction Result**

Returns the data DocuPipe pulled out of a document, shaped by the schema that was used, along with per-field confidence details.

- Action

**Get schema**

Returns one extraction schema from your DocuPipe account, including the JSON schema it applies and its guidelines.

- Action

**List documents**

Returns the documents in your DocuPipe account, optionally narrowed to one dataset or a date range.

- Action

**List extractions**

Returns the data extractions in your DocuPipe account, optionally narrowed to one schema, one document, or a specific set of extractions.

- Action

**List schemas**

Returns the extraction schemas in your DocuPipe account.

- Action

**Upload and Extract Data**

Sends a file to DocuPipe and immediately starts pulling structured data out of it, returning both the new document and the extraction.

- Action

**Upload Document**

Sends a file to DocuPipe to be read and turned into a document you can extract data from.

- Trigger

**List Phone Numbers**

Triggers when a new phone number is added to your Quo workspace.

- Action

**Add contact**

Adds a new contact to your Quo workspace, with name, company, role, emails, phone numbers and custom field values.

- Action

**Add task**

Creates a task in Quo linked to a phone number, a conversation, or a conversation activity, optionally with a due date and an assigned user.

- Action

**Delete contact**

Deletes a contact from your Quo workspace.

- Action

**Get a Message by ID**

Returns a single text message by its ID, including its sender, recipients, content, direction, delivery status and any attached media.

- Action

**Get a Summary for a Call**

Returns the AI-generated summary of a call, including key points discussed, suggested next steps, and any Sona job results. Call summaries are available on Business and Scale plans.

- Action

**Get a Transcription for a Call**

Returns the transcript of a call, including each spoken segment with its speaker and timing. Transcripts are available on Quo Business and Scale plans.

- Action

**Get call**

Returns a single Quo call by its ID, including its direction, status, participants, duration and timestamps.

- Action

**Get contact**

Returns a single Quo contact by its ID, including name, company, role, phone numbers, emails and custom field values.

- Action

**Get phone number**

Returns one of your Quo phone numbers, including its display name, number, forwarding setting, assigned users and calling/messaging restrictions.

- Action

**Get Recordings for a Call**

Returns the recordings for a call, oldest segment first, with each recording's status, duration, file type and download URL.

- Action

**Get user**

Returns a user in your Quo workspace, including their name, email, role and profile picture.

- Action

**Get voicemail for a call**

Returns the voicemail left on a call, including its status, length, transcript and a link to the audio. Fields stay blank while the voicemail is still processing.

- Action

**List Calls**

Returns the calls between one of your Quo numbers and a specific external phone number, optionally limited to a date range.

- Action

**List contacts**

Returns the contacts in your Quo workspace, optionally limited to contacts with specific external IDs or sources.

- Action

**List Conversations**

Returns the conversations in your Quo workspace, newest activity first, optionally narrowed to specific Quo numbers, a user's access, or a created/updated date range.

- Action

**List Messages**

Returns the text messages exchanged between one of your Quo numbers and the given participants, newest first, optionally filtered by sender and date range.

- Action

**List Phone Numbers**

Returns the phone numbers in your Quo workspace along with the users who have access to each, optionally limited to one user's numbers.

- Action

**List tasks**

Returns the tasks in your Quo workspace, including title, description, due date, assignee and completion status.

- Action

**List users**

Returns every user in your Quo workspace, with their email, name, role and picture.

- Action

**Send a Message**

Sends a text message from one of your Quo phone numbers to up to 10 recipients.

- Action

**Update contact**

Updates an existing Quo contact's name, company, role, emails, phone numbers and custom fields. Fields you leave blank keep their current values.

## Each app on its own

- [ **DocuPipe** DocuPipe is a service that turns PDFs, images, and scanned documents into structured JSON data.](https://apiant.ai/connections/docupipe)
- [ **Quo** Quo is a next-generation phone system to engage customers, collaborate with your team, and scale your reach...](https://apiant.ai/connections/quo)

Reviews

## What our customers say

## More from DocuPipe

- [ **DocuPipe to Publora** Publish and schedule posts to ten social networks from one endpoint](https://apiant.ai/connect/docupipe-to-publora)
- [ **DocuPipe to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/docupipe-to-hubspot)
- [ **DocuPipe to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/docupipe-to-salesforce)
- [ **DocuPipe to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/docupipe-to-slack)
- [ **DocuPipe to Google Sheets** Google Sheets](https://apiant.ai/connect/docupipe-to-google-sheets)
- [ **DocuPipe to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/docupipe-to-gmail)

## More into Quo

- [ **HubSpot to Quo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-quo)
- [ **Google Sheets to Quo** Google Sheets](https://apiant.ai/connect/google-sheets-to-quo)
- [ **Gmail to Quo** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-quo)
- [ **Google Calendar to Quo** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-quo)
- [ **Google Drive to Quo** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-quo)
- [ **Mailchimp to Quo** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-quo)

Questions

## DocuPipe and Quo, answered

###

### What can start an automation from DocuPipe?

Any of DocuPipe's 1 trigger in the catalog, including Document Processed. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Quo when something happens in DocuPipe?

Any of Quo's 21 actions, including Send a Message, Update contact, Add contact and Add task. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Quo to DocuPipe?

Yes. When something happens in Quo, your agent can act in DocuPipe too. This page covers both directions: Quo's triggers and DocuPipe's actions are listed here as well.

###

### Do I have to build a connector for DocuPipe or Quo?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use DocuPipe and Quo without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
