ConvertAPI Make integrationAutomate ConvertAPI with Make.
Need files converted without opening a converter by hand? The ConvertAPI Make integration gives you 3 action modules: upload a file, convert it, or call the API directly. This guide is for people who already use ConvertAPI and walks you from connection to a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the ConvertAPI Make integration do for you?
The ConvertAPI Make integration links your ConvertAPI account to Make so files get uploaded and converted inside a scenario, which is the automation you build in Make as a chain of modules. A module is one brick of that chain. ConvertAPI brings three of them, all actions, so something else has to hand them a file first.
Converted copies of incoming attachments. A file lands in another app you already use, Make passes it to Upload a File, and Convert a File produces the version your team actually opens. Each file travels as a bundle, one item moving from one module to the next.
A conversion step inside a bigger flow. When a scenario already collects documents, for example from a form or a shared drive, drop the two ConvertAPI modules in the middle and send the result on to the next app. If you keep your records in Airtable, the Airtable Make integration is one place to store what comes out.
Calls the listed modules skip. If the option you need is in the ConvertAPI API but not in the two file modules, Make an API Call reaches any endpoint with the same connection, so you are not stuck when the option you need has no module.
Know the limits before you build. ConvertAPI has no trigger in Make, so it never starts a scenario on its own, and the documentation gives no figures on file size or volume for this app. On the Free plan, Make caps files at 5 MB and runs at 5 minutes each. If you are still weighing tools, our n8n vs Make comparison sets out the criteria, and Make pricing explains how operations are counted.
How do you connect ConvertAPI to Make?
- 01
Open the connection window
In your scenario, add any ConvertAPI module, such as Upload a File, then click Create a connection. A connection is your ConvertAPI account linked to Make once, and every ConvertAPI module reuses it afterwards.
- 02
Give it a clear name
Naming the connection is optional, but a label like the account owner or the workspace saves guesswork later, especially if a colleague ends up with a second ConvertAPI account in the same Make organization.
- 03
Authorize and save
Follow what Make shows you: either approve access on the ConvertAPI page that opens, or paste the key ConvertAPI gives you into the field. Then click Save, and the module can use your account right away.
Build your first scenario with ConvertAPI
GoalWhen a file arrives in another app, Make uploads it to ConvertAPI and hands back a converted copy.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the +. Since ConvertAPI has no trigger, your first module comes from the app where your files already live.
- 02
Pick the starting module
Search that app, choose the module that watches for new files and connect the account. Make can then list the folders or items it is allowed to read, so you point it at the right place.
- 03
Add Upload a File
Click the + to the right, search ConvertAPI and choose Upload a File. Create the connection, then map the file coming out of the first module into it.
- 04
Add Convert a File
Add Convert a File next, choose the source and target formats, and map the File ID returned by the upload step so ConvertAPI knows which file to work on.
- 05
Test with Run once
Click Run once. Make runs the scenario a single time and shows the bundles each module received, which is where you check that a file really went in and a result came out.
- 06
Schedule and switch it on
Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From then on each run counts operations, one per module per bundle.
What each ConvertAPI module does
ConvertAPI gives you 3 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.
Files
2 modules
Upload a File
ActionIn Make“Uploads a file and returns a File ID to be used for conversions.”
This module sends a file from your scenario to ConvertAPI and returns a File ID, a reference you reuse in the conversion step instead of sending the file twice.
Convert a File
ActionIn Make“Converts a file from selected format to other selected format.”
Here is where the actual work happens: you pick the format the file is in and the format you want, and ConvertAPI returns the converted result for the next module to store or send.
Other
1 moduleMake an API Call
ActionIn Make“Performs an arbitary authorized API Call.”
Your fallback for anything the two file modules do not cover: it calls any endpoint of the ConvertAPI API with the connection you already set up, so no second login is needed.
Need help automating ConvertAPI with Make?
A person reads every message.
