Visual automation
Integrate WhatsApp with Make (ex-Integromat)
Make (formerly Integromat) is a visual automation platform where you build flows, called scenarios, by dragging modules connected by lines. Each module represents an action or a trigger: read a spreadsheet row, create a card, send an email, call an API. It has no dedicated native connector for unofficial WhatsApp, but it offers two generic features that cover everything: the HTTP module, which makes REST requests to any API, and Webhooks, which receives external events in real time. With these two blocks you talk to ZapZap API without writing a backend.
Why connect
Picture a clinic that receives leads through a form. In Make, the scenario starts when the form is filled in, goes through a qualification module and, at the end, needs to send a welcome WhatsApp message to the lead. By connecting ZapZap API through the HTTP module, Make sends the message from your own WhatsApp number, with community warm-up and an anti-ban layer that lowers the risk of the account going down. In the opposite direction, a Make Webhook receives every message that arrives on WhatsApp and feeds the rest of the scenario: create a task in the CRM, reply automatically, notify the team. You combine Make's visual orchestration with a managed WhatsApp channel, without depending on the official API or on template approval.
Step by step
- 1
Get your credentials in ZapZap API
In the ZapZap API dashboard, provision a number (R$15 per active number/month, prepaid, with a welcome credit when you create the account, subject to the current campaign) and copy the instance's x-api-key and x-api-secret. The complete reference of endpoints and fields is at https://api.zapzapapi.com/llms.txt.
- 2
Create a scenario and add the HTTP module
In Make, click Create a new scenario, add a module, search for HTTP and choose Make a request. This is the module that will send the WhatsApp message by calling ZapZap API.
- 3
Configure the sending request
In the HTTP module, set Method to POST and URL pointing to ZapZap API's sending endpoint (base https://api.zapzapapi.com). Under Headers, add x-api-key and x-api-secret with your values. Set Body type to Raw, Content type to application/JSON, and in the body map the destination number and the text using the fields coming from the previous modules in the scenario.
- 4
Receive messages with the Webhooks module
For the incoming flow, create another scenario starting with the Webhooks module, Custom webhook option. Click Add, copy the URL generated by Make and register that URL as the event webhook on your ZapZap API instance. Each message received on WhatsApp arrives as a trigger in Make.
- 5
Test, map and turn on scheduling
Use Run once to fire a test and check the API response in the execution tab. Adjust the data mapping between modules, save and turn on the scenario's Scheduling (immediate for webhooks, or by interval) to run in production.
Example
POST https://api.zapzapapi.com/api/v1/{instanceId}/send/text
Headers:
x-api-key: YOUR_API_KEY
x-api-secret: YOUR_API_SECRET
Content-Type: application/json
Body (illustrative example, check the exact fields at https://api.zapzapapi.com/llms.txt):
{
"number": "5511999999999",
"text": "Hello! We received your contact and will be with you shortly."
}Illustrative. The exact fields and endpoints are in the documentation.
Frequently asked questions
Does Make have a ready-made ZapZap API WhatsApp module?
You do not need one. You use the HTTP module (Make a request) to send messages and the Webhooks module (Custom webhook) to receive. Both are native to Make and talk to any REST API, including ZapZap API.
Do I need the official WhatsApp API for this?
No. ZapZap API works through managed WhatsApp instances, with no template approval and no official API process. You connect your number and start sending right away from your Make scenarios.
How much does it cost to run on Make?
ZapZap API charges R$15 per active number per month, prepaid, with a welcome credit when you create the account, subject to the current campaign. Make's cost depends on your plan on the platform, which even includes a no-cost tier for smaller volumes.
Is my number at risk of being banned when sending through Make?
No solution eliminates the risk, but ZapZap API brings community warm-up and an anti-ban layer that lowers it. It is worth spacing out the sends in the scenario and avoiding identical mass blasts.
Where do I find the exact endpoints and fields of ZapZap API?
The machine-readable documentation is at https://api.zapzapapi.com/llms.txt, with the API base at https://api.zapzapapi.com. Use it to confirm the sending routes and the webhook format before publishing the scenario.
Start now
Create your account, connect a number in minutes and test the API with warm-up and anti-ban. R$15 per active number/month, prepaid, no lock-in.