Resources · Make integration

Apiframe Make integrationAutomate Apiframe with Make.

Can Make turn a text prompt into Apiframe images without you opening Apiframe? Yes. The Apiframe Make integration gives you 5 action modules: grids, variations, upscales, retrieval and a custom API call. This page helps you connect your account and build a first scenario.

Try the Apiframe integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Apiframe Make integration let you automate?

The Apiframe Make integration links your Apiframe account to Make so a scenario, the automation you build in Make, can ask Apiframe for images on its own. Each step of that scenario is a module, one brick that does one job: here, create a grid, make variations, upscale a picture or fetch a grid you already made.

A visual for every new product. A store adds a product in its catalog tool, and the scenario sends the product name as a prompt to Create an image grid. Apiframe returns four candidate images in one grid, and Upscale an image turns the best one into a usable visual.

More options when the first try misses. A designer marks a grid as not quite right in a tracking sheet. Create a variation starts from that earlier task and gives four fresh takes, without rewriting the prompt.

Grids you can find again. A content team keeps the grid ID in a sheet row, and Get an image grid pulls that grid back later to publish it or pass it on.

Know the limits before you start: Make's documentation for Apiframe is marked as limited, so it gives no connection steps, no field list and no troubleshooting notes. For anything the five modules do not cover, Make an API Call reaches the rest of the Apiframe API. If you are still choosing a tool, read n8n vs Make. To learn the editor properly, Make training walks through it, and Make troubleshooting helps when a run fails.

Connect

How do you connect Apiframe to Make?

  1. 01

    Add an Apiframe module

    In your scenario, click the + and search for Apiframe, then pick any of its modules, such as Create an image grid. Make asks for a connection, meaning your Apiframe account linked to Make once and reused by every Apiframe module. Click Create a connection.

  2. 02

    Name the connection

    Give the connection a name you will recognize later, for example the client or project the images belong to. This step is optional, but it helps a lot once you run several Apiframe accounts from the same Make organization.

  3. 03

    Authorize and save

    Depending on what the form shows, either approve access on the Apiframe page or paste the key Apiframe gives you into the field. Then click Save. The connection now appears in the module, ready for every scenario that uses Apiframe.

First scenario

Your first scenario with Apiframe in Make

GoalWhen a new prompt arrives in another app, Make asks Apiframe for an image grid and upscales one of its pictures.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Apiframe has no trigger, so the first module comes from the app where your prompts live, like a sheet or a form tool.

  2. 02

    Add Create an image grid

    Click the + on the right of that first module, search for Apiframe and choose Create an image grid. Pick your connection, then map the prompt text coming from the first module.

  3. 03

    Add Upscale an image

    Click the + again and add Upscale an image. Map what the grid module returned so Make knows which grid to work from, then fill the remaining fields Make shows.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and each module shows the bundles it received, a bundle being one item passed along. Check what reached the upscale module.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module run on each bundle counts as one operation on your Make plan.

Modules

What the Apiframe modules do in Make

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

Apiframe1

Create an image grid

Action

In Make“Generates a 2×2 image grid from a prompt. Returns the grid image ID.”

Send a prompt and get back a 2×2 grid of images, plus the ID of that grid. It is the entry point of almost every Apiframe scenario, since Upscale an image then works from the grid it produces.

When to use it
a new product name or campaign brief lands in another app and you want four visual options without typing anything into Apiframe.
Watch out
keep the returned grid ID somewhere, because Get an image grid needs it to find that grid again.
Apiframe2

Create a variation

Action

In Make“Generates four new images from a previous task.”

Four brand new images, drawn from a task you already ran, without writing a new prompt. That is what this module gives you when the first grid is close but not quite there.

When to use it
a reviewer flags a grid as almost right and you want fresh takes on the same idea rather than starting over.
Watch out
it needs a previous task to start from, so place it after a module that produced one.
Apiframe3

Get an image grid

Action

In Make“Retrieves an image grid from your account using an ID.”

With just an ID, this module brings back a grid that already exists in your Apiframe account. Nothing new is generated, so it is the way to reuse earlier work inside a later scenario.

When to use it
the grid ID sits in a sheet row or a database record, and a second scenario needs the images to publish or share them.
Watch out
store the ID somewhere when the grid is created, since this module cannot search by prompt.
Apiframe4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the Apiframe API from your scenario, using the same connection as the other modules. It covers whatever the four dedicated modules leave out.

When to use it
you need an Apiframe feature that has no module of its own in Make, and you know which endpoint handles it.
Watch out
you write the request yourself, so keep the Apiframe API reference open; Make's documentation for this app is limited.
Apiframe5

Upscale an image

Action

In Make“Upscales an image from the image grid.”

Pick one picture out of an image grid and get a larger version of it, ready to use on its own. This is the step that turns four small candidates into one final visual.

When to use it
right after Create an image grid, once you know which of the four images should go to your site, store or ad tool.
Watch out
it works on an existing grid, so place it after a module that gives you one.
Need help

Need help automating Apiframe with Make?

A person reads every message.

FAQ

Apiframe and Make: common questions

01Is the Apiframe Make integration free?
Yes, on the Make side. Apiframe is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, 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, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month. Your Apiframe account itself is a separate matter that Make does not cover.
02What do you need to connect Apiframe to Make?
An Apiframe account and a Make account. Make's documentation lists no specific prerequisite for Apiframe and no dedicated connection steps, so the generic flow applies: add any Apiframe module, click Create a connection, optionally name it, then either authorize Make on the Apiframe page or paste the key Apiframe gives you, and click Save. The same connection is then reused by all five Apiframe modules, including Make an API Call, so you only set it up once per account.
03Can an Apiframe scenario start on its own when something happens?
Not from Apiframe itself, because the app has no trigger module in Make: all five modules are actions. A scenario can still start in two ways. Put another app's trigger first, for example a new row or a new form entry, and the Apiframe modules follow it. Or rely on the schedule of the first module, every 15 minutes by default, down to 1 minute on paid plans. If that first app offers an instant trigger, meaning it calls Make through a webhook, the Apiframe steps run as soon as it fires.
04What if the Apiframe module you need is missing in Make?
Use Make an API Call. It is available for Apiframe and lets a scenario call any endpoint of the Apiframe API with the connection you already set up, so a missing feature does not mean switching tools. Plan a little extra effort, though: Make marks its Apiframe documentation as limited, with no field list and no troubleshooting section, so you will lean on the Apiframe API reference to write the request. The four dedicated modules cover grids, variations, retrieval and upscaling.
05Make or n8n for Apiframe?
It depends on what your team already runs. On Make, Apiframe comes with five modules, four of them for grids, variations, retrieval and upscaling, plus Make an API Call for the rest of the API. Many apps also have an n8n node, so check whether Apiframe has one and which operations it covers before deciding. The fair way to choose is to compare the modules available on each side for your exact use case, and to keep the scenario in the tool where your other automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations