Short answer: Drop the "ConvertAPI → Convert File Format" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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. |
{"fromFormat": "docx","toFormat": "pdf","fileUrl": "e.g. https://example.com/path"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.