Resources · Make integration

Megaapi Start Make integrationAutomate Megaapi Start with Make.

Could your messages, files and groups on Megaapi Start run on their own? The Megaapi Start Make integration gives you 20 modules, 18 actions and 2 searches. This page shows what each one is for and walks you through a first scenario.

Try the Megaapi Start integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Megaapi Start Make integration do for you?

The Megaapi Start Make integration links your Megaapi Start account to Make, a tool where you build a scenario: an automation made of modules, each module being one brick that acts on one app. Megaapi Start sits in the Communication category, and its 20 modules send messages and files, manage groups and read lists, with no code.

Reply to leads while they are still interested. A form tool collects a phone number, Check a contact on Whatsapp confirms it can be reached, and Send a Message greets the person. Each item passing between modules is called a bundle: here, one lead.

Keep a customer group up to date. When a deal closes in your CRM, Create a Group opens a conversation for the account and Add a Participant brings in the right contacts. When the project ends, Remove a Participant tidies up.

Deliver documents where people already read. Send a File pushes a quote or a receipt to one person, and Send a File Group shares it with a whole group.

Know the limits before you start. Make states that its documentation for Megaapi Start is limited, because little public information exists about the app, and the app has no trigger: another app or Make's schedule has to start your scenario. When a listed module falls short, Make an API Call reuses your connection to reach other endpoints.

The same app often has an n8n node too; the n8n vs Make comparison helps you pick your tool. To learn the editor properly, see Make training, and when a run fails, Make troubleshooting lists the usual fixes.

Connect

How do you connect Megaapi Start to Make?

  1. 01

    Open the connection window

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

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when you run several accounts. Then either approve Make on the Megaapi Start page that opens, or paste the key Megaapi Start gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Back in the module, Make can now read your account, so the fields fill with choices instead of staying empty. If they stay empty, the connection did not go through.

First scenario

Build your first scenario with Megaapi Start

GoalWhen a new lead lands in your form tool, Make checks the phone number with Megaapi Start and sends that person a message.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the form app that collects your leads, since Megaapi Start has no trigger of its own.

  2. 02

    Add the number check

    Click the + on the right, search Megaapi Start and choose Check a contact on Whatsapp. Click Create a connection, then map the phone number from the form module.

  3. 03

    Add the message

    Add Send a Message after the check. Fill the fields Make shows once the connection exists, and map data from the form so every lead receives wording that fits them.

  4. 04

    Test with Run once

    Click Run once, send a test entry through your form, and read the bundles each module received. You see right away whether the number was found and what the message module returned.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From now on each form entry goes through both Megaapi Start modules with nobody watching.

Modules

What each Megaapi Start module does

Megaapi Start gives you 20 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Megaapi Start1

Add a Participant

ActionIn the docs only

Puts a new person into a group you already run through Megaapi Start, so a signup elsewhere ends with that person inside the right conversation instead of on a to-do list.

When to use it
a customer pays for a program and should join the members group without anyone copying a number by hand.
Watch out
the group has to exist first, so pair it with Create a Group or List Groups earlier in the flow.
Megaapi Start2

Check a contact on Whatsapp

ActionIn the docs only

As its name says, checks whether a phone number exists on WhatsApp before you spend an operation, meaning one run of one module, on a message that would go nowhere.

When to use it
right after a form or a CRM hands you a number you have never messaged, to split good numbers from typos.
Watch out
run it once and read the bundle it returns, because the documentation does not describe its output.
Megaapi Start3

Create a Group

ActionIn the docs only

Opens a brand new group from your scenario, which saves you from building the same project or customer conversation by hand every time a deal starts.

When to use it
a new account is signed in your CRM and the team wants one shared thread with the client from day one.
Watch out
each run creates another group, so make sure the step before it only lets real new accounts through.
Megaapi Start4

Create a Webhook

ActionIn the docs only

Judging by its name, sets up a webhook on the Megaapi Start side from inside Make, a setup step rather than something you repeat for every message or contact.

When to use it
you want Megaapi Start to call an outside address when events happen, and you prefer to set that up from a scenario instead of the app's own screens.
Watch out
this module does not turn Megaapi Start into a trigger, since the app offers no trigger module in Make.
Megaapi Start5

Get a Group

ActionIn the docs only

Fetches the details of one group you already know, so later modules can reuse what Megaapi Start stores about it instead of you retyping anything.

When to use it
before adding someone or posting a file, to confirm you are pointing at the right group and pull its data into the flow.
Watch out
you need the group reference beforehand; if you only have a name, start with List Groups.
Megaapi Start6

Leave a Group

ActionIn the docs only

Makes your connected number step out of a group, which is handy when a project closes and the account should stop receiving that conversation.

When to use it
a contract ends in your billing tool and the matching client group no longer needs your presence.
Watch out
treat it as a one-way step and test it on a throwaway group first.
Megaapi Start7

List Groups

SearchIn the docs only

Returns the groups your account belongs to, as a search module: zero, one or many bundles, one bundle per group, that the next modules process one after the other.

When to use it
you need to find a group by its name or post the same announcement across several of them.
Watch out
every returned group runs the following modules again, so the operation count grows with the length of the list.
Megaapi Start8

List Message

SearchIn the docs only

Make files it as a search, yet the documentation never says what it returns; the name only hints at a list tied to messages. Treat it as unknown until you have seen its output.

When to use it
once a test shows it returns what your flow actually needs.
Watch out
run it alone with Run once and read the bundles before you wire it into a live scenario.
Megaapi Start9

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Megaapi Start API with the connection you already set up, which covers what the named modules leave out.

When to use it
you found an operation in the Megaapi Start API documentation that none of the named modules offers.
Watch out
you write the request yourself, so keep the API documentation open and check the answer in the bundle after Run once.
Megaapi Start10

Perform a Logout

ActionIn the docs only

As the name suggests, signs your connected session out of Megaapi Start from a scenario, useful as a controlled off switch rather than a step in daily messaging flows.

When to use it
a phone line is being retired or handed over, and you want the change done as part of a documented process.
Watch out
the modules that follow may stop working after the logout, so place it last and keep it out of routine scenarios.
Megaapi Start11

Remove a Participant

ActionIn the docs only

Takes one person out of a group, so access follows the status in your other tools instead of lingering after a customer or a freelancer leaves.

When to use it
a subscription is cancelled or a mission ends, and the matching member should lose the group at the same moment.
Watch out
map the number from a reliable source, since a wrong mapping removes the wrong member.
Megaapi Start12

Send a Contact Message

ActionIn the docs only

Shares a contact card inside a chat, so the recipient can save the number in one tap instead of copying digits from a text.

When to use it
a new customer is assigned an account manager and should receive that person's details in the conversation.
Watch out
check with Run once how the card shows on a real phone before sending it to customers, as the documentation does not describe the fields.
Megaapi Start13

Send a File

ActionIn the docs only

Delivers a document to one person on Megaapi Start, so a quote, an invoice or a ticket lands where the customer already reads their messages.

When to use it
your invoicing tool produces a PDF and the customer should get it without opening an email.
Watch out
on the Free plan Make caps files at 5 MB, so check the size of your PDFs before you switch the scenario on.
Megaapi Start14

Send a File Base64

ActionIn the docs only

Sends a file whose content arrives as Base64 text rather than as a file, which is how some apps and APIs hand over documents they generate.

When to use it
the module before it returns an encoded string, for example a PDF built by another service, and you want to forward it as is.
Watch out
if the previous module already gives a normal file, Send a File is the simpler choice.
Megaapi Start15

Send a File Group

ActionIn the docs only

Posts one document to a whole group at once, so every member gets the same version instead of a chain of forwards.

When to use it
a price list, a schedule or a brief changes and the team group has to see the latest file.
Watch out
the group must be identified first, so place Get a Group or List Groups upstream when you do not have its reference.
Megaapi Start17

Send a Location

ActionIn the docs only

Drops a map location into the conversation, so the recipient opens directions straight from the chat instead of retyping an address.

When to use it
a visit, a delivery or an event is confirmed and the person needs to know exactly where to go.
Watch out
the documentation does not say which location format the module expects, so check the fields in the module once the connection exists.
Megaapi Start18

Send a Message

ActionIn the docs only

Sends a text to one contact, the workhorse of most Megaapi Start scenarios: confirmations, reminders tied to an event, answers to a form.

When to use it
something happens in another app, like a paid order or a booked slot, and one person should hear about it.
Watch out
each bundle that reaches it sends one message, so a search upstream returning many items means many messages.
Megaapi Start19

Send a Message to Group

ActionIn the docs only

Posts a text into a group rather than to a single person, so a whole team or community gets the same update at the same time.

When to use it
a new lead, a failed payment or a published release should be announced to the people who act on it.
Watch out
pick the group from Make's list once connected, or map it from Get a Group, so the text does not reach the wrong audience.
Megaapi Start20

Update a Connection Status

ActionIn the docs only

Changes the status of your Megaapi Start connection from a scenario, a maintenance step that sits beside your messaging flows rather than inside them.

When to use it
you manage the line from your own tools and want its state to follow a decision recorded there.
Watch out
the documentation does not list the possible statuses, so open the module and read the choices before building around it.
Need help

Need help automating Megaapi Start with Make?

A person reads every message.

FAQ

Megaapi Start and Make: common questions

01Is the Megaapi Start Make integration free?
Yes, Megaapi Start is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to one minute, remove the cap on active scenarios and allow runs of 40 minutes. Make counts usage in operations, one per module per bundle. Your Megaapi Start subscription is a separate matter that this page does not cover.
02What do you need to connect Megaapi Start to Make?
A Megaapi Start account and a Make account are enough to start. Make's documentation for this app lists no prerequisites and no specific connection steps, so the generic path applies: add a Megaapi Start module, click Create a connection, name it if you want, then either approve Make on the Megaapi Start page or paste the key the app gives you, and click Save. Once saved, the connection serves all 20 Megaapi Start modules, so you only do this once per account.
03Can Megaapi Start start a Make scenario in real time?
No, not on its own: Megaapi Start has no trigger module in Make, neither scheduled nor instant. Your scenario starts another way. The usual option is a trigger from another app, such as a form, a CRM or a shop, followed by Megaapi Start actions. You can also run the scenario on Make's schedule, every 15 minutes by default, or start it with a Make webhook when a system can call a URL. Going by its name, the Create a Webhook module sets up a webhook on the Megaapi Start side; it does not add a trigger in Make.
04What if a Megaapi Start module is missing in Make?
It depends on what you need, but Make an API Call usually covers it. That module calls any endpoint of the Megaapi Start API with the connection you already created, so an operation absent from the listed modules stays within reach. Keep the Megaapi Start API documentation open, since you write the request yourself. Also note that Make describes its own documentation for this app as limited, so test every new module with Run once and read the bundles before you switch a scenario on.
05Should you use Make or n8n for Megaapi Start?
It depends on the tool your team already works in. On Make, Megaapi Start comes with 20 modules, 18 actions and 2 searches, and Make an API Call to reach the rest of its API, all with one connection. The same app often has an n8n node as well, so check whether it exists and what it covers before you decide. Neither tool is ranked here. If your other automations already run in Make, keeping Megaapi Start there means one editor and one place to monitor runs.
Same platform

Other docs you might need on this stack.

Browse all integrations