Resources · Make integration

Bannerbear Make integrationAutomate Bannerbear with Make.

Can your Bannerbear images, GIFs and videos get made without you opening Bannerbear each time? The Bannerbear Make integration covers it with 21 modules: 4 triggers, 14 actions and 3 searches. This guide is for marketers and ops teams who already design in Bannerbear and want a first scenario live.

Try the Bannerbear integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bannerbear Make integration automate for you?

The Bannerbear Make integration links your Bannerbear account to Make, a no-code tool where you build a scenario: the automation itself, drawn as a chain of bricks called modules. Once linked, Make can react when an image or a video appears in Bannerbear, and it can ask Bannerbear to create images, animated GIFs, videos, movies and collections on your behalf.

A review queue for videos. Watch New Video Pending Approval or Complete wakes the scenario when a video reaches Bannerbear's approval stage. From there you can post it to your team, then call Approve a Video or Delete a Video depending on the answer.

Images that land where the work happens. A new row in a sheet or a base can feed Create an Image, and the result goes back to the same record. If your data lives in Airtable, the Airtable Make integration shows the other half of that setup.

An inventory of what Bannerbear already produced. List Images, List Videos and List Collections return every matching item, one bundle each, which is handy for an audit or a cleanup.

What Make does not give you: a field-by-field description of each module. The documentation gives the 21 modules a name and one line each, so anything missing goes through Make an API Call with the same connection. Bannerbear also has an n8n node; compare both on the Bannerbear n8n integration page and in n8n vs Make.

Connect

How do you connect Bannerbear to Make?

  1. 01

    Copy the API key from Bannerbear

    You need an active Bannerbear account. Open your project dashboard, click Settings, then API Key, and copy the key shown on screen. That key is what lets Make act on your project.

  2. 02

    Add a Bannerbear module in Make

    In your scenario, add any Bannerbear module and click Create a connection. The Connection name field is optional, but a clear name helps once you run several Bannerbear projects.

  3. 03

    Paste the key and save

    Paste the API key and confirm. The connection (your Bannerbear account linked to Make once) is then offered in every other Bannerbear module, so you never paste the key twice.

First scenario

Your first scenario: a product visual for every new row

GoalWhen a new product row lands in your sheet or base, Make sends its data to Bannerbear and Create an Image returns the finished visual.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your products live, such as your spreadsheet or your base, and its module that watches new rows.

  2. 02

    Link the data source

    Click Create a connection to link that app, then fill the module fields. Make lists the sheets or tables it can read, so you choose the one holding your products.

  3. 03

    Add Create an Image

    Click the + on the right, search Bannerbear and pick Create an Image. Link your account, then map the product data from the first module into the fields Make shows you.

  4. 04

    Test with Run once

    Add a test row, then click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item, here one product). Check the image in Bannerbear.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, the shortest interval on the Free plan. Switch the scenario on, and every new product gets its visual.

Triggers

Which Bannerbear triggers can start a scenario?

4 modules start a scenario when something happens in Bannerbear. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Bannerbear as soon as it happens.

Bannerbear1Watch New Image

Watch New Image

Instant trigger

In Make“Watches for a new image.”

Watch New Image starts your scenario each time a new image appears in your Bannerbear project. Each image arrives as its own bundle, ready for the next module.

How it fires
instant, meaning Bannerbear calls Make through a webhook as soon as the image exists. No schedule to wait for.
When to use it
finished visuals should be posted, emailed or stored somewhere else without anyone downloading them by hand.
Watch out
click Create a webhook before Create a connection, and avoid creating images later in the same scenario, or it can wake itself up.
Bannerbear2Watch New Template

Watch New Template

Scheduled trigger

In Make“Watches for a new template.”

Watch New Template notices when a template is added to your Bannerbear project and hands it to the rest of the scenario. The designer adds the template once; Make takes it from there.

How it fires
scheduled, which means Make checks Bannerbear on the scenario's schedule, every 15 minutes by default. Nothing happens between two checks.
When to use it
you want a test render, a message to the design channel or a log entry whenever a new layout becomes available.
Watch out
on the Free plan the scheduled check cannot run more often than every 15 minutes, so a template may wait a little before Make sees it.
Bannerbear3Watch New Video Pending Approval or Complete

Watch New Video Pending Approval or Complete

Instant trigger

In Make“Watches for a new video which pending approval or completed.”

This trigger reacts to a Bannerbear video in two situations: it is waiting for approval, or it is complete. One module covers both the review moment and the delivery moment.

How it fires
instant. Bannerbear calls Make through a webhook as soon as a video reaches one of those two states.
When to use it
a reviewer should get the video the moment it needs a decision, and the final file should go out once it is done.
Watch out
since two states arrive through the same trigger, add a filter or a router right after it so pending videos and finished ones follow separate paths.
Bannerbear4Watch New Video Template

Watch New Video Template

Scheduled trigger

In Make“Watches for a new video template.”

Watch New Video Template is the video counterpart of the template trigger: it picks up each new video template created in your Bannerbear project and passes it along as a bundle.

How it fires
scheduled. Make checks Bannerbear on the scenario's schedule, so new video templates show up at the next check rather than the instant they are saved.
When to use it
the motion designer publishes a new format and the marketing team should hear about it, or a catalog of templates should stay current in a sheet.
Watch out
it only sees video templates. Image templates go through Watch New Template, so pick the one that matches what your designers publish.
Modules

What can Bannerbear do inside a Make scenario?

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

Bannerbear1

Approve a Video

Action

In Make“Approves a video.”

Approve a Video records a yes on a Bannerbear video that is waiting for approval, straight from the scenario. The reviewer never has to log in to Bannerbear to click through.

When to use it
after a reviewer answers in a form or a chat message, place this module on the approved branch of your router.
Watch out
approving is a decision. Keep a filter or a human answer in front of it rather than approving every incoming video.
Bannerbear2

Create a Collection

Action

In Make“Creates a collection.”

Create a Collection asks Bannerbear to build a new collection from inside your scenario. Make's documentation names the module without detailing what a collection contains, so open your Bannerbear project to see what a collection holds for you.

When to use it
you already produce collections by hand in Bannerbear and want the same result each time a record is ready.
Watch out
test it with Run once before switching the scenario on, and read the returned bundle.
Bannerbear3

Create a Movie

Action

In Make“Creates a movie.”

Create a Movie requests a movie from Bannerbear, which is not the same module as Create a Video. The two modules sit side by side in Make, so pick based on what your Bannerbear project calls a movie.

When to use it
your workflow already relies on Bannerbear movies and you want them started by an event, such as a new product going live.
Watch out
follow up with Get a Movie if a later module needs the result.
Bannerbear4

Create an Animated Gif

Action

In Make“Creates an animated gif.”

Create an Animated Gif produces a GIF in Bannerbear, the lightweight moving format that plays inside emails and chat tools where a video would not. It is the module to reach for when a still image feels flat and a full video is too heavy.

When to use it
a newsletter or a Slack announcement needs a short animated visual built from fresh data.
Watch out
on the Free plan Make handles files up to 5 MB, so keep the output small if a later module downloads it.
Bannerbear5

Create an Image

Action

In Make“Creates an image.”

Create an Image turns the data of your scenario into a finished visual: it asks Bannerbear for a new image and returns it as a bundle. No designer has to open a file for each version.

When to use it
a new blog post, product or event should get its visual without a designer opening a file.
Watch out
if Watch New Image sits at the top of the same scenario, every image you create here can trigger another run.
Bannerbear6

Create a Video

Action

In Make“Creates a video.”

Create a Video starts a video render in Bannerbear from your scenario. Paired with the video triggers, it opens a chain that goes from request to approval to delivery, with a person stepping in only to approve.

When to use it
each new listing, course or campaign deserves a short video built from its own data.
Watch out
if your videos pass through approval, the scenario that creates them is not the one that should approve them. Keep the review in a second scenario.
Bannerbear7

Delete a Video

Action

In Make“Rejects a video.”

Despite its name, Make describes Delete a Video as the module that rejects a video. Read it as the no answer in an approval process, the counterpart of Approve a Video.

When to use it
on the rejected branch of a review scenario, once someone has turned the video down.
Watch out
the name and the description do not say the same thing. Test on a throwaway video with Run once and check in Bannerbear what happened.
Bannerbear8

Get a Collection

Action

In Make“Gets a collection.”

Get a Collection reads one existing Bannerbear collection back into the scenario, so the modules after it can use its content. Nothing is created or changed; it only fetches.

When to use it
right after Create a Collection, or when a record in another tool points to a collection you need to send, file or report on.
Watch out
it returns a single collection. For all of them at once, List Collections is the better choice.
Bannerbear9

Get a Movie

Action

In Make“Gets a movie.”

Get a Movie fetches a single Bannerbear movie so its details reach the next module. Think of it as the reading companion of Create a Movie: one starts the work, the other brings back what was made.

When to use it
the movie must be attached to a message, logged in a project board or checked before it goes public.
Watch out
it only reads. If the scenario needs a new movie, Create a Movie comes first.
Bannerbear10

Get an Image

Action

In Make“Gets an image.”

Get an Image pulls one specific Bannerbear image into the scenario. It helps when the image was made earlier, by another scenario or by hand, and you now need it again.

When to use it
a customer record stores a reference to its visual and a later step (an email, a CMS post) should reuse that exact image.
Watch out
each call is one operation. When you need many images, List Images returns them in one module.
Bannerbear11

Get a Video

Action

In Make“Gets a video.”

Get a Video retrieves one Bannerbear video and exposes its data to the following modules. It fills the gap between the moment a video is requested and the moment you want to do something with it.

When to use it
a video was created in a first scenario and a second one has to share or archive it.
Watch out
if the video trigger already delivers the video you need, this extra read is a wasted operation.
Bannerbear12

Get Fonts Collection

Action

In Make“Gets a Collection of fonts”

Get Fonts Collection returns the set of fonts Bannerbear makes available to your project. It is a reference module: it does not make a visual, it tells the scenario what typography is on hand.

When to use it
you keep a brand sheet or a template checklist and want the font list pulled from Bannerbear instead of typed by hand.
Watch out
few everyday scenarios need it; skip it unless a later module really uses the font data.
Bannerbear13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is the escape hatch: it lets the scenario call any part of the Bannerbear API with the connection you already set up, no new key required.

When to use it
the other Bannerbear modules do not cover what you need, and the Bannerbear API documentation describes an endpoint that does.
Watch out
this is the only technical module of the app. You write the request yourself, so keep the API documentation open while you set it up.
Bannerbear14

Update a Video

Action

In Make“Modifies a video.”

Update a Video changes an existing Bannerbear video instead of starting over with a new one. Use it when the video is almost right and only part of it has to move.

When to use it
a reviewer asks for a correction and the scenario should apply it to the same video before it goes back for approval.
Watch out
if this scenario starts with Watch New Video Pending Approval or Complete, an update can send the video back through the trigger and loop. Filter carefully.
Bannerbear15

List Collections

Search

In Make“Lists all collections.”

List Collections is a search: it returns every collection in your Bannerbear project, each one as a separate bundle. The modules that follow run once per collection.

When to use it
you want a sheet that shows all collections for a review, or you need to find one before calling Get a Collection.
Watch out
a large list means many bundles, and each module after it spends one operation per bundle.
Bannerbear16

List Images

Search

In Make“Lists all images.”

List Images gathers the images stored in Bannerbear and releases them one bundle at a time. It is the way to look back at what was already produced, not to wait for the next one.

When to use it
an asset audit, a backup to cloud storage, or a report of which visuals exist for a campaign.
Watch out
the search can return zero, one or many images. Add an aggregator if you want a single summary instead of one message per image.
Bannerbear17

List Videos

Search

In Make“Lists all videos.”

List Videos returns all the videos of your Bannerbear project, one bundle each, so you can sort, archive or report on them in bulk.

When to use it
you are catching up on videos made before your approval scenario existed, or feeding a dashboard with the full list.
Watch out
run it with Run once first and count the bundles. On the Free plan, a scenario stops after 5 minutes of execution, which a long list can hit.
Need help

Need help automating Bannerbear with Make?

A person reads every message.

FAQ

Bannerbear and Make: common questions

01Is the Bannerbear Make integration free?
Yes, on the Make side. Bannerbear is a standard app, so it works from the Free plan. That plan gives you 2 active scenarios, a scheduled check every 15 minutes at the shortest, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run. Your Bannerbear subscription is a separate matter, handled on Bannerbear's pricing page.
02What does it take to connect Bannerbear to Make?
An active Bannerbear account and its API key. In Bannerbear, open the project dashboard, then Settings, then API Key, and copy the key. In Make, add any Bannerbear module, click Create a connection, give it a name if you like, and paste the key. For the two instant triggers, click Create a webhook first and then Create a connection. The same connection then serves all 21 modules, so this setup only happens once per Bannerbear project.
03Do Bannerbear triggers in Make fire in real time?
Two of them do. Watch New Image and Watch New Video Pending Approval or Complete are instant: Bannerbear calls Make through a webhook as soon as the image or video exists. Watch New Template and Watch New Video Template are scheduled: Make checks Bannerbear on the scenario's schedule, every 15 minutes by default and never faster than that on the Free plan. Paid plans can check every minute. If speed matters, build around the instant triggers and keep the scheduled ones for templates, which rarely need an immediate reaction.
04What if a Bannerbear module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Bannerbear API with the connection you already created, so no second key is involved. The trade-off is that you write the request yourself, following Bannerbear's API documentation, while the other modules fill their fields for you. Make's documentation for this app lists modules by name without field details, so testing with Run once and reading the returned bundles is the reliable way to see what each module gives back.
05Make or n8n for Bannerbear: how do you choose?
It depends on where the rest of your automations already live. Bannerbear exists in both tools: Make offers the 21 modules described on this page, and n8n has its own Bannerbear node, documented on a separate page of this site. The practical test is to list the actions your workflow needs, such as video approval or GIF creation, and check that each one is available in the tool you use daily. Keeping a Bannerbear flow in the same tool as its neighbors makes it easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations