ActionConvertAPIUpdated September 2026
How do I convert a file between formats?
Short answer: You can convert file format in ConvertAPI by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ConvertAPI Convert File Format action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
From Format fromFormat | string | Required | From Format. e.g. "docx" |
To Format toFormat | string | Required | To Format. e.g. "pdf" |
File URL fileUrl | url | Required | A fully qualified URL (https://...) for the file url. |
Sample request
{"fromFormat": "docx","toFormat": "pdf","fileUrl": "e.g. https://example.com/path"}
Returns
{"Files": [{"Url": "https://v2.convertapi.com/d/...","FileName": "output.pdf","FileSize": 524288}],"ConversionCost": 1}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Convert File Format.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Convert File Format.
What does the Convert File Format action do in ConvertAPI?
Converts between PDF, Word, Excel, PowerPoint, HTML, images, and 100+ other format pairs. Pass source URL or file content + target format. For "client uploaded a PDF, convert to editable Word" or "HTML invoice → PDF for archival" workflows.
What inputs does Convert File Format require?
Required: From Format, To Format, File URL. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if ConvertAPI returns an error?
The run history shows the failed step with its input and the error message ConvertAPI returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Convert File Format support batch operations?
Run Convert File Format inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within ConvertAPI's rate limits.