What Zapier triggers and actions does Whatsable expose?
Every Whatsable Zapier trigger and action field: New Incoming or Outgoing WhatsApp Message, Send, Schedule Follow-Up, Update a Contact, and Get Delivery Status.
This page is the field dictionary for the Whatsable app on Zapier — every unlocked trigger and action input/output you can map in a Zap. Use it when you already know you want Zapier and need exact labels, types, and requiredness.
For connect steps, coexistence walkthrough, examples, and troubleshooting, use Zapier overview.
Prerequisites
- Plan: Zapier requires Pro or Agency (Bulk Message does not include integrations).
- WhatsApp number: Connected in Whatsable. Coexistence is supported — keep the WhatsApp Business app; phone replies can fire the trigger.
- Zapier app: Public listing Whatsable, slug
whatsable-ca185063. Search Whatsable in the Zap editor. - API key: From the Whatsable console API Keys page. In the Zap editor, set Credential Type to Notifyer and paste that key (core product key — not a Meta Graph token).
The marketplace app is public. A console “Connect to Zapier” deep link is onboarding only — it does not mean the app is invite-only.
At a glance
| Kind | Exact name in Zapier |
|---|---|
| Trigger (instant) | New Incoming or Outgoing WhatsApp Message |
| Action | Send WhatsApp Message |
| Action | Schedule a Follow-Up Message |
| Action | Update a Contact |
| Action | Get Delivery Status of a Message |
Trigger: New Incoming or Outgoing WhatsApp Message
Type: Instant · App: Whatsable · Internal key: whatsable_message_trigger
Fires when you receive or send a WhatsApp message. You can act on incoming only, outgoing only, or both by filtering after the trigger. Outgoing events include replies typed in the WhatsApp Business app, the Whatsable inbox, and automations.
Configure inputs
Select Notifyer.
Leave as default unless you have a specific mapping need.
Output fields — contact identity
The contact’s phone number (for example 14155550187). May arrive as a number rather than a string.
Unique internal ID for this contact (UUID).
Display name for this contact in Whatsable.
Comma-separated labels on the conversation (for example Hot Lead, Buyer Qualified).
Output fields — message data
Documented values: text, audio, image, or document.
true when the contact sent a message to your business; false when your business sent a message to the contact.
On outgoing messages: "WhatsApp App" (phone app), a teammate’s name (inbox), or an automation/app name. Empty on incoming messages.
true when a person sent the message (phone app or inbox); false when a bot or automation sent it.
Public URL of any attached file, or empty when there is none.
true when this event is a scheduled delivery; false for real-time messages.
Present when the inbound message came from a Click-to-WhatsApp ad or post. Typically on the first inbound after the tap; later messages usually omit it. Nested keys:
| Key | Meaning |
|---|---|
source_type | "ad" or "post" |
source_id | Ad or post ID |
source_url | Where they tapped |
headline / body | Ad copy |
media_type | "image" or "video" |
image_url / video_url | Creative URLs |
ctwa_clid | Click ID for Meta Conversions API |
Persist ctwa_clid and source_id as soon as you see them. See also Incoming message — Click-to-WhatsApp ads.
Output fields — conversation history
JSON string of recent messages (about the last 20). Each item includes type (user / bot), content, timestamp, and content_type. Parse before iterating.
The most recent message from the contact.
The most recent message your business sent (human or automation).
Unix timestamp (milliseconds) of the contact’s last message.
Unix timestamp (milliseconds) of your business’s last message to this contact.
Flat, readable conversation history — useful for LLM prompts without parsing last_messages.
Output fields — AI context and automation
AI context note stored on this contact. Update it with Update a Contact.
Automation instructions for the AI based on conversation events.
Description of messages currently scheduled to this contact.
Use a Zapier Filter on incoming_message, send_by, and was_message_by_human to split incoming vs outgoing and human phone-app replies vs automations.
Action: Send WhatsApp Message
App: Whatsable · Internal key: send_whatsapp_message
Sends a WhatsApp message using the official WhatsApp API. You can add labels and write notes that appear in Whatsable’s chat interface. Choose Configuration: template (start a conversation / proactive) or non-template (inside the customer service window).
Mode A — Send WhatsApp Template (to start conversation)
Recipient in international format — digits only, no + or spaces (for example 14155550187).
Select from your approved templates. The dropdown shows a live preview of body, language, and category.
One field per template variable ({{1}}, {{2}}, …). Required when the template has variables.
Public URL for a media header (image, video, or document). Only when the selected template has a media header.
Full URL including the dynamic portion, when the template has a dynamic URL button.
AI context about this contact. Stored on the contact — not sent to the recipient.
Labels to apply to this conversation.
Mode B — Non-template message (person must write to you first)
Only inside Meta’s customer service window after the contact’s last inbound message. Outside that window, use an approved template.
Same digit format as Phone Number above.
Text Message, Image Message, Video Message, Document Message, or Audio Message. Nested fields:
| Message Type | Nested fields |
|---|---|
| Text Message | Message Content (text, required); Enable Link Preview (boolean, optional, default false) |
| Image Message | Image URL (url, required); Caption (text, optional) |
| Video Message | Video URL (url, required); Caption (text, optional) |
| Document Message | Document URL (url, required); Caption (text, optional); Filename (text, required) |
| Audio Message | Audio URL (url, required) |
Labels to apply to this conversation.
AI context note for this contact.
Testing this action sends a real WhatsApp message. Use a personal test number during setup.
Action: Schedule a Follow-Up Message
App: Whatsable · Internal key: schedule_follow_up_message
Schedules a WhatsApp message for later, with optional reply and label conditions so it can cancel or skip when the lead is already engaged.
Message fields are the same as Send WhatsApp Message (template or non-template, including phone, template/variables or message type, Note, and labels), plus the schedule and condition fields below.
When to send — Relative (delay from now)
Choose only: 1, 2, 3, 4, 5, 10, 15, 20, 30, 60, 90, or 120.
Minutes, Hours, or Days.
When to send — Specific date and time
Exact send time — map from a previous step or enter a fixed value.
Timezone for the scheduled time (global list in the Zap editor).
Reply Condition
Optional but recommended. Cancels the scheduled send if the contact replies within the chosen rule.
| Condition label |
|---|
| Recipient did not reply after my last message (recommended default) |
| Recipient never replied to any of my messages |
| Recipient did not reply within 20 minutes |
| Recipient did not reply within 45 minutes |
| Recipient did not reply within 3 hours |
| Recipient did not reply within 6 hours |
| Recipient did not reply within 12 hours |
| Recipient did not reply within 24 hours |
| Recipient did not reply within 48 hours |
| Recipient did not reply within 72 hours |
Label condition (optional)
Include — only send if the contact has this label at send time. Does Not Include — only send if they do not.
Label evaluated when the scheduled send time arrives.
This is not a native drip builder inside Whatsable. Day-0 / day-3 / day-6 sequences are multiple Zap steps (or Paths) that each schedule one message. Whatsable sends each scheduled message; the sequence logic lives in Zapier.
Action: Update a Contact
App: Whatsable · Internal key: update_contact
Updates a contact in Whatsable — display name, AI note, and labels. The Zapier action description also states you can assign the conversation to a teammate.
Documented fields
Lookup key in international digit format. Creates a contact if none exists yet.
Display name in the Whatsable chat interface.
AI context note for this contact (name, email, preferences, language, and so on).
Labels to add. Whatsable conversation labels are the source of truth inside Whatsable.
Labels to remove. Remove All clears every label on this contact.
Assign a teammate: Update a Contact can assign the conversation to a teammate (Zapier action description + Zapier / Make / API). Documented fields on this page today are Phone Number, Display Name, Add a Note, and Add/Remove Label Names or IDs. Confirm any assignee control in your live Zap editor sample — do not rely on an undocumented field name. Operator how-to: Chat assignment and Team inbox.
Action: Get Delivery Status of a Message
App: Whatsable · Internal key: get_message_delivery_status
Checks whether a previously sent WhatsApp message was delivered — useful for fallback paths (for example email) when a number may be wrong or inactive.
Map from the output of a prior Send WhatsApp Message or Schedule a Follow-Up Message step (message_id in Zapier’s data mapper).
Use the returned status in a Zapier Filter or Paths step to branch delivered vs not-delivered flows (for example send a fallback email).
If a lookup fails in Zap History, re-check the mapped Message ID and contact support if needed. Do not assume every Message ID always resolves in every environment.
Limits and what this does NOT do
No native drip builder. Multi-day sequences use Zapier (or Make / n8n) schedule steps plus reply conditions — not a built-in drip product inside Whatsable.
No CRM ↔ Whatsable bidirectional label mirror. Add/Remove labels update Whatsable conversation labels. They do not sync Monday/Pipedrive (or other) CRM tags as one shared store.
Coexistence: Do not uninstall the WhatsApp Business app to “enable” API or Zapier. Keep using the phone; those replies can still start Zaps.
- Bulk Message plan: no Zapier / integrations — upgrade to Pro or Agency.
- Non-template sends only inside the customer service window after the contact’s last inbound; otherwise use a template.
- Phone format: digits only, full international, no
+, spaces, or dashes. - Group messaging via Zapier is not documented on this fields page (not an unlocked Official API docs surface here).
- Do not invent trigger
message_typevalues beyondtext,audio,image, anddocument. - Typing-indicator dots are not a documented Whatsable automation claim.
Related features and next steps
Zapier overview
Connect, coexistence, examples, troubleshooting
Team inbox
Shared inbox and human replies alongside automations
Chat assignment
Assign chats via Zapier, Make, API, keywords, or AI
Incoming message / CTWA
Webhook payload and Click-to-WhatsApp referral object
Also: Make overview · n8n overview · Plans.
FAQ
Does the Zapier trigger fire when someone replies in the WhatsApp Business app?
Yes, when coexistence is enabled and outgoing events are included. Filter on incoming_message, send_by (for example "WhatsApp App"), and was_message_by_human.
Can I build day-0 / day-3 / day-6 WhatsApp drips with Whatsable and Zapier?
Yes, by chaining Schedule a Follow-Up Message steps (and reply conditions) in Zapier. Whatsable is not a native drip builder — the sequence logic lives in Zapier.
Does Bulk Message include Zapier?
No. Zapier and other integrations require Pro or Agency.
Which fields does Update a Contact document today?
Phone Number, Display Name, Add a Note, Add Label Names or IDs, and Remove Label Names or IDs. Assigning a teammate is supported as a product capability via Zapier; confirm the live editor for any assignee control rather than inventing a field name.