Resources · Make integration

PiAPI/NanoBanana Make integrationAutomate PiAPI/NanoBanana with Make.

What if every new description in your tools came back with its own visuals? The PiAPI/NanoBanana Make integration gives you 3 action modules: images from text, images from an image, and a raw API call. This guide walks a first-time Make user from connection to a live scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PiAPI/NanoBanana Make integration do for you?

The PiAPI/NanoBanana Make integration lets a Make scenario ask PiAPI/NanoBanana for images without you opening any tool. A scenario is the automation you build in Make, a chain of modules; a module is one brick of that chain. Here you get three action modules, and the data that feeds them comes from your other apps.

Product visuals from a written brief. A marketer types a short description in a form or a spreadsheet. Another app's module picks it up, and Generate images from text turns those words into pictures, with no copy and paste between tabs.

Variations of an existing picture. A designer drops a reference photo somewhere Make can read it. Generate images from image uses that picture as the starting point, so a whole series stays consistent with the original.

Anything the two modules skip. Make an API Call reaches any endpoint of the PiAPI/NanoBanana API with the same connection, which covers the requests the listed modules leave out.

Know the limits before you start. Make itself flags this app as having limited documentation, so the directory gives no field list, no official description and no connection guide. The steps below rely on the standard Make gestures only. If a run fails, the Make troubleshooting guide is the place to start, and the Make pricing page explains how operations add up on your plan. Weighing another tool? The n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect PiAPI/NanoBanana to Make?

  1. 01

    Add a module and open the connection

    In your scenario, add any PiAPI/NanoBanana module, then click Create a connection. A connection is your PiAPI/NanoBanana account linked to Make once and reused by all three modules, so you only do this part a single time.

  2. 02

    Name it so you can find it later

    Giving the connection a name is optional, yet it helps as soon as you own more than one account. A label such as the client or the project tells you at a glance which account a scenario spends when you open it later.

  3. 03

    Authorize Make and save

    Depending on what Make shows, either approve access on the PiAPI/NanoBanana page or paste the key the app gives you. Then click Save. The connection now appears in the module, ready for your first test.

First scenario

Your first scenario with PiAPI/NanoBanana

GoalWhen a new description arrives in another app, Make asks PiAPI/NanoBanana to generate images from it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since PiAPI/NanoBanana has no trigger, the first module comes from the app where your descriptions live, a form tool or a spreadsheet for example.

  2. 02

    Set up the starting module

    Search that other app by name, pick the module that returns new entries and connect its account. Once connected, Make lists the sheets or objects it can read, so you choose instead of typing.

  3. 03

    Add Generate images from text

    Click the + on the right of the first module, search PiAPI/NanoBanana and pick Generate images from text. Select the connection you created earlier, or create it now.

  4. 04

    Map the description

    Fill the module by mapping the description from the previous module rather than typing a fixed sentence. Each bundle, meaning one item passed along the chain, then carries its own text to PiAPI/NanoBanana.

  5. 05

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received and check that the image request left with the right text.

  6. 06

    Schedule and switch on

    On the first module, open the clock: a new scenario checks every 15 minutes by default. Keep that or pick another interval your plan allows, then switch the scenario on.

Modules

What each PiAPI/NanoBanana module does

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

PiAPI/NanoBanana1

Generate images from image

ActionIn the docs only

You get fresh images built from a picture you already have, which keeps a series close to its reference.

When to use it
pick it over the text module when the look of an existing photo or mockup matters more than a description, for instance when a catalog needs variants of one shot.
Watch out
Make documents no fields for this module, so run it once and read the bundles before building anything around its output.
PiAPI/NanoBanana2

Generate images from text

ActionIn the docs only

Written words go in, pictures come out: this is the module that lets a sentence in a sheet or a form become a visual without anyone opening PiAPI.

When to use it
choose it when you start from a brief rather than a picture, like a blog post title or a product line waiting for its illustration.
Watch out
each run on one bundle counts as one operation on your Make plan, so filter the incoming rows first.
PiAPI/NanoBanana3

Make an API Call

ActionIn the docs only

This one reaches any endpoint of the PiAPI/NanoBanana API through your existing connection, so nothing needs a second login.

When to use it
reach for it only when neither generation module covers the request you have in mind, for example an endpoint the two others do not expose.
Watch out
you need the API reference of PiAPI itself, since Make's own documentation for this app is limited.
Need help

Need help automating PiAPI/NanoBanana with Make?

A person reads every message.

FAQ

PiAPI/NanoBanana and Make: common questions

01Is the PiAPI/NanoBanana Make integration free?
Yes, on the Make side. PiAPI/NanoBanana is a standard app, available from the Free plan onward. That plan gives you 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and lift the active scenario cap. Usage is counted in operations, one per module run on one bundle. The price of the PiAPI service itself is a separate matter this page does not cover.
02What do you need to connect PiAPI/NanoBanana to Make?
A PiAPI/NanoBanana account and a Make account. The Make documentation lists no specific prerequisite for this app. You add one of its modules, click Create a connection, optionally name it, then either authorize Make on the app page or paste the key the app gives you, and click Save. The connection is reused by the three modules, so you set it up only once per account. If the window does not match what you expect, compare it with your PiAPI account settings.
03Does PiAPI/NanoBanana trigger a Make scenario in real time?
No, because the app has no trigger module at all. All three modules are actions, so something else has to start the scenario. You can open it with an instant trigger from another app, which that app fires through a webhook as soon as something happens. Or you can rely on scheduling, the clock on the first module, which runs a new scenario every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval, while paid plans go down to 1 minute.
04What if the PiAPI/NanoBanana module you need is missing in Make?
Use Make an API Call. With this module, any endpoint of the PiAPI/NanoBanana API can be called from the scenario, reusing the same connection as the two generation modules. You then build the request yourself from the PiAPI reference, which matters here because Make states it cannot yet provide complete documentation for this app. Expect to test with Run once more often than on a well documented app, and read the bundles returned at each step.
05Should you use Make or n8n for PiAPI/NanoBanana?
It depends on the criteria that matter to you, not on a winner. On Make, you get 3 modules: two for image generation and a raw API call that covers the rest, all behind one connection and available from the Free plan. This page does not document whether n8n offers a node for this app, so check its catalog before comparing. Then weigh how each tool fits the apps already in your stack and the way your team likes to build automations.