Blog/Automation

How to Integrate WhatsApp API with Make.com (Formerly Integromat)

Integrate Rapiwa WhatsApp API with Make.com (formerly Integromat) using HTTP modules. Build no-code WhatsApp automations with 2,000+ Make.com apps. Step-by-step guide with screenshots.

by Rabbi
How to Integrate WhatsApp API with Make.com (Formerly Integromat)

You can integrate Rapiwa's WhatsApp API with Make.com (formerly Integromat) using Make.com's built-in HTTP module. Connect any of Make.com's 2,000+ app integrations to WhatsApp by adding an HTTP POST request to https://app.rapiwa.com/send-message in your scenario. No custom app required. Rapiwa costs $5/month flat with no per-message fees.

What You Can Build with Make.com + Rapiwa

Make.com connects over 2,000 apps — every one of them can now trigger a WhatsApp message:

  • HubSpot CRM → new lead → WhatsApp notification to sales rep
  • Typeform → form submission → WhatsApp confirmation to responder
  • Stripe → new payment → WhatsApp receipt to customer
  • Gmail → specific email received → WhatsApp alert to your phone
  • Google Calendar → event starting → WhatsApp reminder
  • Airtable → record updated → WhatsApp notification
  • Shopify → order created → WhatsApp order confirmation
  • WooCommerce → order shipped → WhatsApp shipping update

Prerequisites

Step 1: Create a New Make.com Scenario

  1. Log in to make.com
  2. Click Create a new scenario
  3. Choose your trigger app (e.g., Typeform, Shopify, Gmail, Google Sheets)
  4. Configure the trigger to fire on your desired event

Step 2: Add the Rapiwa HTTP Module

After your trigger module:

  1. Click the + icon to add a module
  2. Search for HTTP
  3. Select HTTP → Make a request
  4. Configure the module:

URL: https://app.rapiwa.com/send-messageMethod: POSTHeaders:

  • Name: Authorization
  • Value: Bearer YOUR_API_KEY

Body type: RawContent type: application/json

Request content (Body):

{
  "number": "{{1.phone_number}}",
  "message": "{{1.message_text}}"
}

Replace {{1.phone_number}} and {{1.message_text}} with the actual field references from your trigger module (Make.com uses {{module_number.field_name}} syntax).

Step 3: Example — Send WhatsApp When a Typeform Is Submitted

Scenario: Customer fills a contact form → receives instant WhatsApp confirmation

Modules:

  1. Typeform → Watch Responses
  2. HTTP → Make a Request (Rapiwa)

HTTP Body for Typeform integration:

{
  "number": "{{1.answers.phone_number.phone_number}}",
  "message": "Hi {{1.answers.full_name.text}}! ✅\n\nWe received your message and will get back to you within 24 hours.\n\nYour reference: {{1.token}}"
}

Working cURL test:

curl -X POST https://app.rapiwa.com/send-message \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "number": "8801234567890",
    "message": "Hi Sarah! ✅ We received your form submission and will get back to you within 24 hours."
  }'

Expected response:

{
  "status": "success",
  "messageId": "msg_make_abc123",
  "timestamp": "2026-06-18T10:30:00Z"
}

Step 4: Example — Stripe Payment WhatsApp Receipt

Scenario: Customer pays via Stripe → receives WhatsApp receipt instantly

Modules:

  1. Stripe → Watch Events → payment_intent.succeeded
  2. HTTP → Make a Request (Rapiwa)

HTTP Body:

{
  "number": "{{1.metadata.customer_phone}}",
  "message": "Payment received! ✅\n\nAmount: {{formatNumber(1.amount / 100, 2)}} {{upper(1.currency)}}\nReference: {{1.id}}\n\nThank you for your payment. Your receipt: {{1.receipt_url}}"
}

Note: Store the customer's phone number in Stripe payment metadata as customer_phone when creating the PaymentIntent.

Step 5: Example — Google Sheets Row Added

Scenario: New row added to a Google Sheet → send WhatsApp to the phone in that row

Modules:

  1. Google Sheets → Watch Rows
  2. HTTP → Make a Request (Rapiwa)

HTTP Body:

{
  "number": "{{1.phone}}",
  "message": "{{1.message}}"
}

This is the simplest possible Make.com + Rapiwa integration — useful for bulk sending from a sheet.

Step 6: Handle the Rapiwa Response

After the HTTP module, add a Router to handle success and failure:

  1. After the HTTP module, click +Router
  2. Branch 1: Filter {{2.data.status}} = success → log success or update database
  3. Branch 2: Filter {{2.data.status}} != success → send error alert or retry

Make.com expression to check success:

{{2.data.status}} equal to `success`

Receiving Incoming WhatsApp Messages in Make.com

To receive messages, use a Make.com Webhook module as your trigger:

  1. Add module: WebhooksCustom webhook
  2. Copy the webhook URL Make.com generates
  3. Register this URL in Rapiwa Dashboard → Webhooks → Events: message.received

Now incoming WhatsApp messages flow into your Make.com scenario for processing.

Example reply flow:

  1. Webhook (receives incoming message) →
  2. Router (parse keyword) →
  3. HTTP → Rapiwa (send reply)

Make.com vs n8n for WhatsApp Automation

FeatureMake.comn8n
PriceFree (1,000 ops/month), paid from $9/monthFree self-hosted, Cloud from $20/month
App integrations2,000+400+
Code/scriptingLimitedFull JS expressions
Self-hostingNoYes
Best forBusiness users, no-codeDevelopers, power users

Both work equally well with Rapiwa's REST API via HTTP modules.

Common Errors and Fixes

  • HTTP 401: Your Authorization header value must be exactly Bearer YOUR_API_KEY (capital B, space, then key). Verify in Make.com's HTTP module.
  • HTTP 400 — invalid number: Ensure the phone number is in international format without +. Add a text transform in Make.com: Tools → Text → Replace → replace + with nothing.
  • Scenario not triggering: Check Make.com's scenario run history. Triggers on free plans may have a 15-minute polling delay — upgrade to instant triggers for real-time scenarios.
  • Webhook not receiving data: Test the Rapiwa webhook registration by sending a WhatsApp message to your connected number after registering the Make.com webhook URL.

FAQ

Is there a native Rapiwa app in Make.com? Not yet. Use the HTTP module with a manual API call to https://app.rapiwa.com/send-message. This works identically to a native integration.

Does Make.com charge per WhatsApp message? Make.com counts each HTTP module execution as one operation toward your monthly limit. Rapiwa charges $5/month flat with no per-message fees. On Make.com's free plan (1,000 ops/month), you can send up to 1,000 WhatsApp messages per month before needing to upgrade.

Can I use Make.com to receive and reply to WhatsApp messages? Yes. Use a Webhooks → Custom webhook module as your trigger to receive incoming messages from Rapiwa, then process and reply with the HTTP module.

How do I format multi-line messages in Make.com? Use \n for line breaks within the JSON string. Make.com's HTTP module handles \n correctly as a newline character in WhatsApp messages.

Can I send the same message to multiple numbers in one Make.com scenario? Yes. Use Make.com's Iterator module to loop over a list of phone numbers (from Google Sheets, Airtable, etc.) and send the HTTP request for each one.