monday.com
Docs

Notifyer Systems integration with monday.com

Learn how to seamlessly integrate monday.com with Notifyer Systems (WhatsAble) for automated WhatsApp messaging directly inside your boards.

monday.com integration with Notifyer System
Automate your WhatsApp messaging workflows with monday.com and Notifyer Systems.
This guide walks you through connecting Notifyer Systems with monday.com to create powerful automated WhatsApp messaging workflows — syncing conversations to your boards and triggering messages from board events, all through monday.com's built-in Workflow Builder.

Prerequisites

Before getting started, make sure you have:

Notifyer Systems account
Active account with a connected WhatsApp number and a subscription plan (Pro or Agency).
monday.com account
Access to monday.com with admin or member-level permissions.
Important
Your WhatsApp number must already be connected inside Notifyer before starting the monday.com integration.
New to Notifyer Systems?Sign up here

Setting up your Notifyer Systems account

Step 1 — Complete the embedding process

Before sending WhatsApp messages, you must complete the platform embedding process, which connects your WhatsApp Business account to Notifyer Systems.

The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
Step 2 — Set up message templates

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.

Option A — Template messages

WhatsApp templates are pre-approved message formats that allow for personalization while maintaining compliance with WhatsApp policies.

  1. Navigate to Your Templates in your dashboard.
  2. Click Create Template at the top of the page.
  3. Fill out the form (template name, language, category, optional header, message body, variables like {{1}}, buttons).
  4. Click Preview and Submit.
Template Creation Interface
Template creation interface.
Templates typically get reviewed within 24 hours. Creating compliant templates that avoid promotional language increases approval chances.
Option B — Non-template messages

For simpler communications within the 24-hour window, you can send non-template messages including text, images, documents, and videos.

Note
Non-template messages can only be sent within the 24-hour customer service window after a customer initiates contact with your business.

Connect Notifyer Systems to monday.com

Once your Notifyer Systems account is configured, follow these steps to connect monday.com and start building workflows.

Step 1 — Open the monday.com integration page
  1. Log in to your Notifyer Console.
  2. In the sidebar, scroll to Connect To.
  3. Click monday.com.
monday.com option in the Notifyer sidebar under Connect To
monday.com option in the Notifyer sidebar under Connect To.
Step 2 — Install WhatsAble on monday.com
  1. Click Install WhatsAble next to Step 1.
  2. You will be redirected to the monday.com marketplace listing.
  3. Follow monday.com's installation flow for your workspace.
Install WhatsAble button on the monday.com integration page
Install WhatsAble button on the monday.com integration page.
If you are already logged into monday.com, the installation proceeds directly. Otherwise, monday.com will prompt you to log in first.
Step 3 — Log in and authorize WhatsAble
  1. Sign in to monday.com (Email/password, Google, or Microsoft).
  2. Review the consent screen.
  3. Click Authorize to grant permissions.
monday.com authorization permissions screen for WhatsAble
monday.com authorization permissions screen for WhatsAble.

WhatsAble requests permissions exclusively for workflow automation. Examples include creating/updating board items, reading files, and managing webhooks.

WhatsAble is an official Meta Tech Provider and the integration is safe to authorize.
Step 4 — Confirm the connection

After authorization, you'll be redirected back to the Notifyer Console. The green Successfully Connected to monday.com banner confirms the integration is live.

Successfully Connected to monday.com confirmation screen
Successfully Connected to monday.com confirmation screen.
Connected
Your Notifyer Systems account is now linked to monday.com. Proceed to create workflows using the triggers and actions below.

Using the WhatsAble Live Chat item view in monday.com

If you prefer, you can authorize and use WhatsAble directly from inside monday.com via the WhatsAble Live Chat item view.

Step 1 — Add the WhatsAble Live Chat item view and authorize

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 Live Chat item view authorization in monday.com
Authorize WhatsAble from the monday.com item view (WhatsAble Live Chat).
Step 2 — Connect your WhatsApp Business account (if needed)

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

Connect WhatsApp Business account in WhatsAble before using monday.com
Connect your WhatsApp Business account in WhatsAble if it is not connected yet.
Step 3 — Send and receive messages from the item view

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

WhatsAble Live Chat inside monday.com item view
Use WhatsAble Live Chat inside monday.com to send and receive messages.

Workflow automation

With the integration connected, WhatsAble exposes 3 triggers and 2 actions inside monday.com's Workflow Builder.

Triggers

Triggers define when a workflow fires.

Trigger 1 — When New Incoming Chat Received

Fires: Once, the first time an unknown contact sends your business a WhatsApp message.

WhatsAble trigger: When you receive a WhatsApp message from a new phone number
Choose trigger: When you receive a WhatsApp message from a new phone number.
FieldTypeDescription
nameTextContact's display name
phonePhoneNumber in international format
countryTextCountry detected from the phone number
labelTextLabel auto-assigned by WhatsAble rules
messageTextBody of the incoming message
attachment_urlURLDirect link to any media attachment
last_message_timeDate/TimeTimestamp of the incoming message
ai_enabledBooleanWhether the AI agent is active for this chat
automation_noteTextNote injected by an upstream automation rule
Note
sent_by and is_incoming are not available on this trigger — the message is always incoming.
Trigger 2 — When New Outgoing Chat Created

Fires: Once, the first time you send a WhatsApp message to a contact that does not yet exist in WhatsAble.

WhatsAble trigger: When you send a message to a new WhatsApp contact
Choose trigger: When you send a message to a new WhatsApp contact.
FieldTypeDescription
nameTextContact's display name (may be blank if not yet resolved)
phonePhoneContact's phone number
countryTextDetected country
labelTextLabel assigned to the contact
messageTextBody of the outgoing message
attachment_urlURLLink to any attached media
last_message_timeDate/TimeTimestamp of the outgoing message
sent_byTextSender name — team member or automation/app name
ai_enabledBooleanWhether the AI agent is active
automation_noteTextNote from an automation rule, if applicable
Note
is_incoming is not available on this trigger — the message is always outgoing.
Trigger 3 — When New Message Received or Sent in WhatsApp

Fires: Every time, for every message — both incoming and outgoing.

WhatsAble trigger: When you receive or send any WhatsApp message
Choose trigger: When you receive or send any WhatsApp message.
FieldTypeDescription
nameTextContact's display name
phonePhoneContact's phone number
countryTextDetected country
labelTextAssigned label
messageTextMessage body
attachment_urlURLURL of any media attachment
last_message_timeDate/TimeMessage timestamp
sent_byTextSender identifier (outgoing messages only)
is_incomingBooleantrue if received, false if sent
ai_enabledBooleanAI agent state
automation_noteTextAutomation-injected note, if any
Map is_incoming to a Checkbox column in monday.com to distinguish customer messages from agent replies.
Trigger quick reference
TriggerFires for existing contacts?Fires multiple times?Direction
New Incoming Chat ReceivedNoFirst time onlyInbound
New Outgoing Chat CreatedNoFirst time onlyOutbound
New Message Received or SentYesEvery messageBoth
Rule of thumb
Use Triggers 1 and 2 for contact creation. Use Trigger 3 for ongoing conversation updates.

Actions

Actions define what happens when a trigger fires.

Action 1 — Send Template Message

Sends an approved WhatsApp Business template message to a contact.

WhatsAble action: Send a template message
Choose action: Send a template message.
  1. Select Send Template Message from the WhatsAble action list.
  2. Choose the template from the dropdown.
  3. Map template variables (e.g. {{1}}) to monday.com column values.
  4. Map the phone number field to your board's phone/mobile column.
Only Meta-approved templates appear in the dropdown. Templates pending review will not be listed.
Action 2 — Send Follow-Up Message
This action is currently in development and will be available in a future release.

Data field reference

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.

Workflow examples

The following examples are real working workflows you can replicate inside monday.com's Workflow Builder.

Example 1 — Sync Every WhatsApp Message to Your Board

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.

Workflow: Sync Every WhatsApp Message to Your Board
Workflow with Find Matching Item and Found/Not Found branches.
Note
This workflow uses monday.com's Find Matching Item block to prevent duplicates. Match phone numbers in E.164 format (e.g. +34612345678).
Example 2 — Log New Outbound Contacts as monday.com Items

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.

Workflow: Log New Outbound Contacts as monday.com Items
Workflow with Create Item and Create Update.
Example 3 — Notify Customer via WhatsApp on Status Change

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

Workflow: Notify Customer via WhatsApp on Status Change
Status trigger + Send Template Message action.
Only Meta-approved templates can be sent via this action.
Full video walkthrough: connect WhatsAble with monday.com and build WhatsApp workflows.

Example use cases

Lead capture
Automatically create items when new WhatsApp contacts reach out
Support tickets
Sync support conversations and track resolution status
Order confirmations
Send template messages when an order status changes
Sales follow-up
Log outbound prospecting messages as new items
Activity updates
Keep board items in sync with every message
Appointment reminders
Trigger WhatsApp reminders from status changes

Disconnecting

To remove the connection, go to Notifyer Console → Connect To → monday.com and click Disconnect.

Disconnecting immediately stops all active WhatsAble-powered workflows in monday.com until the integration is reconnected.

Best practices

Use Find Matching Item for deduplication
Use monday.com's native Find Matching Item block filtering on the phone column to avoid duplicate items. A common pattern is match type equals, pick last_created_item, then branch on found / not found.
Store phone numbers in E.164 format
WhatsAble returns phone numbers in E.164 format (e.g. +34612345678). Ensure your monday.com phone column stores numbers in the same format for reliable matching.
Use templates for compliance
Whenever possible, use Meta-approved templates for better deliverability and compliance with WhatsApp Business policies.
Test workflows before production
Always test your workflows with test phone numbers before activating them for production use.
Monitor Run History
Regularly check Run History in monday.com's Workflow Builder to identify and resolve any failed runs.

Troubleshooting

Install WhatsAble button opens monday.com but nothing happens
Pop-ups may be blocked in your browser. Allow popups from your Notifyer Console URL and try again.
Step 1 still shows incomplete after installation
Refresh the Notifyer Console page. It needs a reload to detect that Step 1 is complete before enabling the Authorize button.
Authorization screen shows an error
Ensure you are authorizing with a monday.com account that has admin or sufficient member-level permissions. Guest accounts cannot authorize third-party integrations.
Workflow triggered but no item was created
If using Trigger 1 or 2, verify whether the contact already exists in your WhatsAble system. These triggers only fire for first-time contacts. Use Trigger 3 for existing contacts.
Phone number not matching in Find Matching Item
WhatsAble returns E.164 phone numbers (e.g. +34612345678). Make sure your monday.com phone column stores the same format.
Template not appearing in Send Template dropdown
Only Meta-approved templates are listed. Check the template status in Notifyer under Settings → Templates.
sent_by field is blank
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.
Workflow shows Failed in Run History
Open Run History and expand the failed run to see which step errored. Common causes include an unmapped required phone number field, invalid template variables, or a deleted board column that was previously mapped.

Technical reference

Trigger and action schemas for automation builders

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
Idempotency notes
Triggers 1 and 2 fire at most once per phone number. Trigger 3 fires on every message event and typically needs explicit deduplication via the Find Matching Item pattern.

Need help?

Email support
team@whatsable.app
Schedule a demo
Book a personalized walkthrough
Live chat
Click the red chat button in the bottom right corner of the dashboard.
For additional integrations (Make, Zapier, n8n, Pipedrive), check our docs at docs.whatsable.app.
© 2026 WhatsAble. All rights reserved.