Connect Notifyer System with n8n. Trigger workflows on incoming and outgoing WhatsApp messages — including replies typed in the WhatsApp Business app. Coexistence is supported; you do not delete the app on your phone.
Automate your WhatsApp messaging workflows with n8n and Notifyer System
This guide walks you through connecting Notifyer System with n8n to create automated WhatsApp workflows — including triggers that fire when someone types a reply in the WhatsApp Business app, and Click-to-WhatsApp ad referral data (source_id, source_url, ctwa_clid) on inbound leads.
Meta WhatsApp Coexistence is supported on Notifyer System. 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 Notifyer chat inbox, and automations (Make, Zapier, n8n, API, and webhooks) at the same time.
Before sending WhatsApp messages, complete the embedding process, which connects your WhatsApp Business account to Notifyer System. You do not need to delete the WhatsApp Business app — coexistence is supported.
The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
2
Set up message templates
Notifyer System 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 Templates
Go to Your Templates in your Notifyer dashboard
2
Create Template
Click the Create Template tab at the top of the page
3
Fill out the form
Complete the template creation form with the following details:
Introducing the New Features of N8N Nodes Version 2.3.3
1
Set up your n8n workflow
Log in to your n8n account
Create a new workflow by clicking Create Workflow
Add a trigger node of your choice:
Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
Connect and configure your trigger according to your use case
WhatsAble trigger node (incoming and outgoing)
Use the WhatsAble trigger so n8n runs when WhatsApp messages are received or sent — including replies typed in the WhatsApp Business app on your phone. Select the incoming and outgoing credential type so those events reach n8n, not only the Notifyer inbox.
1
Add WhatsAble trigger node
Follow these steps to add the WhatsAble trigger node to your workflow:
Click the + button in your workflow canvas to add a new node
Search for “WhatsAble” in the node library search bar
Select the node displaying the official WhatsAble logo
From the available trigger options, choose On new Incoming message event. That is the node’s label — when outgoing is enabled (credential Notifyer System incoming and outgoing messages), the same trigger also fires for outgoing messages, including replies typed in the WhatsApp Business app. Filter with incoming_message.
Adding the WhatsAble trigger labelled On new Incoming message event
The trigger listens for WhatsApp activity and starts your workflow. Outgoing events include messages typed in the WhatsApp Business app (send_by: WhatsApp App).
2
Configure authentication credentials
Set up your WhatsAble API credentials to establish a secure connection:Webhook URL Configuration:
In the WhatsAble Trigger node parameters, locate the Webhook URLs section at the top
Select Production URL and copy the generated URL by clicking on it
Store this URL securely as you’ll need it for the credential setup
Copying the Production URL for webhook configuration
Credential Creation:
In the Credential to connect with dropdown, click + Create new credential
Select WhatsAble Notifyer System API as your connection method. For phone-app and inbox replies, choose the credential that covers Notifyer System incoming and outgoing messages
Enter your Notifyer System API key in the API Key field
Paste the Production URL you copied earlier into the Production URL field
Assign a descriptive name to your credential (e.g., “WhatsAble Production”)
Click Save to securely store your credentials
Credential configuration for WhatsAble Trigger node
Your API credentials are encrypted and stored securely. Never share your API key publicly or commit it to version control.
3
Test and activate workflow
Complete the setup by testing and activating your trigger:Response Configuration:
In the Respond dropdown, select your preferred response timing:
Immediately: Responds as soon as the trigger fires
When Last Node Finishes: Waits for the entire workflow to complete before responding
Testing:
Click Execute step on the WhatsAble node to run a test
Verify the connection is working by checking for a success confirmation
Review any error messages if the test fails and adjust your configuration accordingly
Once activated, your workflow processes incoming and outgoing messages according to your configured logic. Use incoming_message, send_by, and was_message_by_human in later nodes to branch on direction and sender.
Remember to test your workflow thoroughly before activating it in production to ensure it behaves as expected.
2
Add the Notifyer System node
Click the + button after your trigger node
Search for “WhatsAble” in the nodes panel
Select the node with the official WhatsAble logo
After selecting the WhatsAble node, choose ‘Send template via Notifyer’ or ‘Send non-template via Notifyer’ as needed.
WhatsAble Node: Send Message via Send template via Notifyer / Send non-template via Notifyer
3
Configure Notifyer System credential
In the WhatsAble node Parameters, find the Credential to connect with dropdown
Select + Create new credential
Enter your Notifyer System API key that you copied earlier
Name your credential (e.g., “Notifyer Production”)
Click Save to store your credential
Configuring Notifyer System credential
4
Configure your message
In Resource dropdown, select Send Message
In the Operation dropdown, choose Send template via Notifyer for template messages or Send non‑template via Notifyer for regular messages (only works within the 24‑hour window).
(Optional) Select the date and time to schedule when your message will be sent
1
Recipient Phone Number
Enter the Phone Number with country code
2
Select message type
Choose from the following message types:
Text Message
For plain text messages
Document Message
For sending documents (PDF, Word, etc.)
Image Message
For sending images (JPEG, PNG, etc.)
Video Message
For sending videos (MP4, 3GP, etc.)
3
Complete message details
Based on your selected message type, fill in the required fields:
For text messages: Enter your message content
For media messages: Provide a publicly accessible URL to your file
Optional caption (for media files)
For all media types, ensure your file URLs are publicly accessible and match the supported file formats.
4
Label Names or IDs
(Optional) Select the label(s) you created in Chat Notifyer for internal tracking
5
Schedule Message
(Optional) Select the date and time to schedule when your message will be sent
5
Test and activate your workflow
Click Test Step on the Notifyer node to verify it’s working correctly
If the test is successful, you’ll see a confirmation message
Return to your workflow
Click Save to save your entire workflow
Toggle the Active switch in the top-right corner to activate your workflow
Your automated messaging workflow is now operational! Whenever your trigger conditions are met, n8n will automatically send WhatsApp messages through Notifyer System.
Notifyer delivers both incoming and outgoing messages to your webhook or automation trigger — including messages typed by hand in the WhatsApp Business app on your phone.This is possible because Notifyer 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 Notifyer web inbox.
Trigger n8n (or any webhook) from WhatsApp messages — including replies typed in the WhatsApp Business app
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.
true when a person sent the message (WhatsApp Business app or Notifyer chat inbox). false when a bot or automation sent it. Combine with send_by to see both whether a human sent it and which teammate or system did.
This is the JSON Notifyer 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_message_of_bot is the last message your business sent — whether a human typed it in the WhatsApp Business app or the Notifyer inbox, or a bot/automation sent it. last_messages is a JSON string of the last ~20 messages (parse it before iterating). phone_number may arrive as a number rather than a string.
When the same person sends from the Notifyer chat inbox instead of the phone app, the payload is identical except:
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. Notifyer 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" }}
If your delivery includes the Cloud API envelope instead of a flattened Notifyer payload, the same object lives at entry[].changes[].value.messages[].referral. Full field reference and a complete example: Message webhooks — Click-to-WhatsApp ads.
Ensure your API key is entered correctly in the n8n credentials
2
Check phone numbers
Confirm phone numbers are in the correct international format (e.g., +14155552671)
3
Check subscription
Verify your Notifyer subscription is active and has available credits
4
Outgoing events from the WhatsApp Business app
Use the trigger labelled On new Incoming message event with the Notifyer System incoming and outgoing messages credential. When outgoing is enabled, that same trigger also fires for outgoing messages. Confirm incoming_message is false and send_by is WhatsApp App when you type a test reply on your phone. You do not need to delete the WhatsApp Business app.
Template errors?
1
Variable check
Verify all required variables are included in your template message
2
Format verification
Check that variable formats match the expected values (text, number, date, etc.)
3
Template name
Ensure you’re using the correct template name exactly as it appears in your dashboard
Media not displaying?
1
URL access
Confirm your media URLs are publicly accessible (test in an incognito browser)
