PDF Tools
DocumentsSplit, merge, inspect, create and fill in PDF forms inside FlowRunner with no API key, vendor account, or outbound call beyond fetching the file. Every new PDF lands in FlowRunner file storage, ready for the next step.
What This Integration Enables
PDF Tools is for the moment a document has the wrong shape for the system that needs it. One scan holds forty invoices, but the books want one file per bill. A payer wants its own fillable form, not your EHR's printout. A specialist wants one packet, not six attachments. These are not hard problems. They are steady, daily friction, and they usually end with someone opening a desktop PDF editor.
The work runs inside FlowRunner itself, with no API key, no vendor account, and no outbound call beyond fetching the file you point it at. A patient's prior authorization form is filled without being shipped to a third-party PDF service, and there is no per-page meter or expiring key in the flow. Agents split, merge, inspect, create and fill PDFs, and every new file lands in FlowRunner file storage with a URL the next step can use. Like any of FlowRunner's connectors, it does the mechanical part. When a form has changed under the agent, it stops and asks a person on Slack, email, WhatsApp or phone before anything leaves the building.
Without FlowRunner
With FlowRunner
Flows you can build with PDF Tools
-
Payer prior authorization form, filled from the chart
A visit that needs prior authorization is booked in Healthie. The agent reads the patient and the insurance policy on file. Get PDF Form Fields reads the payer's request form and returns every field's name, type, page, options and flags, so a dropdown is filled with one of its own options rather than free text. It also reports an XFA form, which cannot be filled here, so that case becomes an automation exception at once instead of a failure later. Fill PDF Form fills the text fields, checkboxes and radio groups. Every value is checked before anything is saved, and a name that is not a field of the form stops the step by default. Characters the form's standard font cannot show, such as a patient name in Cyrillic, also stop the step unless the flow chooses otherwise, so nothing is silently dropped from a name. The filled copy goes back to the chart with Upload Document to Patient Chart and out to the payer with Send Fax in Documo.
-
A scanned batch split into one PDF per invoice
The mailroom scans a morning's vendor invoices into one PDF, and it lands in Google Drive, firing On New File. Get PDF Info returns the page count and whether the file is password-protected, which PDF Tools cannot open. An extraction step reads where each invoice starts. Split PDF by Page Ranges then cuts one PDF per invoice, with ranges such as "1-2", "3" and "4-end". Every range is checked against the page count before any file is saved, so a bad range leaves no half-split batch behind. Each part is booked with Create Bill in QuickBooks Online, and Attach File to Bill puts the vendor's own pages on the bill they belong to. When the page count does not add up to the invoices found, the agent sends the batch to the AP lead in Slack instead of guessing where one invoice ends.
-
A records packet for a referring provider
A referring physician asks for an update. The agent pulls the chart notes from Healthie and an AI step in OpenAI drafts a summary letter. Create PDF from Text lays the letter out on Letter, A4 or Legal pages with a bold title, wrapping lines and adding pages as the text needs. Download Document saves the lab results and visit notes the request names. Merge PDFs combines the letter and the records in the order given, so the cover letter is always page one. The packet goes out as a single fax with Send Fax in Documo. For a records request that runs long, Split PDF Every N Pages breaks the packet into fixed-size parts.
Human-in-Loop Highlight
The gate is on Fill PDF Form with Flatten turned on, because flattening is the step that makes a mistake permanent in the copy that leaves. Flattening turns every field into plain page content, so the payer receives a form nobody can correct, and an unsigned signature field disappears from it entirely. The action checks every value it is given, but it cannot know about the fields it was not given. Payer forms name fields "Text12" and "Check Box3", and payers revise them. So before each fill, the agent compares Get PDF Form Fields with the field list the mapping was built on. When the form has changed, it fills a copy with Flatten off and asks the billing lead in Slack: "The payer's precertification form now has three fields our mapping does not fill: Text38 and Text39 on page 2, and a signature field on page 3. Here is the filled copy, unflattened. Fill the new fields, send it as is, or hold it for a provider signature?" The flattened copy is made only after the answer. This is human-in-the-loop on a form that changed under the agent, which is where a filled form goes wrong.
Agent Capabilities
7 actionsSplit and Merge
3- Split PDF by Page Ranges Splits a PDF into one new PDF per page range, such as "4", "1-3" or "5-end", and saves each one to FlowRunner file storage. Ranges may overlap, and every range is checked against the page count before any file is saved. Used to separate a scanned batch into one file per invoice, claim or form.
- Split PDF Every N Pages Splits a PDF into consecutive chunks of a fixed number of pages, with 1 giving one PDF per page. The last chunk holds whatever pages remain. Used when every document in a batch has the same length, or to break a long report into parts. A file with the same name in the chosen folder is replaced, so a rerun overwrites rather than duplicates.
- Merge PDFs Combines two or more PDFs into one, in the order given, and saves the result to FlowRunner file storage. Used to assemble a cover letter and its records, or a contract and its appendices, into the single file the recipient expects.
Inspect and Create
2- Get PDF Info Reads a PDF and returns its page count, the size and rotation of every page, its document properties such as title, author and dates, and whether it is password-protected. Nothing is saved. Used before a split, and to route a locked file to a person instead of failing on it.
- Create PDF from Text Lays out plain text as a PDF, with word wrapping, an optional bold title, and as many pages as the text needs, and saves it to FlowRunner file storage. Uses the standard PDF fonts, which cover Western European text, and the flow chooses whether other characters stop the step, are replaced or are left out. Used to turn a summary, a cover letter or a generated report into a document.
Forms
2- Get PDF Form Fields Lists the fillable fields of a PDF form with each field's name, type, page, current value, options and flags. Nothing is saved. It also reports an XFA form, which cannot be filled here. Used to build a field mapping, and to notice when a payer or agency has revised its form.
- Fill PDF Form Fills a form's text fields, checkboxes, radio groups, dropdowns and option lists, and saves the filled copy to FlowRunner file storage. Every value is checked before anything is saved, and an unknown field name stops the step unless the flow chooses to skip it. Optionally flattens the result so it can no longer be edited. Used to complete payer, agency and intake forms from data already in your systems.
Frequently asked questions
What can FlowRunner do with PDF Tools?
FlowRunner agents can run Split PDF by Page Ranges, Split PDF Every N Pages, and Merge PDFs in PDF Tools, plus 4 more actions.
Does connecting PDF Tools to FlowRunner require OAuth?
No. PDF Tools needs no credentials at all, so there is no key to obtain, store, or rotate.
Can PDF Tools trigger a FlowRunner workflow automatically?
PDF Tools doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with PDF Tools
Free plan, no card required. Connect in minutes.