Resources · Make integration

Convertio Make integrationAutomate Convertio with Make.

Need files converted without opening Convertio each time? The Convertio Make integration gives you 3 modules: two actions and one search. This page shows how to link your API key, then walks you through a first scenario that converts files for you.

Try the Convertio integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Convertio Make integration do?

The Convertio Make integration links your Convertio account to Make so that file conversions happen inside a scenario, the automation you build in Make as a chain of modules. A module is one brick of that chain. Convertio brings three of them, and none is a trigger, so something else starts the scenario.

Converted copies without the manual upload. A file shows up in the tool your team already works in, and the next module, Convert a File, turns it into the format you picked. Each file travels as a bundle, one item passed from module to module.

A look at past conversions. List Operations pulls the operations Convertio holds for your account, so a scenario can read them and hand them to a later step. A search like this can return nothing, one result or many.

Anything the two modules skip. Make an API Call reaches any endpoint of the Convertio API with the connection you already set up. It asks for more care, since you write the request yourself.

Keep the Free plan in mind: files there stop at 5 MB, which matters for a conversion tool. The Make pricing page covers the paid plans. The Convertio documentation on Make lists no specific limit. If you also look at n8n, the n8n vs Make comparison sets the two side by side, and Make training helps if scenarios are new to you.

Connect

How do you connect Convertio to Make?

  1. 01

    Copy your API key

    In your Convertio account, open the API section. No account yet? Click Register, sign up, then come back to the API section and copy the key shown on screen.

  2. 02

    Add a Convertio module

    In your Make scenario, add any Convertio module and click Create a connection. A connection is your Convertio account linked to Make once, then reused by every Convertio module.

  3. 03

    Name it and paste the key

    Give the connection a label in Connection name if you like, which helps when several accounts exist. Paste the API key you copied, save, and the module is ready to fill.

First scenario

Your first scenario with Convertio

GoalWhen a new file arrives in another app, Make sends it to Convertio and gets back a converted copy.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Convertio has no trigger, so this first spot goes to another app.

  2. 02

    Pick the starting app

    Search for the app where your files arrive, such as your storage or form tool, pick its trigger and connect that account. This module decides when the scenario runs.

  3. 03

    Add Convert a File

    Click the + on the right of that module, search for Convertio and choose Convert a File. Create the connection with your API key, then map the file from the first module and choose the target format.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received and check that the converted file came back.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default on a new scenario, then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What each Convertio module does

Convertio gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Convertio1

Convert a File

Action

In Make“Converts a file to a specified format.”

Hand this module a file and it returns the same content in the format you choose, ready for the next module to store or send. It is the core of almost every Convertio scenario.

When to use it
right after a trigger from another app delivers a file, whether a form upload, a mail attachment or a new document in shared storage.
Watch out
on the Make Free plan, files are capped at 5 MB, so check your plan before sending large documents.
Convertio2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the Convertio API from your scenario, reusing the connection you already created, and cover what the two other modules leave out. You write the request yourself instead of filling ready made fields.

When to use it
a Convertio feature you need has no dedicated module in Make.
Watch out
read the Convertio API documentation first, because Make will not guide the fields of a raw call for you.
Convertio3

List Operations

Search

In Make“Lists all operations.”

Get the list of operations Convertio keeps for your account, each one delivered as a separate bundle that later modules can read or filter. Here "operation" is the Convertio term, not the Make one used for your plan usage.

When to use it
you want a scenario to review past conversions before acting on them.
Watch out
a search can return zero, one or many bundles, so the modules after it may run several times.
Need help

Need help automating Convertio with Make?

A person reads every message.

FAQ

Convertio and Make: common questions

01Is the Convertio Make integration free?
Yes, on the Make side. Convertio is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Your Convertio subscription is a separate matter, handled on the Convertio pricing page, and Make still needs an active Convertio account with an API key.
02What does the Convertio Make integration require to connect?
An active Convertio account and its API key. Open the API section of your Convertio account, click Register if you have no account yet, then copy the key displayed on screen. In Make, add any Convertio module, click Create a connection, optionally fill Connection name, and paste the key. The same connection then serves all three Convertio modules, including Make an API Call, so you only set it up once per account.
03Does the Convertio Make integration start in real time?
No, because Convertio has no trigger in Make. Its three modules are two actions and one search, so the scenario has to start somewhere else. You can open it with the trigger of another app, for example an instant trigger that the other app calls through a webhook as soon as a file arrives. Or you can rely on scheduling: the clock on the first module runs the scenario on a schedule, every 15 minutes by default, and no less than 15 minutes apart on the Free plan.
04What if a Convertio module is missing in Make?
Use Make an API Call. This module can call any endpoint of the Convertio API from inside the scenario, with the same connection as the other modules, so a feature without a dedicated module is still reachable. The trade off is that you build the request yourself from the Convertio API documentation. If the issue is file size rather than a missing feature, remember that the Make Free plan caps files at 5 MB: check the size limit of your plan on the Make pricing page.
05Make or n8n for Convertio: which one fits?
It depends on the tool your team already runs. On Make, Convertio comes as a standard app with three modules: Convert a File, List Operations and Make an API Call, available from the Free plan and set up with a single API key. Many apps also have an n8n node, so check whether Convertio has one before deciding. If both exist, compare the modules each side offers for your use case and pick the platform where your other scenarios already live.
Same platform

Other docs you might need on this stack.

Browse all integrations