Zamzar

Convert files between hundreds of document, image, audio, and video formats with Zamzar. Agents start conversion jobs from uploaded files or public URLs, poll them to completion, download converted output into FlowRunner storage, and check supported formats and credit costs before converting.

6 actions Basic auth available

Zamzar website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A vendor emails a contract as a .docx attachment to the intake mailbox

Get Format confirms docx converts to pdf and reports the credit cost

Convert File starts the conversion job and returns a job id

Get Job polls until the status reads successful and target_files is populated

Download Converted File saves the PDF into FlowRunner storage

The archived PDF link posts to the legal channel with the source filename

A paralegal spot-checks the rendered PDF before it becomes the filed copy of record

What This Integration Enables

File conversion is the unglamorous tax on every document workflow: the intake process is fine until someone sends a .pages file, the media pipeline works until a client uploads .mov. Zamzar exists so that tax gets paid by an API instead of a person, and the FlowRunner connector makes the whole asynchronous cycle, start the job, poll it, download the output, a single agent behavior instead of a script someone maintains. - Convert uploaded documents to PDF for archiving, or transcode audio and video between formats, without a desktop tool in the loop - Hand Zamzar a public URL over HTTP, FTP, SFTP, or a public S3 object, so large files never transit your infrastructure - Discover valid target formats and their credit cost with List Formats before committing to a conversion - Land converted output directly in FlowRunner file storage, ready for the next step in the flow The asynchronous job model matters more than it sounds. A conversion is not a single call; it is a job started, a status polled, and an output collected, and a workflow that does not handle the failed status gracefully will lose files silently. FlowRunner agents run that full cycle as one behavior, with the failed branch routed to a person rather than swallowed. Because every conversion draws from a finite credit balance, the connector also pairs naturally with FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates: agents convert single files freely and pause for a person before a batch commits real spend.

Without FlowRunner

Format roulette at intake Documents arrive as docx, pages, heic, and mov, and someone opens each one to convert it by hand

Desktop tools in the pipeline Conversion means a laptop, an export menu, and a person who remembers the settings

Credits burned blind Nobody knows what a conversion costs until the balance runs out mid-batch

With FlowRunner

One archival format Everything that enters the workflow leaves it as pdf, png, or mp3, converted in flight

Cost checked before spend Agents call Get Format first, so every conversion's credit cost is known before the job starts

Conversions with a paper trail Every job id, source format, and output URL lands in a log a person can audit

Use Case Scenarios

Order attachments archived as PDF

A [Shopify](/integrations/shopify) order arrives carrying a custom artwork file in whatever format the customer had. The agent calls Get Format to confirm the source format converts to pdf, starts the job with Convert File, polls Get Job until successful, then pulls the output with Download Converted File. The PDF uploads to [Google Drive](/integrations/google-drive) in the order's folder, named by order number. Fulfillment opens one format, every time, regardless of what the customer sent.

Media transcoding into a CDN pipeline

Marketing drops raw video into a shared folder. The agent passes each file's public URL to Convert File targeting mp4, so the bytes go straight from source to Zamzar without a local download. Once Get Job reports success, Download Converted File retrieves the output and the agent pushes it to [Amazon S3](/integrations/aws-s3) for CDN hosting. A row lands in [Google Sheets](/integrations/google-sheets) recording the source file, target format, credit cost, and final URL, which is the audit trail when someone asks where the credits went.

The backfile conversion that asks first

Operations wants a legacy archive of 800 mixed-format documents standardized to PDF. The agent sweeps the folder, groups files by source format, and calls Get Format for each group to price the whole batch in credits. Instead of starting 800 jobs, it posts the plan to the operations lead: file counts per format, total credit cost, and the handful of formats with no pdf target. The lead approves, the agent runs the batch with List Jobs as its progress ledger, and the exceptions route to a person instead of failing silently.

Human-in-Loop Highlight

Convert File draws down a prepaid credit balance every time it runs, and a misconfigured loop can drain an account before anyone notices, converting the same folder twice or picking a target format that costs multiples of the intended one. So batch conversion agents in FlowRunner treat spend as a decision, not a side effect: the agent prices the batch with Get Format, posts the total credit cost and file count to the owner, and starts nothing until a person approves. Single-file conversions inside a live workflow run autonomously. The moment the job count or the credit total crosses a threshold you set, the agent asks. Credits do not come back, so committing them belongs to a person.

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

6 actions

Conversions

Convert File Starts a file conversion job from either a FlowRunner file or a public Source URL (HTTP, FTP, SFTP, or a public S3 object), targeting a format like pdf, png, docx, or mp3. Returns immediately with a job id; the conversion itself runs asynchronously.
Get Job Retrieves a conversion job's current state by id. The polling step: when status becomes successful, the target_files array holds the converted files to download. Also surfaces failed jobs so agents can route them to a person.
List Jobs Lists recent conversion jobs, most recent first, with status, formats, and target files. The progress ledger for batch runs and the way to recover a job id nobody kept.
Download Converted File Downloads a converted file's bytes by file id and saves them to FlowRunner file storage, returning the stored file's URL. The handoff that puts converted output into the rest of the flow.

Formats

List Formats Lists every source format Zamzar converts from, the target formats each supports, and the credit cost of each conversion. The discovery step before building any conversion workflow.
Get Format Retrieves the conversion options and credit costs for a single source format. The pre-flight check that confirms a specific conversion exists and prices it before Convert File commits credits.

Frequently Asked Questions

What can FlowRunner do with Zamzar?

FlowRunner agents can run Convert File, Get Job, and List Jobs in Zamzar, plus 3 more actions.

Does connecting Zamzar to FlowRunner require OAuth?

No. Zamzar connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Zamzar trigger a FlowRunner workflow automatically?

Zamzar doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Zamzar

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us