Resources · Make integration

SOLAPI Make integrationAutomate SOLAPI with Make.

What if every new signup got its text message without anyone typing it? The SOLAPI Make integration gives you 7 modules: 3 triggers and 4 actions. This guide is for teams that already send messages with SOLAPI and walks you from the connection to a working scenario.

Try the SOLAPI integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SOLAPI Make integration do for you?

The SOLAPI Make integration links your SOLAPI account to Make so messages go out on their own. You build a scenario, the automation you assemble in Make, out of modules: each module is one brick, either a trigger that starts the flow or an action that does something in SOLAPI, such as sending a text or a KakaoTalk message.

Welcome text for new leads. A form in another app collects a phone number. Make passes it to Add Contact to Address Book, then Send a Text Message greets the person. Nobody copies numbers by hand anymore.

KakaoTalk follow-up for shoppers. An online store that talks to customers on KakaoTalk can hand the order details to Send a Kakao FriendTalk, so the buyer reads the message in the messaging app they already use.

Keeping an eye on delivery. Watch New Message Report and Watch New Group Report bring SOLAPI's reports into Make, where you can forward them to a sheet or to your team chat. Watch New Commerce Event does the same for commerce events.

The limits: SOLAPI's Make documentation gives no numeric cap, and its 3 triggers are scheduled, so Make checks for news on the scenario's schedule rather than the moment a report appears. When a listed module falls short, Make an API Call reaches the rest of the API. Many apps also have an n8n node, and our n8n vs Make comparison lays out the criteria. To learn the editor step by step, see the Make training, and for a costed plan, the Make pricing page.

Connect

How do you connect SOLAPI to Make?

  1. 01

    Add a SOLAPI module

    You need a SOLAPI account first. In your Make scenario, click the +, search for SOLAPI, pick any of its modules, then click Create a connection. A connection is your SOLAPI account linked to Make once and reused by every SOLAPI module.

  2. 02

    Name the connection

    The Connection name field is optional. A clear name like the brand or the sender account helps the day you link a second SOLAPI account and need to tell them apart in a dropdown.

  3. 03

    Save and confirm access

    Click Save. If SOLAPI asks you to sign in, authenticate your account and confirm the access it requests. The connection then shows up in the module, and Make can start reading what your account holds.

First scenario

Your first scenario with SOLAPI and Make

GoalWhen a form in another app receives a new signup, Make adds the person to your SOLAPI address book and sends a welcome text.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module. Pick the form app your signups come from and connect it.

  2. 02

    Add the contact in SOLAPI

    Click the + on the right of the form module, search SOLAPI and choose Add Contact to Address Book. Click Create a connection, then map the name and phone number from the form.

  3. 03

    Send the welcome text

    Add a second SOLAPI module, Send a Text Message. It reuses the same connection. Map the phone number again and write a short greeting that pulls the first name from the form.

  4. 04

    Test with Run once

    Submit a test signup, then click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one signup. Check that the text reached your own phone.

  5. 05

    Schedule and switch on

    Set the schedule on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Switch the scenario on and new signups get their text.

Triggers

What can start a SOLAPI scenario?

3 modules start a scenario when something happens in SOLAPI. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SOLAPI as soon as it happens.

SOLAPI1Watch New Commerce Event

Watch New Commerce Event

triggerIn the docs only

This trigger starts your scenario when SOLAPI records a new commerce event, so a sale-related signal on the SOLAPI side can feed the rest of your tools. The documentation lists the module without describing what counts as a commerce event, so run a test before relying on it.

How it fires
scheduled. Make checks the app on the scenario's schedule, shown by the clock badge on the module.
When to use it
when your commerce activity flows through SOLAPI and you want each new event copied to a sheet or passed to your team.
Watch out
click Run once and read the bundle before mapping anything, since the documentation gives no field list.
SOLAPI2Watch New Group Report

Watch New Group Report

triggerIn the docs only

Watch New Group Report hands you each new group report from SOLAPI, which is handy when you send to many people at once and want the outcome of the batch somewhere your team looks. The documentation only names the module, so the exact content of a report is something you discover in your first test.

How it fires
scheduled. Make checks the app on the scenario's schedule, not the second a report exists.
When to use it
after a campaign send, to log each group result in a spreadsheet.
Watch out
each run uses operations, the unit Make counts on your plan.
SOLAPI3Watch New Message Report

Watch New Message Report

triggerIn the docs only

Pick this trigger to follow single messages rather than whole groups: every new message report in SOLAPI becomes a bundle your scenario can act on. That makes it the finer-grained sibling of Watch New Group Report, useful when one failed text matters to you.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
when a support or sales team needs to know which individual message came back with a report worth reading.
Watch out
the documentation does not describe the report fields, so inspect a real bundle after Run once.
Modules

What can SOLAPI do inside a scenario?

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

SOLAPI1

Add Contact to Address Book

ActionIn the docs only

Your SOLAPI address book fills itself: this action saves a person from another app as a contact, ready for your next send. It spares you exporting lists and importing them again.

When to use it
right after a signup, a booking or a purchase in another tool, before any message goes out.
Watch out
the documentation lists the module without its fields, so check in the editor which address book and details Make offers.
SOLAPI2

Make an API Call

ActionIn the docs only

When none of the listed modules does what you need, this one reaches any endpoint of the SOLAPI API with the connection you already set up. It is the escape hatch, not the starting point.

When to use it
for a SOLAPI feature that has no dedicated module in Make, once you have found the endpoint in SOLAPI's API reference.
Watch out
you write the request yourself, so a wrong path or body simply fails; test it with Run once.
SOLAPI3

Send a Kakao FriendTalk

ActionIn the docs only

With this action your scenario sends a KakaoTalk FriendTalk message through SOLAPI, reaching customers inside the messaging app instead of by text. It fits brands whose audience lives on KakaoTalk.

When to use it
to confirm an order or share a follow-up with a customer who already chats with your brand on KakaoTalk.
Watch out
the documentation gives no detail on the sender setup this needs, so confirm it on the SOLAPI side before switching the scenario on.
SOLAPI4

Send a Text Message

ActionIn the docs only

Here is the module most scenarios end on: it sends a text through your SOLAPI account, with content you build from data earlier in the flow, such as a first name or an order number.

When to use it
when the person you want to reach has a phone number but no KakaoTalk relationship with you, for reminders, confirmations or a welcome.
Watch out
every bundle that reaches this module sends one message, so test with your own number first.
Need help

Need help automating SOLAPI with Make?

A person reads every message.

FAQ

Questions about the SOLAPI Make integration

01Is the SOLAPI Make integration free?
Yes, on the Make side. SOLAPI is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 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, with usage counted in credits each month. Anything your SOLAPI account itself costs is a separate matter from Make, and this page does not cover it.
02What do you need to connect SOLAPI to Make?
A SOLAPI account and a Make account. Add any SOLAPI module to a scenario, click Create a connection, give the connection a name if you wish, then click Save. If SOLAPI prompts you, sign in and confirm the access it requests. The connection is created once and every SOLAPI module in your scenarios reuses it. The documentation lists no other prerequisite, so there is no plugin to install on the SOLAPI side before you start.
03Do the SOLAPI triggers in Make fire in real time?
No. The 3 SOLAPI triggers are scheduled: Make checks your account on the scenario's schedule, every 15 minutes by default on a new scenario. On the Free plan 15 minutes is also the shortest interval, while paid plans go down to 1 minute. A report or commerce event therefore reaches your scenario at the next check, not the instant it happens in SOLAPI. If speed matters, shorten the schedule on a paid plan, keeping in mind that each check uses operations.
04What if a SOLAPI module is missing in Make?
Use Make an API Call. It calls any endpoint of the SOLAPI API from your scenario with the same connection, which covers what the 7 listed modules leave out. You have to write the request yourself from the SOLAPI API reference, so test it with Run once before switching the scenario on. The SOLAPI documentation in Make gives no numeric limit, so the practical limits are those of your Make plan, such as the execution time per run.
05Should you use Make or n8n for SOLAPI?
It depends on the tool your team already uses. Many apps also exist as an n8n node, so check whether SOLAPI does before you compare. In Make, you get 7 ready modules, 3 scheduled triggers and 4 actions, plus Make an API Call for anything else. If your other automations already live in Make, keeping SOLAPI there saves you a second tool to maintain. The comparison page linked above sets out the criteria without declaring a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations