ConvertAPI
Document ProcessingConvert files between hundreds of format pairs with ConvertAPI. Agents turn documents into PDF and Office formats, render live web pages to PDF, and check remaining conversion quota before large batches.
What This Integration Enables
Document workflows break on format friction: the vendor sends xlsx, the archive wants PDF, the downstream parser wants csv, and a person becomes the conversion layer. ConvertAPI removes that person from the loop. FlowRunner agents convert files between hundreds of format pairs by URL, render live web pages to PDF through a headless browser, and check the account's remaining conversion balance before committing to a batch. Results come back as temporary download URLs, which makes the output immediately usable by the next step in a flow: an email, an archive write, a parser. Conversion is the definition of unglamorous work, which is exactly why it belongs to agents. The judgment calls, whether the rendered output is faithful enough to be the copy of record, stay with people through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates. - Normalize every inbound document to PDF for consistent viewing, parsing, and archiving - Turn PDFs into editable Office formats, and spreadsheets into csv for pipelines - Snapshot live web pages, invoices, and dashboards as portable, timestamped PDFs - Budget conversion quota with a pre-flight balance check before bulk jobs
Without FlowRunner
With FlowRunner
Use Case Scenarios
The intake normalizer
An operations team receives supplier documents through email and shared drives in whatever format the supplier prefers. A FlowRunner agent watches the intake folder in [Google Drive](/integrations/google-drive), pulls each new file's URL, and calls Convert File to produce a PDF copy alongside the original. Spreadsheets additionally get a csv rendition for the data pipeline. Downstream steps stop caring what the supplier sent, because by the time a document reaches them it is always the same two formats.
Web pages as evidence
A finance team reconciles SaaS invoices that exist only as web pages behind vendor portals. When a billing workflow needs the record, the agent calls Convert Web Page To PDF with the invoice URL, and the rendered document is filed with the transaction and linked in [Slack](/integrations/slack) for the approver. A year later, the audit does not depend on whether the vendor's portal still shows that invoice, because the PDF was frozen the day it mattered.
The bulk migration with a budget
A team migrating a legacy archive needs several thousand docx files rendered to PDF. Before the loop starts, the agent calls Get User Info and projects the batch against the remaining seconds balance. The migration runs in nightly tranches sized to the quota, appending each conversion's source, output URL, and cost to a log in [Google Sheets](/integrations/google-sheets). When a tranche would overrun the balance, the run pauses and the owner decides whether to top up the plan or let the next cycle absorb it.
Human-in-Loop Highlight
Convert File is where a document quietly becomes a different document. A docx to PDF rendering that drops a table row, re-flows a signature page, or mangles a currency symbol produces an artifact that looks authoritative and is subtly wrong, and once that artifact is emailed to a customer or filed as the copy of record, the flawed version is the one everyone downstream trusts. So FlowRunner workflows gate the moment of record: the agent converts, checks page count and file integrity, and then a person eyeballs the rendered output before it ships to a counterparty or lands in the archive as final. Routine internal conversions flow straight through. The gate reserves human attention for the conversions whose output someone else will rely on, which is the difference between reviewing everything and reviewing what matters.
Agent Capabilities
3 actionsConversion
2- Convert File Converts a file from one format to another by URL: pdf to docx, docx to pdf, jpg to png, xlsx to csv, and hundreds of other pairs. The converted file is stored on ConvertAPI temporary storage and returned as a download URL, ready for the next workflow step. Format-specific options pass through Extra Parameters.
- Convert Web Page To PDF Renders a live web page into a PDF via headless browser and returns a download URL. The action that turns dashboards, invoices, and articles into timestamped, portable evidence.
Account
1- Get User Info Retrieves the account's plan, identifiers, and remaining seconds and conversions balance. The pre-flight check that keeps bulk jobs from discovering the quota ceiling halfway through.
Frequently Asked Questions
What can FlowRunner do with ConvertAPI?
FlowRunner agents can run Convert File, Convert Web Page To PDF, and Get User Info in ConvertAPI.
Does connecting ConvertAPI to FlowRunner require OAuth?
No. ConvertAPI connects to FlowRunner with an API key, no OAuth flow required.
Can ConvertAPI trigger a FlowRunner workflow automatically?
ConvertAPI doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with ConvertAPI
$100 in credits. No card required. Connect in minutes.