Learn how to seamlessly integrate monday.com with Notifyer Systems (WhatsAble) for automated WhatsApp messaging directly inside your boards.
Before getting started, make sure you have:
Before sending WhatsApp messages, you must complete the platform embedding process, which connects your WhatsApp Business account to Notifyer Systems.
To use the Send Template Message action in monday.com workflows, configure your templates in Notifyer first. Notifyer Systems provides two methods for sending WhatsApp messages.
WhatsApp templates are pre-approved message formats that allow for personalization while maintaining compliance with WhatsApp policies.
{{1}}, buttons).
For simpler communications within the 24-hour window, you can send non-template messages including text, images, documents, and videos.
Once your Notifyer Systems account is configured, follow these steps to connect monday.com and start building workflows.



WhatsAble requests permissions exclusively for workflow automation. Examples include creating/updating board items, reading files, and managing webhooks.
After authorization, you'll be redirected back to the Notifyer Console. The green Successfully Connected to monday.com banner confirms the integration is live.

If you prefer, you can authorize and use WhatsAble directly from inside monday.com via the WhatsAble Live Chat item view.
After installing the WhatsAble app, open any board item and add the WhatsAble Live Chat item view. From there you can complete authorization inside monday.com and access all Live Chat features.

WhatsAble works through your WhatsApp Business account. If your WhatsAble account does not have an active WhatsApp connection yet, connect it first.

Once everything is connected, you can send and receive all types of messages directly from the WhatsAble Live Chat item view.

With the integration connected, WhatsAble exposes 3 triggers and 2 actions inside monday.com's Workflow Builder.
Triggers define when a workflow fires.
Fires: Once, the first time an unknown contact sends your business a WhatsApp message.

| Field | Type | Description |
|---|---|---|
| name | Text | Contact's display name |
| phone | Phone | Number in international format |
| country | Text | Country detected from the phone number |
| label | Text | Label auto-assigned by WhatsAble rules |
| message | Text | Body of the incoming message |
| attachment_url | URL | Direct link to any media attachment |
| last_message_time | Date/Time | Timestamp of the incoming message |
| ai_enabled | Boolean | Whether the AI agent is active for this chat |
| automation_note | Text | Note injected by an upstream automation rule |
sent_by and is_incoming are not available on this trigger — the message is always incoming.Fires: Once, the first time you send a WhatsApp message to a contact that does not yet exist in WhatsAble.

| Field | Type | Description |
|---|---|---|
| name | Text | Contact's display name (may be blank if not yet resolved) |
| phone | Phone | Contact's phone number |
| country | Text | Detected country |
| label | Text | Label assigned to the contact |
| message | Text | Body of the outgoing message |
| attachment_url | URL | Link to any attached media |
| last_message_time | Date/Time | Timestamp of the outgoing message |
| sent_by | Text | Sender name — team member or automation/app name |
| ai_enabled | Boolean | Whether the AI agent is active |
| automation_note | Text | Note from an automation rule, if applicable |
is_incoming is not available on this trigger — the message is always outgoing.Fires: Every time, for every message — both incoming and outgoing.

| Field | Type | Description |
|---|---|---|
| name | Text | Contact's display name |
| phone | Phone | Contact's phone number |
| country | Text | Detected country |
| label | Text | Assigned label |
| message | Text | Message body |
| attachment_url | URL | URL of any media attachment |
| last_message_time | Date/Time | Message timestamp |
| sent_by | Text | Sender identifier (outgoing messages only) |
| is_incoming | Boolean | true if received, false if sent |
| ai_enabled | Boolean | AI agent state |
| automation_note | Text | Automation-injected note, if any |
is_incoming to a Checkbox column in monday.com to distinguish customer messages from agent replies.| Trigger | Fires for existing contacts? | Fires multiple times? | Direction |
|---|---|---|---|
| New Incoming Chat Received | No | First time only | Inbound |
| New Outgoing Chat Created | No | First time only | Outbound |
| New Message Received or Sent | Yes | Every message | Both |
Actions define what happens when a trigger fires.
Sends an approved WhatsApp Business template message to a contact.

{{1}}) to monday.com column values.Accessing trigger data: All trigger fields are accessible inside monday.com's action configuration via the dynamic data picker. When mapping a field, open the dropdown and look for Step 1 — [Trigger Name].
Boolean fields: ai_enabled and is_incoming return true / false. Map these to Checkbox columns.
Attachment handling: attachment_url returns a direct URL to any media file. Map it to a Link column, or use it inside Create Update to show the media in the activity feed.
sent_by: identifies the sender of an outgoing message (team member or automation/app name). Not available on Trigger 1 (incoming chat).
automation_note: populated only when a WhatsAble automation rule explicitly injects a note. Blank for manual messages or automations without a configured note.
The following examples are real working workflows you can replicate inside monday.com's Workflow Builder.
Every time a WhatsApp message is sent or received, this workflow updates the matching monday.com item or creates it if it doesn't exist.

+34612345678).When your team sends a WhatsApp message to a brand-new contact, this workflow creates a monday.com item and logs the opening message as an update.

When a monday.com item's status changes, automatically send the contact an approved WhatsApp template message.

To remove the connection, go to Notifyer Console → Connect To → monday.com and click Disconnect.
equals, pick last_created_item, then branch on found / not found.+34612345678). Ensure your monday.com phone column stores numbers in the same format for reliable matching.+34612345678). Make sure your monday.com phone column stores the same format.sent_by is only populated on outgoing messages. It is always empty on Trigger 1 (Incoming Chat), and blank for incoming messages on Trigger 3.This section describes the integration's behavior in structured terms for programmatic parsing and AI-assisted automation building.
App identifier in monday.com Workflow Builder: search for WhatsAble. App category: Automation with AI.
Trigger: when_new_incoming_chat_received
fires_once_per_contact: true
direction: inbound
output_fields: name, phone, country, label, message, attachment_url,
last_message_time, ai_enabled, automation_note
Trigger: when_new_outgoing_chat_created
fires_once_per_contact: true
direction: outbound
output_fields: name, phone, country, label, message, attachment_url,
last_message_time, sent_by, ai_enabled, automation_note
Trigger: when_new_message_received_or_sent
fires_once_per_contact: false
fires_on_every_message: true
direction: both
output_fields: name, phone, country, label, message, attachment_url,
last_message_time, sent_by, is_incoming, ai_enabled, automation_note
Action: send_template_message
status: available
required_inputs: template_id, phone_number
optional_inputs: template_variables[] (mapped from board columns)
Action: send_follow_up_message
status: in_development