WhatsAble integration with MakeCopy Anchor Link

Make is a platform that runs automated workflows, called scenarios. The Whatsable for WhatsApp Business app connects your scenarios to your WhatsApp number in WhatsAble.

Use it to:

• Start a scenario when a contact writes to your WhatsApp number.
• Send a WhatsApp template or a free-form message from any other app in Make.
• Schedule a follow-up that WhatsAble cancels when the contact replies.
• Keep the AI note and the labels of a contact in sync with your CRM or your forms.
• Check whether a message was delivered, and send a fallback email when it was not.

Labels, notes and scheduled messages that a scenario sets appear in the WhatsAble inbox. Your team and your AI agent use the same data.

Available modules at a glanceCopy Anchor Link

The app is called Whatsable for WhatsApp Business in Make. Each module connects with your WhatsAble API key.

How the Make app works with WhatsAbleCopy Anchor Link

The Make app calls the WhatsAble integration API with your API key. The Make, Zapier and n8n apps all use this API. It is not API v1, which is for your own code. One API key works for both.

API keys and WhatsApp numbersCopy Anchor Link

An API key belongs to one default WhatsApp number in your organization. This decides how the Make app behaves:

• Every message that the Make app sends with the key goes out from the key's default number.
• A trigger that the Make app registers with the key receives the messages of that number only.
• The template list in the Send WhatsApp Message module shows the approved templates of the WhatsApp Business account that holds that number.

To work with two numbers, create one API key for each number. Then create one Make connection for each key.

To move a key to another number, open API keys and use Change number on the key. The triggers that the key registered move with it. Messages that are already scheduled keep their number.

PrerequisitesCopy Anchor Link

Before you start, make sure that you have:

Set up your WhatsAble accountCopy Anchor Link

Connect WhatsAble to MakeCopy Anchor Link

Module referenceCopy Anchor Link

TriggersCopy Anchor Link

An instant trigger runs your scenario as soon as a message event occurs in WhatsAble. Each trigger needs a webhook and a connection with your WhatsAble API key.

Setting up a WhatsAble trigger in MakeCopy Anchor Link

Both triggers use the same five steps. The only difference is the trigger that you select in step 1.

When you save the trigger, the Make app registers its webhook URL with WhatsAble. The webhook then appears in Settings → Webhooks, where you can see and change what it receives.

Incoming Messages from console (Whatsable)Copy Anchor Link

Runs each time a contact sends a message to the number of your API key. Use it for AI chatbots, lead qualification, CRM updates and real-time automations. It sends the full conversation context, including the AI note and the recent conversation history.

How to set up: Follow the five-step trigger setup guide above. In step 1, select Incoming Messages from console (Whatsable).

Output fields that your scenario receives:

This trigger does not send the incoming_message, send_by and was_message_by_human fields on an incoming message.

Incoming & Outgoing Messages from console (Whatsable)Copy Anchor Link

Runs on both incoming and outgoing messages, including messages typed by hand in the WhatsApp Business app. Use it for conversation logs, CRM sync, or automations that must react when a teammate replies on the phone.

Description in Make: "Get your sent and incoming messages data through a single webhook."

How to set up: Follow the same five-step trigger setup guide above. In step 1, select Incoming & Outgoing Messages from console (Whatsable).

Key difference: Use the incoming_message field to branch your logic:

• incoming_message = true: a contact sent your business a message.
• incoming_message = false: your business sent a message to a contact, from the phone app, the WhatsAble inbox or an automation.

Output fields: The same as the Incoming Messages from console trigger above, with these differences:

Incoming and outgoing WhatsApp messagesCopy Anchor Link

Whatsable can deliver both incoming and outgoing messages to your webhook — including messages typed by hand in the WhatsApp Business app on your phone. Outgoing messages reach only an endpoint you add under Settings → Webhooks, with Send to set to Make, Zapier or n8n and Outgoing messages ticked. The Whatsable triggers in the n8n, Make and Zapier apps receive incoming messages only.

This is possible because Whatsable supports Meta WhatsApp Coexistence. You keep using WhatsApp Business on your phone; those hand-typed replies still reach an external webhook and can start an automation. They are not limited to the Whatsable inbox.

The payload is the same whether you use n8n, Make, Zapier, or a custom webhook. For outgoing messages, paste your workflow's webhook URL into such an endpoint rather than using the app trigger. Watch the walkthrough on YouTube.

Direction, sending system, and team memberCopy Anchor Link

Use these three fields to tell what happened and who sent it:

Example payload: message typed on the phoneCopy Anchor Link

This is the JSON Whatsable POSTs when someone types a reply in the WhatsApp Business app. incoming_message is false, send_by is "WhatsApp App", and was_message_by_human is true.

{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
  "conversation_paragraph": "Bot (12:24:47 PM): Hello n8n ; User (12:27:42 PM): hi",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "last_message_of_user": "hi",
  "last_message_of_bot": "Hello n8n",
  "message_type": "text",
  "user_last_message_time": 1786722580,
  "bot_last_message_time": 1786797014,
  "attachment_url": "",
  "note": "email: alex\nName: Alex",
  "note_automation": "email: alex\nName: Alex",
  "labels": "n8n, webhook-test",
  "incoming_message": false,
  "send_by": "WhatsApp App",
  "was_message_by_human": true
}

When a teammate sends the same reply from the Whatsable inbox instead of the phone app, the payload is identical except:

{
  "incoming_message": false,
  "send_by": "Notifyer",
  "was_message_by_human": true
}

Click-to-WhatsApp ad attributionCopy Anchor Link

When a contact messages you after tapping a Click-to-WhatsApp ad (Facebook, Instagram, or WhatsApp Status), Meta includes a referral object on that inbound event. Whatsable forwards it in webhook and trigger data (n8n, Make, Zapier).

Use it to see which ad, creative, and platform produced the lead — then label the chat, route it, or send ctwa_clid back to Meta for campaign optimization.

{
  "incoming_message": true,
  "last_message_of_user": "Quiero información",
  "referral": {
    "source_type": "ad",
    "source_id": "52540693396957",
    "source_url": "https://www.instagram.com/p/DZiVBz7gAF9/",
    "headline": "Expo Nissan",
    "body": "Aprovechá la EXPONISSAN y llevate tu nuevo Nissan Kicks Play Sense MT.",
    "media_type": "image",
    "image_url": "https://scontent.xx.fbcdn.net/v/t45.1600-4/example.jpg",
    "ctwa_clid": "AfhN-JKvx8HeFTmfB-Tu11zktQRJ-MNdMV1mwvDNxHnpYrGl-jVf3OEFhLva_MP41zYRe5ErUteWFn3v4gkkjzfIEVr9J_u8GAo3-o6DqShykM4Zsl14FcU5MyThsCoQ"
  }
}

Whatsable never sends Meta's Cloud API envelope. On an endpoint that uses the Native payload format, the same object is at message.referral. Full field reference and a complete example: Message webhooks — Click-to-WhatsApp ads.

ActionsCopy Anchor Link

Actions work in WhatsAble: they send messages, schedule follow-ups and update contacts.

Send WhatsApp MessageCopy Anchor Link

Description in Make: "Send WhatsApp Messages using the official WhatsApp API. You can add labels to a WhatsApp conversation and also write notes about the lead that will appear in Whatsable's chat interface."

Sends a WhatsApp message at once to a phone number, from the default number of your API key. It sends template messages, which start a new conversation, and non-template messages, which you can send inside the 24-hour window. Labels and notes that you set here appear in the WhatsAble inbox.

How to configure:

Schedule a follow-up MessageCopy Anchor Link

Description in Make: "Schedule a follow-up to get sent later and add conditions so it only gets sent if the lead did not reply to you."

Schedules a WhatsApp message for a later time. An optional reply condition cancels the message when the recipient replies before it is sent. Use it for no-reply follow-up sequences, re-engagement and nurture workflows.

How to configure:

Update a ContactCopy Anchor Link

Description in Make: "Assign conversation to someone in your team, Add information in the notes, add/remove labels. Simply put the phone number and what information you want to change. This appears in the chat interface of our system."

Updates a contact in WhatsAble: the display name, the labels, and the AI note. Use it to keep WhatsAble contacts in sync with your CRM, your forms or other external data.

How to configure:

email: john@example.com | Name: John Smith
Looking for: 3BR house, $500k budget, north suburbs
Pre-approved: Yes | Language: English
Best time to contact: evenings after 6pm

SearchCopy Anchor Link

Get delivery status of a messageCopy Anchor Link

Description in Make: "Check if the message was delivered or not. Use this if you're not sure the number is correct and want to check if it was delivered and want to send a fallback email."

Checks the delivery status of a message that you sent before. Use it for a fallback: when a message was not delivered (for example, because the number is wrong), send an email instead.

How to configure:

The module returns the status of the message: pending, sent, delivered, read or failed. It finds only messages that were sent from the number of your API key. For any other ID, it answers that no message with this ID was sent from this number.

Build a complete scenario: step-by-step exampleCopy Anchor Link

This example goes from a new lead in a form to a template message and a follow-up: New lead from a form → AI context set → Template message sent → Conditional follow-up scheduled

email: {{email}} | Name: {{name}} | Budget: {{budget}} | Language: {{language}}

Example use casesCopy Anchor Link

Best practicesCopy Anchor Link

TroubleshootingCopy Anchor Link

Need help?Copy Anchor Link