Zapier
WhatsAble triggers and actions in Zapier: run Zaps on WhatsApp messages, send templates and media, schedule follow-ups, update contacts and check delivery status. Coexistence is supported; you keep the WhatsApp Business app on your phone.
WhatsAble integration with Zapier
Zapier is a platform that runs automated workflows, called Zaps. The Whatsable app in Zapier connects your Zaps to your WhatsApp number in WhatsAble.
Use it to:
- Start a Zap when a contact writes to your WhatsApp number.
- Send a WhatsApp template or a free-form message from any other app in Zapier.
- 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 Zap sets appear in the WhatsAble inbox. Your team and your AI agent use the same data.
Meta WhatsApp Coexistence is supported on Whatsable. You do not need to delete the WhatsApp Business app or stop using the number on your phone. After Embedded Signup, the same number works in the WhatsApp Business app, the Whatsable inbox, and automations (Make, Zapier, n8n, API, and webhooks) at the same time.
Available triggers and actions at a glance
The app is called Whatsable in Zapier. Each step signs in with your WhatsAble API key.
Trigger (Instant)
- New Incoming or Outgoing WhatsApp Message
Actions
- Send WhatsApp Message
- Schedule a Follow-Up Message
- Update a Contact
- Get Delivery Status of a Message
How the Zapier app works with WhatsAble
The Zapier 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.
The What this key can do setting of an API key limits API v1 only. It does not limit the Zapier app.
API keys and WhatsApp numbers
An API key belongs to one default WhatsApp number in your organization. This decides how the Zapier app behaves:
- Every message that the Zapier app sends with the key goes out from the key's default number.
- A trigger that the Zapier app registers with the key receives the messages of that number only.
- The template list in the Send WhatsApp Message action 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 connect one Whatsable account in Zapier 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.
Prerequisites
Before you start, make sure that you have:
WhatsAble account
A WhatsAble plan that includes integrations (Pro or Agency) and a connected WhatsApp number. The Basic plan does not include integrations.
Zapier account
Access to Zapier, where you build and turn on Zaps.
New to WhatsAble? Sign up here.
Set up your WhatsAble account
Connect your WhatsApp number
Connect your WhatsApp Business number to WhatsAble with the embedding process. You do not need to delete the WhatsApp Business app. Coexistence is supported.
Your connected numbers are in Settings → Business Numbers.
Meta requires this process to verify your business and to apply the WhatsApp Business Platform policies.
Set up message templates (if you send template messages)
A WhatsApp template is a message format that Meta approves. You need a template to start a new conversation with a contact. Create the template in WhatsAble, and get it approved, before you use it in Zapier.
Open Templates
In the WhatsAble sidebar, click Templates.
Start a new template
Click New template.
Fill out the form
A name for internal reference. WhatsAble changes it to lowercase with underscores, as Meta requires.
The language of the template.
Marketing, Utility or Authentication.
A text, image, document or video header.
The message text. Use {{1}}, {{2}} for variables, numbered in sequence from 1.
A short line under the body.
Optional quick reply, website, phone or copy code buttons.
Submit for review
Click Submit for review.
Meta usually reviews a template within 24 hours. Utility and Authentication templates have the highest approval rates.
Create the template on the WhatsApp Business account of the number that your API key uses. For the full procedure, see Message templates.
Create your WhatsAble API key
Only owners and admins can create API keys.
- In the WhatsAble sidebar, click API keys.
- Click Create API key.
- In Key name, type a name that tells you where the key is used, for example
Zapier production. - In Number, choose the WhatsApp number that the key sends from.
- Click Create key.
- Click Copy key, then click I have saved it.
You can reveal and copy the key again later from the same page. For more about keys, see API keys.
Treat the key like a password. Anyone with the key can send messages to your contacts. Never share it publicly or commit it to version control.
Connect WhatsAble to Zapier
Open the Zapier page in WhatsAble (optional)
In the WhatsAble sidebar, under Integrations, click Zapier. This page lists the triggers and actions, the fields a trigger sends, and video walkthroughs. Click Open in Zapier to open the Whatsable app on zapier.com.
Create a new Zap
- Log in to your Zapier account at zapier.com.
- Click + Create and select Zaps.
- In the Zap editor, add your first step. Follow the trigger or action guides in the step reference below.
Step reference
Trigger
New Incoming or Outgoing WhatsApp Message
Type: Instant trigger | App: Whatsable | Connection: your WhatsAble API key
Description in Zapier: "When you receive or send a WhatsApp message. You can choose to only trigger this when you send or receive a message, or both."
Runs as soon as a WhatsApp message event occurs on the number of your API key. You can set it to run on incoming messages only, outgoing messages only, or both directions. Outgoing events include messages typed by hand in the WhatsApp Business app, messages from the WhatsAble inbox, and messages from automations. Use it for AI chatbots, lead qualification, CRM sync, and automations that must react when a teammate replies on the phone.
When you turn on the Zap, the Zapier app registers its trigger URL with WhatsAble. The trigger then appears in Settings → Webhooks, where you can see and change what it receives.
After a team member replies in a chat, this trigger stops sending that chat for 24 hours. This prevents your Zap and your team from both answering. To change or remove the pause, edit the webhook in Settings → Webhooks and change Pause when your team replies.
Set up the trigger
Add the trigger step
- In your Zap editor, click the Trigger step.
- Search for Whatsable in the app search bar.
- Select Whatsable in the results.
- Under Trigger Event, select New Incoming or Outgoing WhatsApp Message.
- Click Continue.
Connect your WhatsAble account
- In the Account section, click Sign in to Whatsable.
- A dialog asks for your API key. Paste your WhatsAble API key.
- Click Yes, Continue to Whatsable.
You do this once. You can use the connected account again in every Whatsable step of every Zap.
Paste the WhatsAble API key, not a WhatsApp or Meta API key. Copy the key from the API keys page.
Configure the trigger
The Configure section shows these fields:
Select Notifyer. This is the option for a WhatsAble API key
How Zapier maps the trigger data to your Zap fields. Keep the default unless you need a specific mapping
Click Continue.
Test the trigger
- Click Test trigger. Zapier gets a recent message event from WhatsAble.
- If Zapier finds a record, it shows a sample with all the output fields.
- Check that the fields look correct.
If no test data appears, send a WhatsApp message to your connected number first. Then click Test trigger again. Zapier needs at least one recent event for a sample.
When the test passes, your trigger is ready. Click Continue to add your first action.
Trigger output fields
When this trigger runs, your Zap receives these fields from WhatsAble. You can map any of them into your action steps.
The contact's number in international format, digits only (for example 14155550187). It is the contact who sent or received the message. On an outgoing message, it arrives as a number, not as text
The contact's ID in WhatsAble
The contact's display name in WhatsAble
The labels of the conversation, separated by commas (for example Hot Lead, Buyer Qualified, Urgent)
The type of the message, for example text, image, audio or document. The value is referral for a text message that came from a Click-to-WhatsApp ad. The value is button or interactive when the contact tapped a button or a list row
false when your business sent the message. On an incoming message, the field is true or is not sent. Use a Filter step after the trigger to act on one direction only
Outgoing messages only. WhatsApp App for a reply typed in the WhatsApp Business app. AI for a message from the AI agent, follow-ups included. Notifyer for every other sender: the WhatsAble inbox, a broadcast, the API, Make, Zapier or n8n
Outgoing messages only. false when the AI agent sent the message. true for every other sender
The public link to an attached file (image, document, audio). Empty when there is no attachment
true when the delivery combines several quick messages into one request. You turn this on with Combine quick messages in Settings → Webhooks. false for a delivery of one message
Only on the first message of a chat that started from a Facebook or Instagram ad or post. The object exactly as Meta sends it, with keys such as source_type, source_id, source_url, headline, body, media_type, the creative URLs and ctwa_clid. See Click-to-WhatsApp ads
Only when the contact tapped a button or a list row. It contains id (the ID that you gave the option), title (its label), message_id and whatsapp_message_id (the message that offered the option). Each ID is null when it is not known
A JSON string with the recent messages of the conversation. Each item has type (user or bot), content, timestamp and content_type. Parse it before you loop over it
The latest message from the contact
The latest message that your business sent to this contact, from a person or from a bot. It helps an AI not to repeat the same answer
The Unix time, in seconds, of the contact's latest message. null when the recent history has no message from the contact
The Unix time, in seconds, of the latest message from your business. null when the recent history has no message from your business
The conversation as one block of readable text. Give it to an AI prompt directly, without parsing last_messages
The AI note saved on the contact. It holds lead details such as name, email, preferences and language. Set or change it with the Update a Contact action
Automation instructions that the AI follows for this contact
Only on a delivery that combines several quick messages. The messages of the contact from the wait time, in one text: Message 1: "…" — Message 2: "…". The text is not text when the batch is empty
To act on one direction only, add a Zapier Filter step on incoming_message. An outgoing message has false. An incoming message has true, or does not have the field. So to keep only incoming messages, continue when incoming_message is not false. Use send_by and was_message_by_human to see whether the WhatsApp Business app, the AI agent or another sender sent it.
Incoming and outgoing WhatsApp messages
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 member
Use these three fields to tell what happened and who sent it:
true when a contact sent a message to your business. false when your business sent a message to the contact (outgoing). Filter on this field to run logic only for one direction.
Which system or person sent an outgoing message:
send_by value | Meaning |
|---|---|
WhatsApp App | Typed by hand in the WhatsApp Business app on a phone |
AI | Sent by your AI agent, including its follow-ups, or by an automatic reply: the away message or the keep-the-window-open follow-up |
Notifyer | Anything else: a teammate in the inbox, a broadcast, the API or an automation |
Notifyer is the old name of Whatsable. The value stays the same so existing automations keep working. Incoming messages carry no send_by.
false when your AI agent or an automatic reply (the away message or the keep-the-window-open follow-up) sent the message, true for every other outgoing message. Combine it with send_by to tell a reply typed on the phone from one sent through Whatsable.
Example payload: message typed on the phone
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
}last_message_of_bot is the last message your business sent — whether a human typed it in the WhatsApp Business app or the Whatsable inbox, or your AI agent or an automation sent it. last_messages is a JSON string of the last 15 messages (parse it before iterating). phone_number may arrive as a number rather than a string.
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 attribution
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.
referral is typically present on the first inbound message after the ad click. Later messages in the same conversation usually omit it. Persist ctwa_clid and source_id as soon as you see them.
| Field | What it tells you |
|---|---|
source_type | "ad" for an ad, "post" for an organic post |
source_id | Ad or post ID — use this to group leads by creative |
source_url | Where they tapped (Instagram permalink, Facebook/ad URL) |
headline / body | Ad copy the lead saw |
media_type | "image" or "video" |
image_url / video_url | Creative asset URL |
ctwa_clid | Click ID for Meta Conversions API attribution |
{
"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.
Actions
Actions work in WhatsAble: they send messages, schedule follow-ups, update contacts and check delivery status.
Send WhatsApp Message
Type: Action | App: Whatsable | Connection: your WhatsAble API key
Description in Zapier: "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 or reach out first, 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.
Set up the action
Add an action step
- In your Zap editor, click + to add a new step, or click an existing action step.
- Search for Whatsable in the app search bar and select it.
- Under Action Event, select Send WhatsApp Message.
- Click Continue.
Connect your WhatsAble account
Select your connected Whatsable account in the dropdown. Or click Sign in to Whatsable to add an account with your WhatsAble API key.
Configure the message
In the Configure section, choose your message type in the Configuration dropdown:
Use this to start a new conversation with a contact, or to reach out first. It needs a template that Meta approved.
The recipient's number in international format, digits only, with no + or spaces (for example 14155550187). Map it from an earlier step or type it
Select one of your approved templates. The list shows the approved templates of the WhatsApp Business account that holds your key's number, with a preview of the body, the language and the category
A field appears for each variable of the template ({{1}}, {{2}}...). Map each one to data from earlier steps (for example the contact name from a form)
If the template has a media header (image, video or document), the public URL of the file. This field shows only for a template with a media header
If the template has a dynamic URL button, the full URL value, including the dynamic part
AI context about this contact (name, email, preferences, language, budget). WhatsAble saves it on the contact, and the AI reads it to personalize later replies. The recipient does not see it
Labels to add to this conversation, for internal tracking and routing. Labels appear in the WhatsAble inbox, and the label condition of a follow-up can use them
Test the action
- Click Continue to go to the Test section.
- Click Test step. Zapier sends a real message with your configuration.
- Check WhatsApp to make sure that the message arrived.
- If the test passes, click Publish to turn on your Zap, or add more steps first.
A test of this action sends a real WhatsApp message. Use your own number during setup, so that no real contact gets a test message.
Schedule a Follow-Up Message
Type: Action | App: Whatsable | Connection: your WhatsAble API key
Description in Zapier: "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 that stop when a lead replies.
Set up the action
Add an action step
- In your Zap editor, click + to add a new step.
- Search for Whatsable and select it.
- Under Action Event, select Schedule a Follow-Up Message.
- Click Continue.
Connect your WhatsAble account
Select your connected Whatsable account, or add one with your WhatsAble API key.
Choose your message type
In the Configure section, select Send WhatsApp Template or Send a non-template message in the Configuration dropdown.
The message fields are the same as in the Send WhatsApp Message action above. Fill in the phone number, select your template or message type, map the variables, and set labels and a note if you want.
Set when to send the message
Sends the message after a delay from the time this Zap step runs:
Choose 1, 2, 3, 4, 5, 10, 15, 20, 30, 60, 90 or 120
Choose Minutes, Hours or Days
Set a reply condition (recommended)
The reply condition tells WhatsAble to cancel the scheduled message when the recipient replies in the time that you choose. This keeps follow-ups away from contacts who already talk to you.
| Condition | WhatsAble cancels the message when... |
|---|---|
| Recipient did not reply after my last message | The contact replies at any time before the scheduled send |
| Recipient never replied to any of my messages | The contact has replied to you at some time |
| Recipient did not reply within 20 minutes | The contact replies within 20 minutes |
| Recipient did not reply within 45 minutes | The contact replies within 45 minutes |
| Recipient did not reply within 3 hours | The contact replies within 3 hours |
| Recipient did not reply within 6 hours | The contact replies within 6 hours |
| Recipient did not reply within 12 hours | The contact replies within 12 hours |
| Recipient did not reply within 24 hours | The contact replies within 24 hours |
| Recipient did not reply within 48 hours | The contact replies within 48 hours |
| Recipient did not reply within 72 hours | The contact replies within 72 hours |
For most follow-up sequences, use "Recipient did not reply after my last message". Then no follow-up goes to a contact who already talks to you. This protects the reputation of your WhatsApp number and keeps the conversation natural.
Set a label condition (optional)
Send the scheduled message only when the contact has, or does not have, a specific label at the send time:
Include: send only when the contact has this label.
Does Not Include: send only when the contact does not have this label.
The label that WhatsAble checks at the scheduled send time
Test and activate
Click Continue, then Test step, to make sure that WhatsAble queues the follow-up. You can see the scheduled messages in the contact's conversation in the WhatsAble inbox.
Scheduled messages appear in each contact's conversation in the WhatsAble inbox. You can cancel a scheduled message there at any time.
Update a Contact
Type: Action | App: Whatsable | Connection: your WhatsAble API key
Description in Zapier: "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.
Set up the action
Add an action step
- In your Zap editor, click + to add a new step.
- Search for Whatsable and select it.
- Under Action Event, select Update a Contact.
- Click Continue.
Connect your WhatsAble account
Select your connected Whatsable account, or add one with your WhatsAble API key.
Fill in the contact fields
The contact's number in international format, digits only, with no + or spaces (for example 14155550187). WhatsAble finds the contact by this number. If no contact has this number, WhatsAble creates one
The name of the contact in the WhatsAble inbox
Sets the AI note for this contact. The AI reads this field to personalize its replies and to qualify leads. A clear, structured note gives better AI conversations.
Recommended note format:
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 6pmOne or more labels to add to this contact. WhatsAble creates a label that does not exist yet. You can use labels in the label condition of a follow-up and for routing
One or more labels to remove from this contact. Select Remove All to remove every label at once
Test the action
Click Continue, then Test step. Open the contact in the WhatsAble inbox to make sure that the name, the labels and the note are correct.
Put Update a Contact as the first action in your Zap, before Send WhatsApp Message. Fill the AI note from your form or CRM data. Then the AI has the full context before the first message.
Get Delivery Status of a Message
Type: Action | App: Whatsable | Connection: your WhatsAble API key
Description in Zapier: "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 or not on WhatsApp), send an email instead.
Set up the action
Add an action step
- In your Zap editor, click + to add a new step after a Send WhatsApp Message or Schedule a Follow-Up Message action.
- Search for Whatsable and select it.
- Under Action Event, select Get Delivery Status of a Message.
- Click Continue.
Connect your WhatsAble account
Select the same Whatsable account that sent the message.
Enter the Message ID
The ID of the message to check. The Send WhatsApp Message or Schedule a Follow-Up Message step earlier in the same Zap returns it. Map it from that step with the Zapier data mapper
Click Continue.
Test and use the result
Click Test step. Zapier asks WhatsAble for the delivery status of that message.
The status is pending, sent, delivered, read or failed. Use it in a Filter step after this action to make two paths:
- Delivered or read: continue your main workflow.
- Failed: send a fallback email with Gmail, Outlook or another email app.
This action 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.
Add a Zapier Filter or Paths step after Get Delivery Status. Send delivered messages down one path, and failed messages down another path with a fallback email or an alert.
Build a complete Zap: step-by-step example
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
Trigger: New form submission
Start with a Google Forms, Typeform or Jotform trigger that runs when someone fills in your lead form.
Action: Update a Contact
Add Whatsable: Update a Contact. Map the form fields into the note:
email: {{email}} | Name: {{name}} | Budget: {{budget}} | Language: {{language}}Add labels such as New Lead and Form Submission.
The AI now has the full context before any conversation starts.
Action: Send WhatsApp Message (Template)
Add Whatsable: Send WhatsApp Message with the template configuration. Select your approved welcome template. Map the phone number and the template variables from the form data.
Action: Schedule a Follow-Up Message
Add Whatsable: Schedule a Follow-Up Message and configure it:
- Message: a follow-up template (for example
Hi {{1}}, just checking in...) - Schedule: 24 Hours (Relative delay)
- Reply condition: Recipient did not reply after my last message
WhatsAble cancels this follow-up when the lead replies to your first message.
Test and activate
- Click Test on each step and make sure that each step shows a success result.
- Click Publish to save your Zap.
- Set the On/Off switch to On.
Example use cases
AI chatbot lead qualification
Start on incoming messages, give conversation_paragraph and note to OpenAI, then send its reply with Send WhatsApp Message
Smart follow-up sequences
Schedule follow-ups with reply conditions. WhatsAble cancels them when the lead replies, so you never send too many messages
CRM-to-WhatsApp sync
When a deal stage changes in HubSpot or Pipedrive, update the AI note with Update a Contact, then send a matching template
Form-to-WhatsApp onboarding
When someone submits a form, set the AI context with Update a Contact, then send a personal onboarding template
Delivery fallback
After a send, use Get Delivery Status. If the message failed, send a fallback email with Gmail or Outlook
Real-time CRM logging
Log the conversation data of each WhatsApp message to a Google Sheet, Airtable or your CRM
Best practices
In new-lead Zaps, use Update a Contact as the first action, before Send WhatsApp Message. A note with structured lead data (name, email, preferences, language, budget) gives better AI conversations and better lead qualification.
Set a reply condition on every Schedule a Follow-Up Message action. "Recipient did not reply after my last message" is the safest choice. No follow-up then goes to a contact who already talks to you, which also protects the reputation of your WhatsApp number.
Send WhatsApp Message and Update a Contact can both add labels to conversations. Use labels to tag contacts (for example Hot Lead, Form Submission or Appointment Set). They appear in the WhatsAble inbox, and the label condition of a follow-up can use them.
In AI chatbot Zaps, map the conversation_paragraph trigger field into your OpenAI or Claude prompt. It is the conversation as plain text, which is simpler to put in a prompt than the last_messages JSON string.
Add a Zapier Filter step right after the trigger. To react only when a contact writes to you, continue when incoming_message is not false. To react only when your business sends a message, continue when incoming_message is false. Use send_by to tell WhatsApp App, AI and other senders apart.
When referral is present, save source_id, source_url, headline and ctwa_clid on the contact at once. Later messages in the same chat usually do not have referral. Use source_url to tell Instagram from Facebook, and source_id to compare ads.
Always give phone numbers in full international format, digits only, with no +, spaces or dashes (for example 14155550187 for the US, 447911123456 for the UK, 966501234567 for Saudi Arabia).
Troubleshooting
Check that your Zap is on
The trigger runs only when the Zap is on. Open the overview page of your Zap and make sure that the On/Off switch is set to On.
Check your connected account
Open the trigger step in the Zap editor and go to the Account section. Make sure that your Whatsable account shows no errors. If it shows an error, connect it again with an active WhatsAble API key.
Send a test message
Test trigger needs at least one recent event. Send a WhatsApp message to the number of your API key, then test again.
Check the number and the pause
The trigger receives only the messages of your API key's number. It also pauses a chat for 24 hours after a team member replies. Check both in Settings → Webhooks.
Contact support
If the messages appear in the WhatsAble inbox but the trigger still does not run, contact support.
Check the connected account
Make sure that your WhatsAble API key is active and that the correct account is selected in the action step.
Check the number of the key
If WhatsAble answers that the number of the API key is not connected, open API keys. Use Change number to move the key to a connected number.
Check the phone number format
The phone number must be digits only, in full international format, with no + or spaces (for example 14155550187).
Check the template status
Make sure that the template has the Approved status on the Templates page. A pending or rejected template causes an error.
Check the 24-hour window
You can send a non-template message only within 24 hours of the contact's last incoming message. Outside this window, use an approved template.
Check your plan
Make sure that your subscription is active and that your plan includes integrations (Pro or Agency). See Settings → Billing.
Check the WhatsApp account of the key
The list shows only the approved templates of the WhatsApp Business account that holds your API key's number. Create the template on that account, or move the key with Change number.
Fill all variable fields
All body variable fields (Body 1, Body 2 and so on) are required. Make sure that none is empty or mapped to a field that returns an empty value.
Check the template preview
The template dropdown shows a preview of the body text and example values. Use it to see what each variable expects.
Use a public media URL
If your template has a media header, the URL must be public. Open it in a private browser window to test it.
Check the reply condition
If the contact replied before the scheduled time, the reply condition cancelled the message. Check the contact's conversation in the WhatsAble inbox.
Check the delay settings
Make sure that the delay value and unit are correct (for example 24 + Hours, not 24 + Minutes).
Check your Zap history
In Zapier, open Zap History and find the run of the Schedule a Follow-Up Message step. Make sure that the step shows a success status.
Check the phone number
The phone number must match the contact's number in WhatsAble, in the same international format. If no contact has this number, WhatsAble creates a new contact.
Check the connected account
Make sure that the action step uses the Whatsable account with your WhatsAble API key.
Map the correct Message ID
Map the Message ID from the output of a Send WhatsApp Message or Schedule a Follow-Up Message step in the same Zap.
Use the same API key
The action finds only messages that were sent from the number of your API key. Use the same Whatsable account that sent the message.
Allow time for delivery
The status can take a few seconds to change after a send. If you check right after the send, add a Zapier Delay step before Get Delivery Status.
Need help?
Email support
Contact team@whatsable.app
Schedule a demo
Book a personal walkthrough
Live chat
Click the chat button in the bottom right corner of the WhatsAble app. The inbox hides it, so open another page first