Resources · Make integration

AI Engine Make integrationAutomate AI Engine with Make.

Can Make send your requests to AI Engine without a line of code? Yes: the AI Engine Make integration gives you 4 action modules, two for text and two for images. This page shows how to link your account, build a first scenario and pick the right module.

Try the AI Engine integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the AI Engine Make integration do?

The AI Engine Make integration lets a Make scenario, the automation you build as a chain of modules, send a text or image query to your AI Engine account and pass the answer to the next step. Each module is one brick of that chain, and AI Engine brings four of them, all actions.

Answer incoming requests. A contact form app catches a question, Text Query hands it to AI Engine, and the reply travels on to your inbox or your helpdesk.

Illustrate new content. When a post draft lands in another app, Image Query sends a prompt built from its title, so the visual request no longer depends on someone remembering it.

Try the Custom variants. The two Custom modules sit next to the standard ones. Make does not document how they differ, so run both on the same request with Run once and keep the one whose answer suits you.

What Make does not do here: AI Engine has no trigger, so a scenario always starts with another app or with a schedule, and there is no universal API call module to reach something the four modules skip. If you are still weighing platforms, the n8n vs Make comparison lays out the criteria, and the Make review covers the editor itself. For hands-on practice, see the Make training.

Connect

How do you connect AI Engine to Make?

  1. 01

    Copy your API key

    Log in to your Meow Apps account, open the dashboard, click the Settings menu, then the API section. Copy the API key shown there. You need an active AI Engine account first; the pricing page of AI Engine covers the subscription.

  2. 02

    Open the connection window

    In your Make scenario, add any AI Engine module and click Create a connection. A connection is your AI Engine account linked to Make once, then reused by every AI Engine module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the key you copied, or follow the on-screen instructions, to create the connection. The module can now talk to your account.

First scenario

Your first scenario with AI Engine

GoalWhen a new request arrives in another app, Make sends it to AI Engine as a text query, then as an image query.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that receives your requests, such as a form tool, and set its trigger as the first module.

  2. 02

    Add Text Query

    Click the + on the right of that first module, search AI Engine, choose Text Query and create your connection. Map the request text from the previous module into the query.

  3. 03

    Chain Image Query

    Add one more module with the +, pick Image Query and map the data you want to turn into a visual. Each bundle, one item passing from module to module, gets its own query.

  4. 04

    Test with Run once

    Click Run once, submit one real request in the first app and open the bubbles to read the bundles each module received. Fix the mapping here, before anything runs on its own.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Every module run counts as an operation, the unit Make tracks on your plan.

Modules

What can AI Engine do in Make?

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

AI Engine1

Image Query

ActionIn the docs only

You get an image request sent to your AI Engine account straight from a scenario, with the result handed to the next module so it can be stored or shared.

When to use it
a product sheet or an article reaches another app and needs a visual built from its own title or description.
Watch out
each bundle triggers one query, so a module that outputs many items sends many requests.
AI Engine2

Image Query (Custom)

ActionIn the docs only

A second image module, labelled Custom by Make, sitting next to the standard Image Query. Its name points to a custom version of the same request, nothing more is documented.

When to use it
the standard module ran with Run once and the image is not what you expected.
Watch out
the documentation does not spell out how it differs, so test both on the same bundle before settling.
AI Engine3

Text Query

ActionIn the docs only

Your scenario can ask AI Engine a question in plain text and pass the answer along, to an email, a sheet or a chat message, without copying anything by hand.

When to use it
a customer question lands in your form tool and you want a draft reply prepared before someone reads it.
Watch out
keep a human check on anything sent to customers, since the reply comes from a model.
AI Engine4

Text Query (Custom)

ActionIn the docs only

The Custom counterpart of Text Query: same kind of text request, through a second module whose name signals a custom version.

When to use it
the answer from the standard Text Query misses what you need and you want to compare with a second route.
Watch out
Make lists no official description for it, so rely on a Run once test rather than assumptions.
Need help

Need help automating AI Engine with Make?

A person reads every message.

FAQ

AI Engine and Make: common questions

01Is the AI Engine Make integration free?
Yes, on the Make side. AI Engine is a standard app, so its modules are 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 and files up to 5 MB. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Your AI Engine subscription is separate and handled on the AI Engine pricing page, which this page does not cover.
02What do you need to connect AI Engine to Make?
An active AI Engine account and its API key. Log in to your Meow Apps account, open the dashboard, click Settings, then the API section, and copy the key. In Make, add any AI Engine module, click Create a connection, give it an optional name and paste the key. The same connection then serves all four AI Engine modules, so you only do this once per account, even if you later add more AI Engine modules.
03Does AI Engine trigger Make scenarios in real time?
No, because AI Engine has no trigger module in Make. A scenario always starts elsewhere: with the trigger of another app, such as a form tool, or with the schedule set on the first module, every 15 minutes by default. An instant trigger from another app reacts as soon as its event happens, while a scheduled one waits for the next check. AI Engine then runs as an action inside that flow.
04What if an AI Engine module is missing in Make?
It depends on what you need, but there is no Make an API Call module for AI Engine, so you cannot reach a feature the four modules skip. Start by testing the Custom variants of Text Query and Image Query, which may cover a tailored setup. If they do not, another app may fit the job, or the team can review your case. Make also warns that its AI Engine documentation may contain mistakes, so confirm details with the vendor.
05Make or n8n for AI Engine?
It depends on your criteria rather than on a winner. On Make, AI Engine offers 4 action modules, no trigger and no universal API call module, and every scenario starts from another app or a schedule. Check whether n8n offers an AI Engine node before comparing, then weigh which editor your team already uses and how each one fits your other apps. The n8n vs Make comparison linked above sets out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations