Resources · Make integration

MegaConvert Make integrationAutomate MegaConvert with Make.

Can Make convert your files through MegaConvert without a single line of code? Yes: the MegaConvert Make integration gives you 5 action modules and no trigger. This guide shows how to link your account, build a first scenario and pick the right module.

Try the MegaConvert integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the MegaConvert Make integration do?

The MegaConvert Make integration links your MegaConvert account to Make, so a scenario (the automation you build in Make, a chain of modules) can send a file for conversion and pick up the output. All five modules are actions: something else has to start the scenario, either a schedule or a trigger from another app.

A converted copy of every incoming file. A module (one brick of a scenario) from your storage or form tool spots the new file, then Convert a file hands it to MegaConvert and Download result brings the output back into the flow, ready for the next app.

A job you can follow. When you want to know where a conversion stands before moving on, Get job status should, as its name says, read the state of the job, so the next step can wait for the right answer.

A usage check. Get API usage, going by its name, reports how much of your MegaConvert API you have consumed, handy to alert an admin before a heavy batch.

Know the limits before you start: Make's own documentation for MegaConvert says it is incomplete, because little public information exists about the app. It gives no description of the modules either: what this page says about each one is read from its name, so test each module with Run once and read what comes back. For anything the listed modules skip, Make an API call reaches other endpoints with the same connection. If you also weigh n8n, the n8n vs Make comparison lays out the criteria. New to the editor? Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect MegaConvert to Make?

  1. 01

    Add a MegaConvert module

    In your scenario, click the + and search for MegaConvert, then pick any of its modules. In the module panel, click Create a connection. A connection is your MegaConvert account linked to Make once and reused by every MegaConvert module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, something that tells accounts apart later. Then either authorize Make on the MegaConvert page that opens, or paste the key MegaConvert gives you, depending on what the window asks for.

  3. 03

    Save and reuse

    Click Save. The connection now appears in the dropdown of every MegaConvert module, so the next module you add only needs you to select it instead of logging in again.

First scenario

Your first scenario with MegaConvert

GoalWhen a new file lands in another app, Make sends it to MegaConvert and brings back the converted result.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since MegaConvert has no trigger, start with the app where your files arrive.

  2. 02

    Add Convert a file

    Click the + to the right of that first module, search for MegaConvert and choose Convert a file. Select your connection, then map the file from the previous module into the fields Make shows.

  3. 03

    Fetch the output

    Add Download result after it and map the data that Convert a file returned. The bundle (one item passed from module to module) coming out is what your next app will store or send.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, which is the best way to see what MegaConvert actually sends back.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What each MegaConvert module does

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

MegaConvert1

Convert a file

ActionIn the docs only

Sends a file to MegaConvert for conversion, straight from your scenario, so nobody has to upload it by hand. This is the core brick of the integration.

When to use it
right after the module that brings in the file, such as a new attachment or an uploaded document.
Watch out
the documentation does not list its fields, so map one test file first and check the bundle with Run once.
MegaConvert2

Download result

ActionIn the docs only

Brings the converted output back into Make, where the following modules can save it, email it or attach it to a record. Without it, the conversion stays on the MegaConvert side.

When to use it
after Convert a file, whenever the next step needs the actual file rather than a reference.
Watch out
on the Free plan Make handles files up to 5 MB, so large outputs call for a paid plan.
MegaConvert3

Get API usage

ActionIn the docs only

Its name says it reads how much of your MegaConvert API you have used, so you check consumption from inside the scenario. It concerns your account, not a single file.

When to use it
ahead of a large batch of conversions, to warn someone in chat or email when usage runs high.
Watch out
each call is still one operation on your Make plan.
MegaConvert4

Get job status

ActionIn the docs only

Going by its name, it tells you the state of a MegaConvert job, so the scenario moves on with facts instead of guessing. Useful when a conversion is not instant.

When to use it
between Convert a file and Download result, when you want to confirm the job before fetching anything.
Watch out
the documentation does not describe the possible statuses, so read them in a Run once test before relying on one.
MegaConvert5

Make an API call

ActionIn the docs only

Opens the whole MegaConvert API to your scenario, reusing the connection you already created. It covers any endpoint the four other modules leave out.

When to use it
when an option you need in MegaConvert has no dedicated module in Make.
Watch out
you write the request yourself, so start from one simple request and check the answer with Run once.
Need help

Need help automating MegaConvert with Make?

A person reads every message.

FAQ

MegaConvert and Make: frequent questions

01Is the MegaConvert Make integration free?
Yes, MegaConvert is a standard app, available from the Make Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops an execution after 5 minutes, and handles files up to 5 MB with 512 MB of data transfer. Paid plans drop the minimum interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. The price of MegaConvert itself is a separate matter, set by MegaConvert.
02What do you need to connect MegaConvert to Make?
A MegaConvert account and a Make account. Make's documentation lists no specific prerequisite for this app, so the generic connection flow applies: add any MegaConvert module, click Create a connection, give it a name if you want, then authorize Make on the MegaConvert page or paste the key MegaConvert gives you, and click Save. The same connection then serves all five modules, including Make an API call. You link the account once, then simply pick it in each new module.
03Does the MegaConvert Make integration react in real time?
No, because MegaConvert has no trigger module in Make: all five modules are actions. A scenario therefore starts in one of two ways. Either another app fires first, for example a storage or form tool that spots a new file, or you set a schedule on the first module, every 15 minutes by default and down to 1 minute on paid plans. In both cases the MegaConvert modules run as soon as the scenario reaches them.
04What if a MegaConvert module is missing in Make?
Use Make an API call. It sends a request to any MegaConvert API endpoint with the connection you already set up, which covers whatever Convert a file, Download result, Get API usage and Get job status do not. Keep in mind that Make's documentation for this app is incomplete, since little public information exists about MegaConvert. Testing each request with Run once remains the surest way to see the exact data that comes back.
05Should you use Make or n8n for MegaConvert?
It depends on where the rest of your automations run. In Make, MegaConvert offers five action modules plus Make an API call, and it works from the Free plan, with 2 active scenarios at no cost. Before choosing n8n, check that a MegaConvert node exists there and covers the same operations, since this page cannot confirm it. The n8n vs Make comparison on this site lays out the general criteria side by side, so you can weigh them against your own setup.
Same platform

Other docs you might need on this stack.

Browse all integrations