Automate CherryIN With Make: 4 Modules, Zero Code Needed

What you can automate

What can the CherryIN Make integration do?

The CherryIN Make integration lets a Make scenario (the automation you build, a chain of modules) call your CherryIN account without code. You get 4 modules: three actions, including a generic API call, and one search. None of them is a trigger, so something else has to start the scenario.

A reply drafted for every new request. Another app starts the scenario, and Create a Chat Completion sends the text you mapped to CherryIN. The result comes back as a bundle, one item passed to the next module, ready to be stored or sent.

A check on what your account offers. List Models is a search, so it can return zero, one or several bundles. Put it at the start of a scenario when you want to see what is available before you pick a value in the next module.

Anything the listed modules skip. Make an API Call reaches any endpoint of the CherryIN API with the connection you already set up. Create a Response is the other ready-made action when your call fits it.

Know the limits before you build. The CherryIN documentation on Make says it was generated with AI and may contain mistakes, so verify important details with CherryIN. If a module behaves oddly, Make troubleshooting covers the common errors. To weigh the platforms, read n8n vs Make, and for plan details see Make pricing.

Connect

How do you connect CherryIN to Make?

01
Collect your two credentials
Log in to CherryIN and open the user dashboard. In the API credentials or security section, copy the API key. Then go to the order center and copy the order number tied to your active subscription.
02
Open the connection window
In Make, add any CherryIN module to your scenario and click Create a connection. A connection is your CherryIN account linked to Make once, then reused by every CherryIN module.
03
Name it and paste the details
The Connection name field is optional, but a clear name helps when you have several accounts. Paste the credentials you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario with CherryIN

GoalOn each scheduled run, Make lists the models your CherryIN account can reach and sends one chat completion request per model, so you can compare their answers side by side.

01
Create a blank scenario
Go to the Scenarios page, create a new scenario and click the big +. That first slot is where your scenario starts, and here it will be a CherryIN search.
02
Add List Models
Search for CherryIN, pick List Models and click Create a connection to link your account. Fill the module fields Make shows you.
03
Chain the chat completion
Click the + on the right of List Models and add Create a Chat Completion. Map the model from the previous module. List Models returns one bundle per model, so the completion runs once for each.
04
Test with Run once
Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received. Fix the mapping here, before anything runs on its own.
05
Schedule and switch it on
Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Set the schedule you want, then switch the scenario on.

Modules

Every CherryIN module in Make

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

CherryIN1

Create a Chat Completion

ActionIn the docs only

This action sends a chat completion request to CherryIN and hands the result to the next module as a bundle. It works on one item per run, so one incoming message means one request.

When to use it

a support form or a shared inbox feeds the scenario and you want a draft answer stored next to each message.

Watch out

every run of the module counts as an operation on your Make plan, so test with Run once before you schedule.

CherryIN2

Create a Response

ActionIn the docs only

Here you get a second ready-made action for asking CherryIN to generate a response, without building the call yourself. Like any action, it acts on one bundle at a time.

When to use it

you want a second way to generate text and compare it with the chat completion during a Run once test.

Watch out

Make shows no description for this module, so ask CherryIN how it differs from the chat completion before you rely on it.

CherryIN3

List Models

SearchIn the docs only

With this search you see which models your CherryIN account can reach, straight inside Make. A search can return zero, one or several bundles, one per result.

When to use it

at the start of a scenario, to check what is available before a completion module uses a value from the list.

Watch out

several bundles mean the modules after it run once per bundle, and each run is an operation, so filter before you chain an action.

CherryIN4

Make an API Call

ActionIn the docs only

This module lets you call any endpoint of the CherryIN API from your scenario, reusing the connection you already created. It covers what the three other modules leave out.

When to use it

you need an endpoint or an option that none of the ready-made CherryIN modules exposes.

Watch out

you build the request yourself, so read the CherryIN API reference first, and remember that the Make documentation for this app may contain mistakes.

Need help

Need help automating CherryIN with Make?

A person reads every message.

FAQ

CherryIN and Make: common questions

01Is the CherryIN Make integration free?

Yes, on the Make side. CherryIN is a standard app, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) go down to 1 minute between runs and count usage in credits each month. You still need an active CherryIN account with an API key, and CherryIN's own pricing is set on its side.

02What do you need to connect CherryIN to Make?

You need an active CherryIN account and an API key. From the user dashboard, open the API credentials or security section and copy the key, then copy the order number of your active subscription from the order center. In Make, add a CherryIN module, click Create a connection, give it a name if you want, and paste those details. The connection is then shared by all 4 CherryIN modules in your scenarios.

03Does CherryIN trigger Make scenarios in real time?

No. CherryIN has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario by itself. You have two ways to start one. Set a schedule on the first module: a new scenario runs every 15 minutes by default, and paid plans can go down to 1 minute. Or put a trigger from another app first, such as a form or an inbox, and add the CherryIN modules after it.

04What if a CherryIN module you need is missing in Make?

Use Make an API Call. It can reach any endpoint of the CherryIN API and reuses the connection you already created, so there is nothing new to set up. Read the CherryIN API reference to build the request, then test it with Run once. Keep in mind that the CherryIN documentation on Make says it was generated with AI and may contain mistakes, so confirm important details with CherryIN before relying on them.

05Should you use Make or n8n with CherryIN?

It depends on the criteria you care about, not on a winner. On Make, CherryIN comes with 4 modules: two generation actions, a model search and a generic API call, all set up through one connection. The same app often has an n8n node too, so check whether CherryIN has one there. Then compare the modules each platform offers for your case, how you prefer to build, and your plan limits before you choose.

Collect your two credentials

Open the connection window

Name it and paste the details

Create a blank scenario

Add List Models

Chain the chat completion

Test with Run once

Schedule and switch it on

Need help automating CherryIN with Make?