Resources · Make integration

Very Good FFmpeg Make integrationAutomate Very Good FFmpeg with Make.

Can Make start and follow your FFmpeg jobs for you? The Very Good FFmpeg Make integration gives you 6 modules: 1 scheduled trigger, 4 actions and 1 search. This guide shows how to link your account and build a first working scenario.

Try the Very Good FFmpeg integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Very Good FFmpeg Make integration do?

The Very Good FFmpeg Make integration links your Very Good FFmpeg account to Make, so a scenario (the automation you build in Make, a chain of modules) can launch FFmpeg jobs, look them up, list them or cancel them. Each module is one brick of that chain, and you set it up by clicking, not by writing code.

Launch a job from another app. When a record or a file shows up elsewhere in your stack, Run an FFmpeg job can start the processing in Very Good FFmpeg with values mapped from that earlier step.

Keep an eye on your jobs. Watch jobs checks your account on the scenario's schedule and hands every job it finds to the next module, for example a message to your team or a row in a tracking sheet. Get a job reads a single job again when you need its latest details.

Clean up what should not run. List jobs returns the jobs of your account, and Cancel a job stops one you no longer need, such as a duplicate launched by mistake.

The official Make documentation for this app is short: it names the modules, but gives no field list and no specific limit, and it warns that its content was generated with AI help. Test each module with Run once (the editor button that runs the scenario one time) before you rely on it, and keep Make troubleshooting close by. For anything the 6 modules do not cover, Make an API call reaches the rest of the Very Good FFmpeg API. Still choosing a platform? Read the Make review and the n8n vs Make comparison.

Connect

How do you connect Very Good FFmpeg to Make?

  1. 01

    Copy your API key

    Log in to Very Good FFmpeg and open the dashboard. Your API key is displayed there: copy it and keep it at hand. You need a Very Good FFmpeg account first, and its subscription is described on the Very Good FFmpeg pricing page.

  2. 02

    Open a connection in Make

    In your scenario, add any Very Good FFmpeg module and click Create a connection. A connection is your Very Good FFmpeg account linked to Make once, then reused by every module of the app.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several accounts coexist. Paste the API key you copied, or follow the instructions Make shows on screen, then save.

First scenario

Your first scenario with Very Good FFmpeg

GoalWhen a new item lands in another app, Make starts a Very Good FFmpeg job with the data of that item.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module: the app where the item you want to process shows up.

  2. 02

    Set up the starting app

    Pick that app's module, create its connection and fill its fields. Make lists the folders or objects it can read as soon as the connection exists, so you choose rather than type.

  3. 03

    Add Run an FFmpeg job

    Click the + on the right of the first module, search for Very Good FFmpeg and pick Run an FFmpeg job. Select your connection, then map the values coming from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item passed from a module to the next). Check that a job appears in Very Good FFmpeg.

  5. 05

    Schedule and switch on

    On the first module, open the clock and set the schedule: every 15 minutes by default. Then switch the scenario on. Each module run counts as an operation, the unit Make counts on your plan.

Triggers

What starts a Very Good FFmpeg scenario

1 module starts a scenario when something happens in Very Good FFmpeg. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Very Good FFmpeg as soon as it happens.

Very Good FFmpeg1Watch jobs

Watch jobs

triggerIn the docs only

Watch jobs gives you a steady feed of the jobs in your Very Good FFmpeg account, so a scenario can react to them without you opening the dashboard. Each job it finds becomes a bundle for the modules that follow.

How it fires
it is a scheduled trigger. Make checks the app on the scenario's schedule, every 15 minutes by default, and never faster than 15 minutes on the Free plan.
When to use it
when a team or a channel should hear about jobs without anyone checking by hand.
Watch out
the documentation does not say which jobs it returns or in which state, so click Run once and read the bundles before you build on them.
Modules

What each Very Good FFmpeg module does

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

Very Good FFmpeg1

Cancel a job

ActionIn the docs only

Cancel a job stops a job in Very Good FFmpeg from inside your scenario, which saves you a trip to the dashboard when something was launched by mistake.

When to use it
after a filter spots a duplicate, or right after List jobs has found the job you want to drop.
Watch out
the documentation says nothing about resuming a cancelled job, so treat the cancel as final and test it on a throwaway job first.
Very Good FFmpeg2

Get a job

ActionIn the docs only

Get a job fetches one precise job again, so the next modules work with its current details instead of an older copy.

When to use it
when an earlier module has already pointed to the job and you want a fresh read before notifying someone.
Watch out
it reads one job only; to browse several, pick List jobs.
Very Good FFmpeg3

List jobs

SearchIn the docs only

List jobs returns the jobs of your account as separate bundles, which lets the modules after it handle each job on its own.

When to use it
for a report of what ran, or to find a job before cancelling it.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, which adds operations to your plan.
Very Good FFmpeg4

Make an API call

ActionIn the docs only

Make an API call opens the rest of the Very Good FFmpeg API to your scenario, using the same connection as the other modules.

When to use it
when an endpoint you need has no dedicated module among the 6 listed here.
Watch out
you write the request yourself, so keep the vendor's API documentation open and test the call with Run once before mapping its response.
Very Good FFmpeg5

Run an FFmpeg job

ActionIn the docs only

Run an FFmpeg job launches processing in Very Good FFmpeg straight from a scenario, with inputs mapped from the modules before it.

When to use it
when an item arriving in another app, such as a new upload or a form entry, should set off a job without anyone launching it by hand.
Watch out
the documentation lists no fields for this module, so build it with Run once and read the returned bundle before chaining Get a job.
Need help

Need help automating Very Good FFmpeg with Make?

A person reads every message.

FAQ

Very Good FFmpeg and Make: common questions

01Is the Very Good FFmpeg Make integration free?
Yes, on the Make side. Very Good FFmpeg is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits each month. Your Very Good FFmpeg account is billed separately; its own pricing page gives the details.
02What do you need to connect Very Good FFmpeg to Make?
Two things: a Very Good FFmpeg account and its API key. Once logged in to Very Good FFmpeg, the key is displayed on the dashboard, ready to copy. In Make, add a Very Good FFmpeg module, click Create a connection, give it a name if you like and paste the key. That single connection then serves all 6 modules of the app, including Make an API call, so you only enter the key once per account.
03Does the Very Good FFmpeg trigger react in real time?
No. Watch jobs is a scheduled trigger: Make checks your account on the scenario's schedule, which is every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. A job will therefore reach your scenario at the next check, not the moment it appears. The app has no instant trigger, the kind an app fires through a webhook as soon as something happens, in the documentation read for this page.
04What if a Very Good FFmpeg module is missing in Make?
Use Make an API call. It calls any endpoint of the Very Good FFmpeg API with the connection you already set up, so you are not limited to the 5 other modules. You will need the vendor's API documentation to write the request. The Make documentation for this app gives no specific limit and states that its content was generated with AI help, so for any doubt about how the API behaves, the vendor is the right contact.
05Should you use Make or n8n for Very Good FFmpeg?
It depends on the tool your team already runs. On Make, this page confirms 6 modules, a Free plan to test on and Make an API call for gaps. Many apps also have an n8n node, but this guide did not check one for Very Good FFmpeg, so look at the n8n node list before deciding. Compare what each platform offers for the jobs you actually need to launch, follow or cancel, and test one real case on each side.
Same platform

Other docs you might need on this stack.

Browse all integrations