WhatsAble integration with n8nCopy Anchor Link

n8n is a workflow automation platform that you use in n8n Cloud or on your own server. The verified Whatsable node connects your n8n workflows to your WhatsApp number in WhatsAble.

Use it to:

• Start a workflow when a contact writes to your WhatsApp number.
• Send an approved template, with variables, a media header and a URL button.
• Send text, image, video or document messages inside the 24-hour window.
• Schedule a message for a later date and time.
• Add labels and an AI note to a contact, so that your team and your AI agent see the same context.
• Read Click-to-WhatsApp ad data (source_id, source_url, ctwa_clid) on new leads.

Available operations at a glanceCopy Anchor Link

For every field of the node, see What can the Whatsable n8n node send and receive?.

How the n8n node works with WhatsAbleCopy Anchor Link

The Whatsable node 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 node behaves:

• Every message that the node sends with the key goes out from the key's default number.
• A trigger that you register with the key receives the messages of that number only.
• The template list in the node 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 n8n credential 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

Integrate with n8nCopy Anchor Link

Set up your n8n workflow

1. Log in to your n8n account.
2. Click Create Workflow.
3. Add a trigger node:
   • Popular triggers are Google Forms, Jotform, ClickUp or a Schedule trigger.
   • Connect and configure the trigger for your use case.

Whatsable trigger node (incoming and outgoing)

Add the Whatsable node

1. Click the + button after your trigger node.
2. Search for "Whatsable" in the nodes panel.
3. Select the node with the official Whatsable logo.
4. Choose Send template via Whatsable or Send non-template via Whatsable.

Configure the WhatsAble credential

1. In the Whatsable node Parameters, find the Credential to connect with dropdown.
2. Select + Create new credential.
3. Paste your WhatsAble API key.
4. Give the credential a name, for example "WhatsAble Production".
5. Click Save.

Configure your message

1. In the Resource dropdown, select Send Message.
2. In the Operation dropdown, choose Send template via Whatsable for template messages. Choose Send non-template via Whatsable for other messages, which you can send only in the 24‑hour window.
3. Complete the required fields:

Operation: Send template via WhatsableOperation: Send non-template via Whatsable

Configure the message

Complete the required fields:

Recipientstringrequired

The recipient's number with the country code (for example +14155552671), or data from an earlier node

Template Name or IDdropdownrequired

Select one of your approved templates. The list shows the approved templates of the WhatsApp Business account that holds your key's number

Template message detailsstringrequired

Fill in the fields that your template needs:

• For text: type your message content.
• For media: give a public URL of your file.
• A caption, if you want one (for media files).

For all media types, make sure that your file URLs are public and that the file format is supported.

Notestring

(Optional) A note that WhatsAble saves on the contact, for internal tracking and for the AI agent

Label Names or IDsdropdown

(Optional) The labels from your WhatsAble labels to add to the conversation

Schedule Messageselection

(Optional) The date and time to send your message

Test and activate your workflow

1. Click Test Step on the Whatsable node.
2. If the test passes, n8n shows a success message.
3. Go back to your workflow.
4. Click Save to save the workflow.
5. Set the Active switch in the top-right corner to on.

Your workflow now runs. Each time your trigger conditions occur, n8n sends WhatsApp messages through WhatsAble.

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.

Example use casesCopy Anchor Link

Best practicesCopy Anchor Link

TroubleshootingCopy Anchor Link

Need help?Copy Anchor Link

Our support team can help you: