Resources · Make integration

OpenRouter Make integrationAutomate OpenRouter with Make.

What if every text your tools collect got an AI answer without you copying a single prompt? The OpenRouter Make integration gives you 4 modules: 3 actions and 1 search. It suits marketers and ops leads who already use OpenRouter. This page walks you through the connection, a first scenario and each module.

Try the OpenRouter integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the OpenRouter Make integration do for you?

The OpenRouter Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) send a request to an AI model through OpenRouter and pass the answer to your other apps. Think of OpenRouter as a switchboard: hundreds of AI models sit behind one account. Changing model is a choice in the module, not a new connection.

Article summaries on autopilot. A content team collects links in a sheet. Each new row goes to Create a Chat Completion, and the short summary lands back in the same row, ready for the newsletter.

Personal copy for each lead. A sales team gets form entries from a landing page. The scenario asks a model for an opening message that uses the lead's own answers. If one model is unavailable, Create a Chat Completion (with Fallback) lets you name backup models in advance.

A model picked on purpose. Before you commit, List Models shows what OpenRouter currently offers, so you can compare options and choose the most cost-effective one for the task.

One honest limit: OpenRouter has no trigger in Make, so it never starts a scenario on its own. Another app, or the schedule, has to start it. If you also work with n8n, the OpenRouter n8n integration covers the same service, and n8n vs Make helps you weigh both tools. New to the editor? Make training starts from zero.

Connect

How do you connect OpenRouter to Make?

  1. 01

    Add an OpenRouter module

    In your scenario, add any OpenRouter module, for example Create a Chat Completion. Make then asks for a connection, meaning your OpenRouter account linked to Make once. Click Create a connection.

  2. 02

    Name it and give access

    Give the connection a clear name if you like, useful when a client and your own team each have an account. Then do what the window asks: authorize Make on OpenRouter's page, or paste the key that OpenRouter gives you.

  3. 03

    Save and reuse

    Click Save. The connection now appears in the dropdown of every OpenRouter module, including Make an API Call, so you never have to repeat this step inside the same scenario.

First scenario

Your first scenario: an AI reply for every new entry

GoalWhen a new entry arrives in another app, Make asks an OpenRouter model for a reply and sends the text on.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the trigger of the app where your texts arrive: a form tool, a sheet or your inbox app.

  2. 02

    Add the OpenRouter action

    Click the + on the right of that first module, search for OpenRouter and choose Create a Chat Completion. Create the connection as shown above.

  3. 03

    Choose the model and map the text

    Select the AI model, then write your prompt and drop in the text coming from the first module. That text travels as a bundle, one item passed from a module to the next.

  4. 04

    Send the answer somewhere

    Add one more module after OpenRouter, from the app where the answer belongs, and map the reply into it. A sheet row or a draft message both work well.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can read the model's answer before anything goes live.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and turn the scenario on. Each module run on one bundle counts as an operation on your plan.

Modules

What each OpenRouter module does

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

OpenRouter1

Create a Chat Completion

Action

In Make“Creates a new chat completion with a selected AI Model and automatic fallback if enabled.”

This is the everyday module: it sends your prompt to the AI model you select and returns the reply as a bundle you can map into the next module. Automatic fallback is available here too, when you switch it on.

When to use it
most text jobs, like summarizing an article, rewriting a product note or drafting a reply to a customer email.
Watch out
every run is one operation in Make, so test with Run once on a single item first.
OpenRouter2

Create a Chat Completion (with Fallback)

Action

In Make“Creates a chat completion with specifically defined fallback models.”

Same idea as the standard chat module, with one difference that matters: you write down yourself which backup models OpenRouter should use, instead of relying on the automatic option.

When to use it
a scenario that feeds customers or a live channel, where you want to control exactly which models may answer.
Watch out
a backup model may word things differently from your first choice, so read a few Run once results before customers see them.
OpenRouter3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your way out when the three other modules do not cover a need. It calls any endpoint of the OpenRouter API while reusing the connection you already created, so there is no key to handle twice.

When to use it
an OpenRouter feature you read about in their API documentation and cannot find in the module list.
Watch out
you write the request yourself, so keep the OpenRouter API reference open next to the editor.
OpenRouter4

List Models

Search

In Make“Returns a list of available models.”

A search module that returns the models OpenRouter currently makes available. Each model comes out as its own bundle, which means the next module runs once per model.

When to use it
before choosing a model for a new scenario, or to keep a sheet of available options up to date for your team.
Watch out
the list can be long, and every bundle passed to a following module costs an operation; filter it before writing anything.
Need help

Need help automating OpenRouter with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the OpenRouter Make integration free?
Yes, on the Make side. OpenRouter is a standard app, so it works on the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, 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 remove the cap on active scenarios. What OpenRouter itself charges for model usage is a separate question, answered on OpenRouter's side.
02What do you need to connect OpenRouter to Make?
An OpenRouter account and a Make account. No specific prerequisite is documented for this app. You add an OpenRouter module, click Create a connection, give it a name if you want, then authorize Make or paste the key OpenRouter provides, depending on what the window asks. Click Save and the same connection works for all four modules, including Make an API Call. If several people share one Make account, name each connection after its owner.
03Does OpenRouter trigger a Make scenario in real time?
No, because OpenRouter has no trigger module in Make. It only acts once a scenario is running. You start the scenario another way: with the trigger of another app, such as a new form entry or a new row, or with the schedule on the first module. A new scenario runs every 15 minutes by default. On the Free plan the shortest interval is 15 minutes, and paid plans go down to 1 minute. OpenRouter then processes whatever the first module passes along.
04What if an OpenRouter module is missing in Make?
Use Make an API Call. It reaches any endpoint of the OpenRouter API with the connection you already set up, so it covers what Create a Chat Completion, the fallback version and List Models do not. You build the request yourself, which takes a little more care than a ready-made module. No numeric limit is documented for this app. When a model fails you, the fallback module lets you name backup models ahead of time.
05Should you use Make or n8n for OpenRouter?
It depends on where your other automations already live. OpenRouter exists on both tools: Make gives you the four modules described on this page, and n8n has its own OpenRouter node with a dedicated page on this site. Neither choice changes what OpenRouter can do. If your team already builds scenarios in Make, stay there and reuse your connections. If your workflows run in n8n, use the node there. The comparison page on this site lays out the differences between the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations