Convertio
Utilities & PersonalConvert files between more than 300 formats with Convertio, covering documents, images, audio, video, ebooks, presentations, spreadsheets, archives, and CAD. Agents normalize whatever arrives into the format the next system accepts.
What This Integration Enables
Convertio's argument is breadth. More than 300 formats across documents, images, audio, video, ebooks, presentations, spreadsheets, archives, fonts, vector, and CAD, with optical character recognition available for scanned documents in 75 languages. That breadth is what makes it a sensible default in a workflow that has to accept whatever the outside world sends. A supplier who exports to WPS, an architect who sends DWG, a customer who photographs a receipt, and a partner whose reporting tool only emits ODS all land in the same intake flow, and the flow does not need a branch per sender.
The model is asynchronous and this connector does not pretend otherwise. A conversion is started from a public URL, from inline base64 or plain text content, or from a file already in FlowRunner file storage, and returns a conversion ID. Get Conversion Status is polled while the step field moves through wait, upload, and convert to finish. Two details matter in practice. Start Conversion From File uploads the bytes to Convertio directly rather than requiring the file to be publicly reachable first, which keeps a private document private. And the output URL Convertio returns is bound to the requesting host IP and cannot be shared, so Download Converted File is what turns a finished job into a durable, shareable link that the rest of the workflow can actually use. The connectors in FlowRunner exist to make that whole sequence one legible set of steps rather than a hand-rolled polling loop.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Making an executed contract searchable
An executed agreement comes back as a scan. The agent calls Start Conversion From File with recognition enabled, so the bytes go straight from FlowRunner file storage to Convertio without being exposed at a public URL. It polls Get Conversion Status until the step reaches finish, reading step percent to report progress on long documents, then calls Download Converted File to store the output durably. The converted copy and the original scan are attached to the same matter record, alongside the signature artifacts from DocuSign, so a later search for a clause finds the document and a later audit finds the original.
Normalising mixed inbound attachments
An intake mailbox receives whatever people send. The agent calls Start Conversion From URL for attachments already hosted, and Start Conversion From Content for files that exist as a value inside the flow, using base64 for binary sources such as DOCX or images and raw text for HTML, CSV, and SVG. Every document lands in the archive as PDF regardless of what arrived. When a conversion produces several output files, such as a multi-page document rendered to images, Convertio assembles a ZIP and that archive is what gets stored, which keeps a many-page result as one attachment rather than as a scatter of files.
Reconciling a batch after the fact
A long-running conversion batch finished overnight and one callback never arrived. The agent calls List Conversions with the status filter to pull the recent jobs with their input and output formats, filenames, consumed API minutes, and, for failures, the error Convertio reported. That is enough to recover the conversion IDs, retry the failures, and account for the minutes consumed. Delete Conversion then removes finished jobs and their outputs from Convertio's servers once the results are safely stored elsewhere, which is optional cleanup rather than a requirement because conversions age out on their own.
Human-in-Loop Highlight
Conversion has a failure mode that no status field reports. Get Conversion Status will tell you a job reached finish, how many API minutes it consumed, and how large the output is. It will not tell you that the signature block reflowed onto a page of its own, that a two-column contract was linearised into an order nobody intended, or that recognition read a handwritten amendment as something close to what the parties wrote. The job succeeded. The document changed. And if the converted copy becomes the searchable record while the original is filed away, the changed version is the one every future reader will see.
So when the output of a conversion is going to stand in for the original, the agent stops. It stores both, posts them together in the legal operations channel, and asks: "Contract NLF-MSA-2026 converted from a 14 page scan with recognition enabled. Output is 14 pages, 96 KB of extracted text. Confirm the converted copy as the searchable record, or keep the scan authoritative and file the conversion as a reading copy?" The contract owner opens both and answers. It takes a minute, it happens once per document, and it is the difference between an archive people trust and an archive nobody checks. For routine conversions, thumbnails, web-ready images, transcoded media, no gate is needed and the agent does not ask. FlowRunner's position is that human-in-the-loop belongs where a step quietly redefines what a record says, and nowhere else.
Agent Capabilities
7 actionsStarting a Conversion
3- Start Conversion From URL Starts an asynchronous job that downloads a publicly reachable file and converts it into any supported target format. Returns a conversion ID for polling. Optionally enables optical character recognition for scanned documents and registers a callback URL that Convertio notifies on finish or failure.
- Start Conversion From Content Starts a job from file content supplied inline, either as base64 for binary sources such as PDF, DOCX, or images, or as raw text for HTML, CSV, SVG, and other plain-text sources. Used when the file already exists as a value inside the flow rather than at a URL.
- Start Conversion From File Starts a job from a file held in FlowRunner file storage. The bytes are uploaded straight to Convertio through the documented direct-upload endpoint, which avoids exposing the file publicly. Returns a conversion ID plus the number of bytes uploaded.
Tracking a Conversion
2- Get Conversion Status Reads the current state of a job so a flow can poll until it is done. The step field moves through wait, upload, and convert before reaching finish, and step percent reports progress within the current step. At finish the response also carries the output URL and size, and for multi-file results the ZIP containing every produced file.
- List Conversions Lists recent conversions on the account with their status, detected input format, requested output format, filename, consumed API minutes, and the reported error for failures. Used to audit activity, reconcile jobs whose callback was missed, and recover conversion IDs.
Retrieving and Cleaning Up
2- Download Converted File Retrieves the finished output and stores it in FlowRunner file storage, returning a durable, shareable URL. This is required rather than optional, because the output URL Convertio returns is bound to the requesting host IP and cannot be shared. The job must have reached the finish step first.
- Delete Conversion Cancels a running conversion or removes a finished one together with its output file from Convertio's servers. Used to stop a job that is no longer needed or to clear results once they are stored elsewhere. Returns a not-found error if the conversion has already been removed.
Triggers
1 triggersEvent Triggers
1- On Conversion Completed Fires when a conversion reaches a terminal state. Each cycle reads the account's recent conversions and emits one event per job that has newly finished or failed since the previous cycle, carrying the conversion ID, filename, input and output formats, consumed API minutes, and any error text. You choose whether successful jobs, failed jobs, or both should fire, and the polling interval is configurable down to 30 seconds. The first cycle records the current conversions as a baseline and emits nothing, so activating the trigger does not replay existing history. Used to pick up long-running conversions in a separate flow from the one that started them, and to route failures to a person without polling from inside the original workflow.
Frequently Asked Questions
What can FlowRunner do with Convertio?
FlowRunner agents can run Start Conversion From URL, Start Conversion From Content, and Start Conversion From File in Convertio, plus 4 more actions.
Does connecting Convertio to FlowRunner require OAuth?
No. Convertio connects to FlowRunner with an API key, no OAuth flow required.
Can Convertio trigger a FlowRunner workflow automatically?
Yes. Convertio supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Convertio
$100 in credits. No card required. Connect in minutes.