Resources · Make integration

RapiWha Make integrationAutomate RapiWha with Make.

Need your messages to leave and arrive without copy and paste? The RapiWha Make integration gives you 2 action modules, one to read messages and one to send them. This page walks you through the connection, a first scenario and the traps to know.

Try the RapiWha integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RapiWha Make integration do for you?

The RapiWha Make integration links your RapiWha account to Make, a no-code tool where you chain apps together. You build a scenario (the automation itself) from modules (one brick each), and RapiWha brings two of them: Get Messages and Send a Message.

Confirm every new order to the buyer. A shop records a new order in its sales tool, and Send a Message tells the buyer it went through. The order app starts the scenario and sets the pace, RapiWha does the talking.

Pull incoming messages into a shared sheet. Get Messages, judging by its name, brings the messages of your account into the scenario, where a spreadsheet module can log each one so the support team reads them in one place.

Warn a colleague when something needs a human. A form tool receives an urgent request, and Send a Message pings the person on duty instead of leaving it in an inbox.

Know the limits first. RapiWha has no trigger in Make, so another app or the scenario schedule has to start things. Make also warns that its documentation for RapiWha is limited, because little public information exists about the app. If you weigh tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains plans, and the Make training helps you build with confidence.

Connect

How do you connect RapiWha to Make?

  1. 01

    Add a RapiWha module

    In your scenario, click the + and search for RapiWha, then pick Get Messages or Send a Message. The module opens and asks for a connection, meaning your RapiWha account linked to Make once. Click Create a connection.

  2. 02

    Name the connection

    Giving it a name is optional but useful: something like "RapiWha support line" tells you which account a module uses when you open the scenario again later. Every RapiWha module reuses this same connection.

  3. 03

    Authorize and save

    Follow what the window asks: either approve Make on the RapiWha page, or paste the key RapiWha gives you. Then click Save. The module can now reach your account and you can fill in its fields.

First scenario

Your first scenario with RapiWha

GoalWhen a new record lands in another app, Make sends a RapiWha message to the right person.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor. This first module decides when the whole automation starts.

  2. 02

    Pick the starting app

    Since RapiWha has no trigger, start with the app where the event happens, such as your order or form tool. Connect it and let Make list what it can read there.

  3. 03

    Add Send a Message

    Click the + on the right of that first module, search for RapiWha and choose Send a Message. Create or select your connection, then map the data of the previous module into the message.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Each module shows the bundles it received, one item per bubble, so you can see exactly what went into the message.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From then on it runs without you.

Modules

What RapiWha modules can you use in Make?

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

RapiWha1

Get Messages

ActionIn the docs only

Judging by its name, this module brings the messages of your RapiWha account into the scenario, so the next modules can store, sort or answer them. It is an action, so it only runs when the scenario reaches it.

When to use it
you want received messages copied into a sheet or a helpdesk tool the team already watches.
Watch out
the documentation is limited, so click Run once and read the bundles before mapping anything.
RapiWha2

Send a Message

ActionIn the docs only

Here is the module that speaks for you: it sends a RapiWha message built from data earlier in the scenario, like a name or an order number. Each send counts as one operation on your plan.

When to use it
an event in another app, such as a paid invoice or a new booking, deserves a quick note to a customer or colleague.
Watch out
Run once really sends, so test with a recipient you control before switching on.
Need help

Need help automating RapiWha with Make?

A person reads every message.

FAQ

RapiWha and Make: common questions

01Is the RapiWha Make integration free?
Yes, on the Make side. RapiWha is a standard app, available from 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, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module run on one bundle. Your RapiWha subscription is separate and not covered here.
02What do you need to connect RapiWha to Make?
A RapiWha account and a Make account. The documentation lists no specific prerequisite, so the generic Make flow applies: add a RapiWha module, click Create a connection, optionally name it, then either authorize Make on the RapiWha page or paste the key RapiWha provides, and click Save. The connection is created once and reused by both modules. If the window asks for something you cannot find, check your RapiWha account settings first.
03Does the RapiWha Make integration react in real time?
No, because RapiWha has no trigger in Make, neither scheduled nor instant. A scenario that uses it has to be started another way. The usual option is to place another app's trigger first, for instance a new order or a form entry, and add Send a Message after it. The other option is to start with Get Messages and let the scenario schedule run it, every 15 minutes by default, or every minute on a paid plan.
04What if a RapiWha module is missing in Make?
It depends on what you need. RapiWha has only two modules in Make, Get Messages and Send a Message, and no Make an API Call module to reach the rest of its API. If your case needs more, look at another messaging app available in Make, or ask the team behind this page to study the setup with you. Make also notes that public information about RapiWha is thin, so its documentation stays limited.
05Should you use Make or n8n for RapiWha?
It depends on your criteria rather than on the app. In Make, RapiWha offers 2 action modules, runs from the Free plan and plugs into scenarios built visually. The same app often exists as an n8n node as well, so check what each tool covers for your exact use: the modules or nodes available, the plan you already pay for and where the rest of your automations live. Neither choice is ranked here; pick the one that fits your stack.
Same platform

Other docs you might need on this stack.

Browse all integrations