--- title: "Documo Integration" description: "Connect AI agents to Documo mFax, the cloud fax service. Agents start a flow the moment a fax arrives with its PDF already in file storage, send documents as faxes with a cover page, and look up or download any sent or received fax." url: https://flowrunner.ai/integrations/documo date_modified: 2026-10-28T13:47:16-07:00 --- # Documo [Communication](https://flowrunner.ai/integrations/category/communication-messaging) Connect AI agents to Documo mFax, the cloud fax service. Agents start a flow the moment a fax arrives with its PDF already in file storage, send documents as faxes with a cover page, and look up or download any sent or received fax. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 4 actions · API key · available [Documo website](https://www.documo.com/) · [Platform Documentation](https://docs.documo.com/) · Capability data verified 2026-11-13 1. On New Inbound Fax fires with the PDF already saved 2. Agent reads the cover sheet to classify the fax 3. A missing PDF is fetched again with Download Fax 4. Referral matched to the patient chart and filed in the EHR 5. Intake team told who sent it, what it is and how many pages 6. Anything the agent cannot classify goes to the intake lead ## What This Integration Enables Documo is where a fax line stops being a machine in the corner and becomes the start of a flow. When a fax lands, the trigger fires with the fax record and its PDF already saved to FlowRunner file storage. Nobody prints it, nobody downloads it. The agent opens the document, works out what it is, and sends it to the team or the system that handles that kind of paper. That matters most where the paper is still the process. Referral offices, pharmacies and freight carriers fax because the other side reliably accepts it. FlowRunner agents read each inbound fax, route it, and send faxes back with Send Fax, then follow delivery with Get Fax and List Faxes. The trigger can be scoped to one receiving number or one outcome, so a clinic's intake line and an AP line each run their own flow. The agent handles the sorting. When a page is unclear or a reply is about to go out, it stops and asks a person on Slack, email, WhatsApp or phone. ### Without FlowRunner **Faxes printed and sorted**: Incoming pages pile up on one machine or one inbox and someone sorts them by reading each one **Routing by memory**: Whether a fax is a referral, a records request or an invoice depends on who picks it up **Replies keyed by hand**: Return faxes go out with a number typed from the cover sheet ### With FlowRunner **Each fax starts a flow**: The fax arrives as an event with its PDF saved, ready for an agent to read **Routed by what it says**: Referrals, records requests and invoices go to the team and system that handle them **Replies confirmed first**: A return fax goes out only after a person confirms where it is going ## Use Case Scenarios ### Clinic fax intake A referral arrives on the clinic's intake line and On New Inbound Fax fires with the PDF attached. The agent reads the cover sheet and the first pages and classifies the fax: new referral, records request, prior authorization paperwork, or something else. For a referral it calls Search Patients in [Healthie](https://flowrunner.ai/integrations/healthie), creates the patient when there is no match, and files the PDF with Upload Document to Patient Chart. A records request goes to the records queue instead. Anything the agent cannot place with confidence goes to the intake lead as an [automation exception](https://flowrunner.ai/concepts/automation-exceptions), with the PDF and the agent's best reading of it. ### An AP fax line kept separate A distributor still receives proofs of delivery and invoices by fax. A second flow runs the same trigger scoped to the AP number, so it never sees the clinic's faxes. Each PDF goes to [Parseur](https://flowrunner.ai/integrations/parseur) for field extraction, and the extracted invoice number, amount and sender are logged with Add Row in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). When the trigger's file is empty because the PDF could not be fetched, the agent retries with Download Fax using the message ID from the event, rather than dropping the document. ### Sending and following up When a signed form is ready, the agent calls Send Fax with the file URLs in page order and an optional cover page. The fax starts as processing, so the agent checks Get Fax until the result code settles. A morning flow calls List Faxes filtered to failed outbound faxes and posts the list to the team. Documo allows 8 fax history requests per minute, so the report flow pages through results at that pace instead of failing halfway. ## Human-in-Loop Highlight The gate is on the reply number, because this connector has no way to call a fax back. Send Fax is the only outbound action, and the connector offers no cancel. When a records request arrives, the agent assembles the documents and drafts the return fax. The obvious destination is the sender's number from the inbound event, but the CSID is whatever text someone typed into the sending machine. It often belongs to a hospital's central fax server rather than the requesting office. So the agent posts to the records channel: "Records request from 'MERCY ORTHO' for patient chart 5521, 9 pages ready. Caller ID is +1 312 555 0142, the cover sheet asks for replies to +1 312 555 0177. Which number do I send to?" The records lead answers, and only then does Send Fax run. This is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) on the one step that cannot be undone, with the evidence for both numbers in front of the person deciding. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 4 actions ### Faxes 4 - **Send Fax** Sends one or more files as a fax to a fax number, with an optional cover page. Files are given as URLs, such as FlowRunner file links from an earlier step, and are faxed in the order listed. Returns the new fax record and its message ID. - **Get Fax** Reads a sent or received fax: status, result code, pages, numbers, timing, tags and users. Used to follow an outbound fax until delivery finishes, where a result code of 0 means delivered. - **List Faxes** Lists the account's fax history, received faxes by default, one page at a time. Filters cover direction, status, creation date and a search term. Used for daily reports on failed deliveries and for catching up on a backlog. - **Download Fax** Downloads a fax's document as PDF or TIFF into FlowRunner file storage and returns the file's URL, name and size. Used when the trigger's PDF could not be fetched, and to pull older faxes into a flow. ## Triggers 1 triggers ### Event Triggers 1 - **On New Inbound Fax** Fires when Documo finishes receiving a fax. The event carries the fax record, including message ID, status, fax number, caller ID, CSID and pages, and for a successful fax its PDF saved to FlowRunner file storage. It starts intake, routing and archiving flows. It can be limited to one receiving number or one outcome, and when the PDF is missing the event says why. ## Frequently asked questions ### What can FlowRunner do with Documo? FlowRunner agents can run Send Fax, Get Fax, and List Faxes in Documo, plus 1 more action. ### Does connecting Documo to FlowRunner require OAuth? No. Documo connects to FlowRunner with an API key, no OAuth flow required. ### Can Documo trigger a FlowRunner workflow automatically? Yes. Documo supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Documo?** This integration exposes Documo to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. ## Need a custom Documo automation? Our team can build it for you. Tell us the process. Our implementation team at Midnight Flow builds it around how you work, tests it on your real data, and keeps it running, in your own FlowRunner workspace. [Have us build it](https://midnightflow.ai/packages/custom?utm_source=flowrunner.ai&utm_medium=referral&utm_campaign=general&utm_content=integrations.aside&utm_term=documo) --- Markdown version of https://flowrunner.ai/integrations/documo. Site index: https://flowrunner.ai/llms.txt