Automate Runware.AI With Make: 3 Image Modules, Zero Code

What you can automate

What can the Runware.AI Make integration do for you?

The integration lets Make send requests to Runware.AI for you. You build a scenario, the automation Make runs for you, and one of its modules, the building blocks of that scenario, asks Runware.AI to create images from a prompt or from a picture you already have. No code is involved: you connect your account once with an API key.

Visuals from a content plan. A marketing team keeps its post ideas in a spreadsheet. Each new line becomes a prompt for Generate Images from Text Prompt, so a draft visual exists before anyone opens a design tool.

Variations of a product photo. An online shop already has a clean shot of each item. Generate Images from Existing Image starts from that shot and produces new versions, useful when the catalog needs several looks of the same product.

Anything the listed modules skip. Runware.AI exposes more through its API than the two image modules cover. Make an API Call reaches those endpoints with the same connection, as long as you know which request to send.

What Make does not do here: the app has no trigger, so Runware.AI never starts a scenario by itself. Something else has to kick it off, another app or the schedule of the scenario. The Make documentation for this app is also flagged as AI-generated, so check important details against the Runware.AI docs. If the same app exists in n8n and you hesitate between the two tools, the n8n vs Make comparison lays out the criteria. To plan your budget, read Make pricing, and for a guided start, see Make training.

Connect

How do you connect Runware.AI to Make?

01
Create an API key in Runware.AI
In your Runware.AI account, open the API Keys page from the dashboard and click Create Key. Give the key a few details, generate it, then copy the value shown on screen. You need an active Runware.AI account for this.
02
Add a Runware.AI module in Make
In your scenario, add any Runware.AI module and click Create a connection. The Connection name field is optional; a clear name helps when you later run several accounts side by side.
03
Paste the key and save
Paste the API key you copied from Runware.AI, or follow the on-screen instructions, and save. The connection, your Runware.AI account linked to Make, is then reused by every Runware.AI module you add.

First scenario

Your first scenario with Runware.AI

GoalWhen a new prompt lands in another app, Make asks Runware.AI to generate an image from it.

01
Create the scenario
From the Scenarios page, create a new scenario and click the +. Pick the app where your prompts live, for example a spreadsheet, as the first module.
02
Add Generate Images from Text Prompt
Click the + on the right of the first module, search Runware.AI and choose Generate Images from Text Prompt. Click Create a connection and paste your API key.
03
Map the prompt
Fill the module fields and map the prompt text from the previous module. Each bundle, one item passed between modules such as one row, becomes one request to Runware.AI.
04
Test with Run once
Click Run once to execute the scenario one time. Then read the bundles each module received and check that Runware.AI sent images back.
05
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as an operation, the unit Make tracks on your plan.

Modules

What the Runware.AI modules do

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

Runware.AI1

Generate Images from Existing Image

Action

In Make“Generates images from an existing image.”

You get fresh images built on a picture you already own, so the result keeps a link with your starting point instead of appearing from nothing. It is an action module, which means it handles one bundle each time it runs.

When to use it

a product shot or a sketch needs new versions and you want the output to stay close to the original.

Watch out

the module needs the source image from an earlier step, so place it after the module that brings that picture into the scenario.

Runware.AI2

Generate Images from Text Prompt

Action

In Make“Generates images from text prompts.”

Write a sentence, receive an image: this module turns a text prompt into generated visuals, with no picture needed at the start. The prompt can come from any earlier module, a form answer or a spreadsheet cell.

When to use it

ideas already live as text somewhere and you want a first visual for each one without drawing anything.

Watch out

every bundle sent in is a separate request, so a long list of rows means as many generations and as many operations.

Runware.AI3

Make an API Call

Action

In Make“Performs an arbitrary authorised API call.”

This module opens the rest of the Runware.AI API to your scenario, reusing the connection you already created. It fills the gap whenever the two image modules do not offer the request you need.

When to use it

Runware.AI documents an endpoint that has no dedicated module in Make and you know the request it expects.

Watch out

you build the call yourself, so read the Runware.AI API documentation first and test with Run once before switching the scenario on.

Need help

Need help automating Runware.AI with Make?

A person reads every message.

FAQ

Runware.AI and Make: common questions

01Is the Runware.AI Make integration free?

Yes, on the Make side. Runware.AI is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and raise the run time to 40 minutes. Runware.AI itself needs its own active account and subscription, which Make does not cover; check the Runware.AI pricing page for that part.

02What do you need to connect Runware.AI to Make?

An active Runware.AI account and an API key. You create the key from the API Keys page of your Runware.AI dashboard with the Create Key button, then copy the value displayed. In Make, add a Runware.AI module, click Create a connection, optionally name it, and paste the key. That single connection then serves every Runware.AI module in your scenarios, so you only do this setup once per account. If Make refuses the key, first check that your Runware.AI account is still active.

03Does the Runware.AI Make integration react in real time?

No, because Runware.AI has no trigger in Make. The app only answers when a scenario calls it. To start a scenario, put another app first, such as a sheet or a form, or rely on the schedule of the scenario, which runs every 15 minutes by default. On a paid plan the interval can go down to 1 minute. Runware.AI modules then run as actions right after whatever opened the flow.

04What if a Runware.AI module is missing in Make?

Use Make an API Call. The Runware.AI app includes this module, which can call any endpoint of the Runware.AI API with the connection you already set up. It suits requests beyond the two image modules. Keep in mind that the Make documentation for this app is marked as AI-generated and may contain mistakes, so confirm important details in the official Runware.AI documentation before relying on them. Test each call with Run once first.

05Should you use Make or n8n for Runware.AI?

It depends on the tool you already run. Many apps also have a node in n8n, so check whether Runware.AI is one of them before choosing. In Make, you get 3 modules: two for image generation and one open API call, all behind a single connection built from your API key. Compare how each tool fits your team and your existing scenarios rather than the app alone; the choice rarely depends on Runware.AI itself.

Create an API key in Runware.AI

Add a Runware.AI module in Make

Paste the key and save

Create the scenario

Add Generate Images from Text Prompt

Map the prompt

Test with Run once

Schedule and switch on

Need help automating Runware.AI with Make?