Resources · Make integration

MessengerOS Make integrationAutomate MessengerOS with Make.

Can Make send your MessengerOS emails and texts for you? Yes. The MessengerOS Make integration gives you 5 action modules to grow contact lists and send messages. This guide shows you how to plug in your account and build a first working scenario.

Try the MessengerOS integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the MessengerOS Make integration do for you?

The MessengerOS Make integration lets a Make scenario (the automation you build in Make, a chain of steps) act inside your MessengerOS account. It can add a contact to an email list or a phone number list, send an email, send an SMS, or call the MessengerOS API directly. Everything it does is an action: it never starts a scenario by itself.

Welcome every new signup. A contact form in another app starts the scenario, Add a Contact to Email List files the person in MessengerOS, and Send an Email greets them right after. Each step is a module, one brick of the scenario.

Text the people who asked for texts. When a customer leaves a phone number in your shop or CRM, Add a Contact to Phone Number list stores it, and Send an SMS confirms what they signed up for.

Reach what the menu does not show. Make an API call reuses your MessengerOS connection to hit any endpoint of its API, so a missing module does not block you.

Be aware of the gaps. MessengerOS has no trigger in Make, so something else has to start the scenario: another app, or the scenario's own schedule. The official documentation is also thin, and Make says so itself: there is not enough public information about MessengerOS for a complete guide. Test with Run once before you trust any mapping. If you want a hand, the Make training walks through these basics, and our Make agency builds scenarios like this one.

MessengerOS may also have an n8n node. If you are weighing the two tools, read n8n vs Make before you choose.

Connect

How do you connect MessengerOS to Make?

  1. 01

    Add a MessengerOS module

    In your scenario, click the + and search for MessengerOS. Pick any of its modules, for example Send an Email, then click Create a connection. A connection is your MessengerOS account linked to Make once and reused by every MessengerOS module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when you run several accounts. Then follow what the window asks: either approve Make on the MessengerOS page, or paste the key MessengerOS gives you. The documentation does not say which of the two applies.

  3. 03

    Save and check the module

    Click Save. The module now uses your connection. From here on, every MessengerOS module you add in any scenario can pick this same connection from the list, no new login needed.

First scenario

Your first scenario with MessengerOS

GoalWhen someone signs up in your form app, Make adds them to a MessengerOS email list and sends them a welcome email.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since MessengerOS has no trigger, start with the app where your signups arrive, such as your form tool.

  2. 02

    Add the contact to a list

    Click the + on the right of that first module, search MessengerOS and choose Add a Contact to Email List. Connect your account, then map the email address coming from the form into the module.

  3. 03

    Send the welcome email

    Add one more module with the +, this time Send an Email. Map the same address from the form, then write the message you want every new contact to receive.

  4. 04

    Test with Run once

    Click Run once and submit a test entry in your form. Open each module to read the bundle it received, one bundle being one item passed along, here one signup.

  5. 05

    Schedule and switch on

    On the first module, set the schedule. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Then turn the scenario on.

Modules

What MessengerOS can do in Make

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

MessengerOS1

Add a Contact to Email List

ActionIn the docs only

Files a person into one of your MessengerOS email lists, so they are ready to receive your next campaign without anyone copying addresses by hand.

When to use it
right after a signup form, a purchase or a webinar registration lands in another app and you want that person on the matching list.
Watch out
the documentation lists no fields, so run the scenario once and check which details MessengerOS actually stored.
MessengerOS2

Add a Contact to Phone Number list

ActionIn the docs only

Puts a contact into a MessengerOS phone number list rather than an email list, so your mobile numbers stay grouped apart from your email addresses.

When to use it
your checkout or CRM collects mobile numbers from customers who agreed to receive texts, and you want those numbers grouped before you message them.
Watch out
pick this one and not the email list module when the data you map is a phone number, or the contact ends up in the wrong place.
MessengerOS3

Make an API call

ActionIn the docs only

Lets your scenario reach any endpoint of the MessengerOS API while reusing the connection you already created, so nothing is out of reach just because no ready module exists.

When to use it
you need something the four other modules do not cover, such as a MessengerOS feature you know exists in your account.
Watch out
you write the request yourself, so you need the API documentation MessengerOS gives you; the Make doc for this app does not cover it.
MessengerOS4

Send an Email

ActionIn the docs only

Sends an email through your MessengerOS account from inside a scenario, as soon as the scenario reaches it, after the module that started the run.

When to use it
a one-to-one message tied to an event, like a welcome note after signup or a confirmation after an order.
Watch out
the module runs once per bundle it receives, and each run counts as one operation on your Make plan, so ten contacts in means ten emails out.
MessengerOS5

Send an SMS

ActionIn the docs only

Fires a text message from MessengerOS to a phone number your scenario provides, which suits short, urgent news better than an email.

When to use it
a delivery goes out, an appointment is booked or a payment fails, and the customer should know on their phone.
Watch out
map the phone number from the previous module rather than typing one in, or every run will text the same person.
Need help

Need help automating MessengerOS with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the MessengerOS Make integration free?
Yes, on the Make side. MessengerOS is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs them at most every 15 minutes, stops a run after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Make counts every module run as one operation against your monthly credits. What MessengerOS itself charges is a separate question for MessengerOS.
02What do you need to connect MessengerOS to Make?
A MessengerOS account and a Make account. The documentation lists no special prerequisite. Add any MessengerOS module, click Create a connection, name it if you want, then either approve Make on the MessengerOS page or paste the key MessengerOS provides, and click Save. Make itself says its MessengerOS documentation is incomplete for lack of public information, so if the window asks for a value you cannot locate, check your MessengerOS settings or contact its support.
03Does the MessengerOS Make integration react in real time?
No, because it has no trigger at all. All 5 MessengerOS modules are actions, so they only run once something else starts the scenario. You have two options. Begin with a trigger from another app, such as a form or a shop, and MessengerOS acts on what that app sends. Or rely on the schedule on the first module, every 15 minutes by default on a new scenario, and 1 minute at the shortest on a paid plan.
04What if the MessengerOS module you need is missing in Make?
Use Make an API call. It sends a request to any endpoint of the MessengerOS API through the connection you already set up, so there is no second login. You will need API documentation from MessengerOS itself to write that request, because the Make documentation for this app is limited and describes no fields. Test each call with Run once and read the returned bundle before you switch the scenario on. If the API cannot do it either, look at another messaging app.
05Should you use Make or n8n for MessengerOS?
It depends on the tool your team already works in. In Make, MessengerOS offers 5 action modules, no trigger, and Make an API call for everything else. The same app may also have an n8n node, so check what that node covers before you decide. Compare the actions you actually need on each side, and keep in mind that on Make, something outside MessengerOS always has to start the scenario.
Same platform

Other docs you might need on this stack.

Browse all integrations