Notifyer System Integration with Zapier

Automate your WhatsApp messaging workflows with Zapier and Notifyer System

This guide covers every trigger and action available for the Notifyer System inside Zapier — so you can build fully automated WhatsApp workflows that send messages, schedule follow-ups, update contacts, and react to incoming and outgoing messages in real time.

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.

Available triggers & actions at a glance

The Notifyer System connects to Zapier through the Whatsable app. Once connected with your Notifyer API key, you get access to the following:

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

All triggers and actions in this guide use the Whatsable app on Zapier. Notifyer System users connect using their Notifyer API key.

Prerequisites

Before getting started, make sure you have:

Notifyer System Account

Active Notifyer System account with a subscription plan (Monthly or Pay-as-you-go) and a connected WhatsApp number

Zapier Account

Access to Zapier workflow automation platform

New to Notifyer System? Sign up here

Setting up your Notifyer System account

Complete the Embedding Process

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.

Set up message templates (if using template messages)

WhatsApp templates are pre-approved message formats required to initiate a new conversation with a contact. Create and get them approved in Notifyer before using them in Zapier.

How to create a template

Navigate to Templates

Go to Your Templates in your Notifyer dashboard

Create Template

Click the Create Template tab at the top of the page

Fill out the form

string

required

Choose a descriptive name for internal reference

string

required

Choose your template’s primary language

string

required

Select the appropriate message category (Marketing, Utility, Authentication)

image | document | video

Optional: Add an image, document, or video header

string

required

Craft your message content. Use {{1}}, {{2}} placeholders for dynamic variables

button

Optional: Configure call-to-action or quick reply buttons

Submit for review

Click Preview and Submit

Templates are typically reviewed within 24 hours. Utility and Authentication templates have the highest approval rates.

Get your Notifyer API key

In your Notifyer dashboard, navigate to API Keys
Copy your unique API key
Store it securely — you will need it when creating the Zapier connection

Never share your API key publicly or commit it to version control systems.

Connect Notifyer System to Zapier

Accept the Whatsable app invitation

Log in to your Notifyer System dashboard
Navigate to Connect to Zapier in the side menu
Click Continue in the connection guide popup
Click Accept & Build a Zap on the invitation page

The Whatsable app is now available in your Zapier account. You can find it by searching “Whatsable” in any Zap editor.

Create a new Zap

Log in to your Zapier account at zapier.com
Click + Create and select Zaps (or New Zap)
You are now in the Zap editor and ready to add your first step — follow the trigger or action setup guides in the Step Reference section below

Step Reference

Trigger

New Incoming or Outgoing WhatsApp Message

Type: Instant Trigger | App: Whatsable | Connection: Notifyer 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.” Fires in real time whenever a WhatsApp message event occurs in your Notifyer console. You can configure it to fire on incoming messages only, outgoing messages only, or both directions. Outgoing events include messages typed by hand in the WhatsApp Business app, messages sent from the Notifyer chat inbox, and messages sent by automations. This is the entry point for AI chatbot workflows, lead qualification, CRM syncing, and any automation that must react when a teammate replies on their phone.

Setting 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 from the results
Under Trigger Event, select New Incoming or Outgoing WhatsApp Message
Click Continue

Connect your Notifyer account

In the Account section, click Sign in to Whatsable
A dialog will appear asking for your API key — paste your Notifyer API key
Click Yes, Continue to Whatsable

You only need to do this once. Once your account is connected, you can reuse it across all Whatsable steps in any of your Zaps.

Make sure you are pasting the Notifyer API key, not the WhatsApp API key. Your Notifyer API key is found at console.notifyer-systems.com/api-key.

Configure the trigger

In the Configure section, you will see the following fields:

dropdown

required

Select Notifyer — this tells the app you are authenticating with a Notifyer System API key

dropdown

Choose how incoming trigger data is mapped to your Zap fields. Leave as default unless you have specific mapping requirements

Click Continue when done.

Test the trigger

Click Test trigger — Zapier will attempt to fetch a recent message event from your Notifyer console
If a test record is found, Zapier displays a sample data payload showing all available output fields
Review the fields to confirm the data looks 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 to pull a sample.

Once the test passes, your trigger is configured. Click Continue to add your first action step.

Trigger output fields

When this trigger fires, your Zap receives the following data fields from Notifyer. You can map any of these fields into your action steps.

Contact identity

text

The phone number of the contact (e.g. 14155550187). This is the contact who sent or received the message

text

Unique internal ID for this contact in Notifyer (UUID format)

text

The display name used for this contact in Notifyer

text

Comma-separated list of labels currently applied to this conversation (e.g. Hot Lead, Buyer Qualified, Urgent)

Message data

text

Type of the message: text, audio, image, or document

boolean

true when the contact sent a message to your business; false when your business sent a message to the contact. Use a Filter step after the trigger to act only on incoming or outgoing messages

text

Which system or person sent an outgoing message: "WhatsApp App" for the WhatsApp Business app, the teammate’s name for the Notifyer chat inbox, or the automation/app name for Make, Zapier, n8n, or API. Empty on incoming messages

boolean

true when a person sent the message (phone app or Notifyer inbox). false when a bot or automation sent it

text

Public URL of any file attached to the message (image, document, audio). Empty if the message has no attachment

boolean

true if this trigger was fired by a scheduled message being delivered; false for real-time messages

object

Present when the inbound message came from a Click-to-WhatsApp ad or post. Includes source_type, source_id, source_url (platform), headline, body, media_type, creative URLs, and ctwa_clid. Omitted on ordinary chats and on most follow-up messages. See Click-to-WhatsApp ads.

Conversation history

text

JSON array of recent messages in the conversation. Each item includes: type (user/bot), content, timestamp, content_type. Useful for passing full history to an AI model

text

The most recent message sent by the contact — the message that triggered this Zap run

text

The most recent message your business sent to this contact — helps prevent an AI from repeating the same response

number

Unix timestamp (milliseconds) of when the contact’s last message was received

number

Unix timestamp (milliseconds) of when your business last messaged this contact

text

A flat, readable version of the full conversation history — ideal for passing directly into an AI/LLM prompt without needing to parse the last_messages JSON array

AI context & automation fields

text

The AI context note stored on this contact in Notifyer. Contains lead details: name, email, preferences, background, language, etc. Set or update this using the Update a Contact action

text

Automation instructions for the AI — rules the AI follows automatically based on conversation events (e.g. “If budget confirmed and timeline under 6 months, notify the agent within 1 hour”)

text

Description of any messages currently scheduled to be sent to this contact at a future time

Use the incoming_message field with a Zapier Filter step to split logic between incoming messages (contacts writing to you) and outgoing messages (your business sending). Use send_by and was_message_by_human to see whether the WhatsApp Business app, a named teammate, or an automation sent it.

Incoming and outgoing WhatsApp messages

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

The payload is the same whether you use n8n, Make, Zapier, or a custom webhook. Watch the walkthrough on YouTube.

Direction, sending system, and team member

Use these three fields to tell what happened and who sent it:

boolean

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.

string

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
A team member’s name (for example `Axel Meta`)	Sent from the Notifyer chat inbox by that logged-in user
An automation or app name (Make, Zapier, n8n, API, bot)	Sent by that integration or bot

Empty or omitted on incoming messages.

boolean

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.

Example payload: message typed on the phone

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_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": null,
  "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 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:

{
  "incoming_message": false,
  "send_by": "Axel Meta",
  "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. 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.

Actions

Actions perform operations in Notifyer System — sending messages, scheduling follow-ups, updating contacts, and checking delivery status.

Send WhatsApp Message

Type: Action | App: Whatsable | Connection: Notifyer 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.” Send a WhatsApp message immediately to any phone number. Supports both template messages (to start a new conversation or send proactive outreach) and non-template messages (within an active 24-hour conversation window). Labels and notes set here appear directly in your Notifyer console — making this the core send action for all outbound WhatsApp automation.

Setting 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 Notifyer account

Select your connected Notifyer account from the dropdown, or click Sign in to Whatsable to add a new one using your Notifyer API key

Configure the message

In the Configure section, start by choosing your message type from the Configuration dropdown:

Send WhatsApp Template (to start conversation)
Send a non-template message (person must write to you first)

Use this to initiate a new conversation with a contact or send a proactive outreach message. Requires a Meta-approved WhatsApp template.

text

required

The recipient’s phone number in international format — digits only, no + or spaces (e.g. 14155550187). Map this from a previous trigger step or enter it directly

dropdown

required

Select from your approved templates. The dropdown shows a live preview of each template’s body, language, and category

text

required

If your template contains variables ({{1}}, {{2}}…), a separate field appears for each one. Map them to dynamic data from previous steps (e.g. {{contact_name}} from a form submission)

text

If your template has a media header (image, video, or document), enter the publicly accessible URL of that file. Only appears if your selected template includes a media header

text

If your template has a dynamic URL button, enter the full URL value including the dynamic portion

text

AI context about this contact (name, email, preferences, language, budget). This note is stored on the contact in Notifyer and the AI reads it to personalize future replies. It is not sent to the recipient

multiselect

Labels to apply to this conversation for internal tracking and routing. Labels appear in your Notifyer console and can be used in scheduling conditions

Use this to send a message within an active conversation — only possible within 24 hours of the contact’s last incoming message. Supports multiple message types.

text

required

The recipient’s phone number in international format — digits only, no + or spaces (e.g. 14155550187)

dropdown

required

Choose what type of message to send:

Text Message

text

required

The text content to send to the contact

boolean

Set to true to show a URL preview card when the message contains a link. Default: false

Image Message

url

required

Publicly accessible URL of the image file (JPEG, PNG, etc.)

text

Optional caption text displayed below the image

Video Message

url

required

Publicly accessible URL of the video file (MP4, etc.)

text

Optional caption text displayed below the video

Document Message

url

required

Publicly accessible URL of the document file (PDF, DOCX, etc.)

text

Optional caption for the document

text

required

The filename to display to the recipient (e.g. invoice-2026.pdf)

Audio Message

url

required

Publicly accessible URL of the audio file (MP3, OGG, etc.)

multiselect

Labels to apply to this conversation. Labels appear in your Notifyer console

text

AI context note for this contact — set or update the note that the AI reads to personalize future replies

Test the action

Click Continue to proceed to the Test section
Click Test step — Zapier will attempt to send a real message using the configuration you set
Check your WhatsApp to confirm the message was received
If the test passes, click Publish to activate your Zap (or continue adding more steps first)

Testing this action sends a real WhatsApp message. Use a personal test number during setup to avoid sending unintended messages to real contacts.

Schedule a Follow-Up Message

Type: Action | App: Whatsable | Connection: Notifyer 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.” Schedule a WhatsApp message to be sent at a future time, with an optional reply condition that automatically cancels the scheduled message if the recipient responds before it is sent. This is one of Notifyer’s most powerful features — use it to build no-reply follow-up sequences, re-engagement drips, and smart nurture workflows that stop automatically when a lead engages.

Setting 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 Notifyer account

Select your connected Notifyer account, or add a new one with your Notifyer API key

Choose your message type

In the Configure section, select either Send WhatsApp Template or Send a non-template message from the Configuration dropdown.The message fields are identical to the Send WhatsApp Message action above — fill in the phone number, select your template (or message type), map any variables, and optionally set labels and a note.

Set when to send the message

Relative (Delay from now)
Specific Date & Time

Send the message after a set delay from the moment this Zap step runs:

select

required

Choose: 1, 2, 3, 4, 5, 10, 15, 20, 30, 60, 90, or 120

select

required

Choose: Minutes, Hours, or Days

Set a reply condition (recommended)

The reply condition tells Notifyer to automatically cancel the scheduled message if the recipient replies within the specified timeframe — preventing follow-up messages from reaching contacts who are already engaged in a conversation with you.

select

Condition	The message is cancelled if…
Recipient did not reply after my last message	The contact replies at any point before the scheduled send time
Recipient never replied to any of my messages	The contact has never replied to any of your messages
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

“Recipient did not reply after my last message” is the recommended default for most follow-up sequences — it ensures that no follow-up is sent to contacts who are already in an active conversation with you. This protects your WhatsApp account reputation and keeps communication natural.

Set a label condition (optional)

Restrict the scheduled message so it only sends if the contact has — or does not have — a specific label at the time of sending:

select

Include — only send the message if the contact currently has this label
Does Not Include — only send the message if the contact does NOT have this label

select

The label to evaluate when the scheduled send time arrives

Test and activate

Click Continue, then Test step to confirm the follow-up is queued in Notifyer. You can view all pending scheduled messages in your Notifyer console under the contact’s conversation.

Scheduled messages are visible in your Notifyer console under each contact’s conversation. You can manually cancel any scheduled message there at any time.

Update a Contact

Type: Action | App: Whatsable | Connection: Notifyer 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.” Update a contact’s details in your Notifyer console — set their display name, add or remove conversation labels, or update the AI context note. Use this to keep Notifyer contacts in sync with your CRM, form submissions, or any other external data source.

Setting 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 Notifyer account

Select your connected Notifyer account, or add a new one with your Notifyer API key

Fill in the contact fields

text

required

The phone number of the contact to update, in international format — digits only, no + or spaces (e.g. 14155550187). This is used to look up the contact in your Notifyer console. If the contact does not yet exist, a new record will be created

text

Update the display name shown for this contact in the Notifyer chat interface

text

Set or update the AI context note for this contact. The AI reads this field to personalize its responses and qualify leads more accurately. A well-structured note dramatically improves AI conversation quality.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 6pm

multiselect

One or more labels to add to this contact. Labels appear in the Notifyer console and can be used in scheduling conditions and routing rules

multiselect

One or more labels to remove from this contact. Select Remove All to clear every label from this contact at once

Test the action

Click Continue, then Test step to confirm the contact is updated in your Notifyer console. Open the contact in your Notifyer dashboard to verify the name, labels, and note appear correctly.

Place Update a Contact as the first action step in your Zap — before Send WhatsApp Message — to populate the AI Note from form or CRM data. This ensures the AI has full context about the lead before the very first message is sent.

Get Delivery Status of a Message

Type: Action | App: Whatsable | Connection: Notifyer 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.” Check whether a previously sent WhatsApp message was successfully delivered to the recipient. Use this to build fallback automation — if a message was not delivered (for example, because the phone number is incorrect or inactive), automatically trigger an alternative action such as sending a fallback email.

Setting 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 Notifyer account

Select your connected Notifyer account, or add a new one with your Notifyer API key

Enter the Message ID

text

required

The ID of the message to check. This is returned in the output data of the Send WhatsApp Message or Schedule a Follow-Up Message action that ran earlier in the same Zap. Map it from that step’s output using Zapier’s data mapper

Click Continue when done.

Test and use the result

Click Test step. Zapier will call Notifyer and return the delivery status of that message.Use the returned status field in a Filter step immediately after this action to create two paths:

Delivered → continue your main workflow
Not Delivered → send a fallback email via Gmail, Outlook, or another email app

Add a Zapier Filter or Paths step after Get Delivery Status to branch your Zap: route successfully delivered messages down one path and undelivered messages down another where you send a fallback email or alert.

Building a complete Zap: step-by-step example

Here is a practical end-to-end example: 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 fires instantly when someone fills in your lead capture form

Action: Update a Contact

Add Whatsable — Update a Contact. Map form fields into the Note field:

email: {{email}} | Name: {{name}} | Budget: {{budget}} | Language: {{language}}

Add relevant labels: New Lead, Form SubmissionThis gives the AI complete context before any conversation starts.

Action: Send WhatsApp Message (Template)

Add Whatsable — Send WhatsApp Message set to the template configuration. Select your approved welcome template, then map the recipient’s phone number and any template variables from the form data

Action: Schedule a Follow-Up Message

Add Whatsable — Schedule a Follow-Up Message. Configure:

Message: a follow-up template (e.g. Hi {{1}}, just checking in...)
Schedule: 24 Hours (Relative delay)
Reply condition: Recipient did not reply after my last message

This follow-up cancels automatically if the lead responds to your first message.

Test and activate

Click Test on each step to verify all steps show a success result
Click Publish to save your Zap
Toggle the On/Off switch to On to activate it

Example use cases

AI chatbot lead qualification

Trigger on incoming messages, pass conversation_paragraph and note to OpenAI, then send the AI’s reply back via Send WhatsApp Message

Smart follow-up sequences

Schedule a series of follow-ups with reply conditions — they cancel automatically when the lead engages so you never over-message

CRM-to-WhatsApp sync

When a deal stage changes in HubSpot or Pipedrive, use Update a Contact to update the AI note, then send a relevant WhatsApp template

Form-to-WhatsApp onboarding

When a form is submitted, instantly set AI context via Update a Contact, then send a personalized onboarding template message

Delivery fallback

Use Get Delivery Status after sending a message — if undelivered, route to a fallback email via Gmail or Outlook

Real-time CRM logging

Trigger on every incoming or outgoing message and log the conversation data to a Google Sheet, Airtable, or your CRM in real time

Best practices

Set the AI Note before sending

Always use Update a Contact as the first action in new-lead Zaps — before Send WhatsApp Message. Setting the note field with structured lead data (name, email, preferences, language, budget) dramatically improves AI conversation quality and lead qualification accuracy.

Always use reply conditions on follow-ups

Set a reply condition on every Schedule a Follow-Up Message action. “Recipient did not reply after my last message” is the safest choice — it ensures no follow-up is sent to contacts who are already in an active conversation. This also protects your WhatsApp account reputation.

Use labels on every send and update

Both Send WhatsApp Message and Update a Contact let you attach labels to conversations. Use labels to tag contacts (e.g. Hot Lead, Form Submission, Appointment Set) — they appear in your Notifyer console and can be used in label conditions for scheduling.

Use conversation_paragraph for AI prompts

When building AI chatbot Zaps, map the conversation_paragraph trigger field to your OpenAI or Claude prompt. It is a pre-formatted, readable version of the full conversation — much simpler to include in a prompt than parsing the raw last_messages JSON array.

Filter by incoming_message for one-direction flows

The trigger fires on both incoming and outgoing messages by default. Add a Zapier Filter step immediately after the trigger and filter by incoming_message = true if you only want your Zap to react when a contact writes to you, or incoming_message = false to react only when your business sends a message (including replies typed in the WhatsApp Business app). Use send_by to distinguish "WhatsApp App", a teammate name, and automations.

Capture Click-to-WhatsApp referral on the first message

When referral is present, store source_id, source_url, headline, and ctwa_clid on the contact immediately. Later messages in the same chat usually omit referral. Use source_url to see Instagram vs Facebook, and source_id to compare creatives.

Phone number format

Always provide phone numbers in full international format — digits only, no +, spaces, or dashes (e.g. 14155550187 for US, 447911123456 for UK, 966501234567 for Saudi Arabia).

Troubleshooting

Trigger not firing?

Check your Zap is turned on

The trigger only fires when the Zap is toggled On. Go to your Zap’s overview page and confirm the On/Off switch is set to On

Verify your connected account

Open the trigger step in your Zap editor, go to the Account section, and confirm your Whatsable connected account shows no errors. If it does, disconnect and reconnect with your Notifyer API key

Send a test message

Zapier’s Test trigger button requires at least one recent event in your Notifyer console. Send a WhatsApp message to your connected number — or type a reply in the WhatsApp Business app — and then re-test. You do not need to delete the WhatsApp Business app.

Check your Notifyer console

If messages appear in your Notifyer console but the trigger still does not fire, contact support — there may be a webhook configuration issue

Messages not sending?

Check the connected account

Verify your Notifyer API key is valid and the correct connected account is selected in the action step

Check phone number format

Phone number must be digits only in full international format, no + or spaces (e.g. 14155550187)

Template not approved?

Ensure the selected template has Approved status in your Notifyer dashboard. Pending or rejected templates will cause an error

24-hour window for non-template messages

Non-template messages can only be sent within 24 hours of the contact’s last incoming message. Outside this window you must use an approved template

Check subscription credits

Verify your Notifyer subscription is active and has sufficient message credits

Template variables not populating?

Fill all required variable fields

All body variable fields (Body 1, Body 2, etc.) are required — confirm none are empty or mapped to fields that return empty values

Check the template preview

The template dropdown in the action configuration shows a preview of the body text and example values — use this as a reference to understand what each variable slot expects

Media URL must be public

If your template has a media header, the URL must be publicly accessible. Test it by opening it in an incognito browser window

Scheduled message was not sent?

Reply condition may have cancelled it

If you set a reply condition and the contact replied before the scheduled send time, the message was intentionally cancelled. Check the contact’s conversation in your Notifyer console

Verify the delay settings

Confirm the delay value and unit are correct (e.g. 24 + Hours, not 24 + Minutes)

Check your Zap run history

In Zapier, go to Zap History and find the run where the Schedule a Follow-Up Message step executed. Confirm the step shows a success status at the time the trigger fired

Update a Contact changes not appearing in Notifyer?

Verify the phone number

The phone number must exactly match the contact’s number in Notifyer (same international format). If no contact with that number exists, Notifyer will create a new record

Confirm you are using the correct connection

The Update a Contact action requires the Notifyer connection (the one authenticated with your Notifyer API key). Confirm the correct connected account is selected in the action step

Get Delivery Status returning no result?

Map the correct Message ID

The Message ID field must be mapped from the output of a Send WhatsApp Message or Schedule a Follow-Up Message step in the same Zap. Make sure you are mapping the message_id field from the correct preceding action step

Allow time for delivery

Delivery status may take a few seconds to update after a message is sent. If checking status immediately after sending, consider adding a short delay using Zapier’s Delay action before the Get Delivery Status step

Need help?

Email support

Contact team@whatsable.app

Schedule a demo

Book a personalized walkthrough

Live chat

Click the green chat button in the bottom right corner of the Notifyer System dashboard

​Notifyer System Integration with Zapier

​Available triggers & actions at a glance

Trigger (Instant)

Actions

​Prerequisites

Notifyer System Account

Zapier Account

​Setting up your Notifyer System account

​Connect Notifyer System to Zapier

​Step Reference

​Trigger

​New Incoming or Outgoing WhatsApp Message

​Setting up the trigger

​Trigger output fields

​Incoming and outgoing WhatsApp messages

​Direction, sending system, and team member

​Example payload: message typed on the phone

​Click-to-WhatsApp ad attribution

​Actions

​Send WhatsApp Message

​Setting up the action

​Schedule a Follow-Up Message

​Setting up the action

​Update a Contact

​Setting up the action

​Get Delivery Status of a Message

​Setting up the action

​Building a complete Zap: step-by-step example

​Example use cases

AI chatbot lead qualification

Smart follow-up sequences

CRM-to-WhatsApp sync

Form-to-WhatsApp onboarding

Delivery fallback

Real-time CRM logging

​Best practices

​Troubleshooting

​Need help?

Email support

Schedule a demo

Live chat

Notifyer System Integration with Zapier

Available triggers & actions at a glance

Prerequisites

Setting up your Notifyer System account

Connect Notifyer System to Zapier

Step Reference

Trigger

New Incoming or Outgoing WhatsApp Message

Setting up the trigger

Trigger output fields

Incoming and outgoing WhatsApp messages

Direction, sending system, and team member

Example payload: message typed on the phone

Click-to-WhatsApp ad attribution

Actions

Send WhatsApp Message

Setting up the action

Schedule a Follow-Up Message

Setting up the action

Update a Contact

Setting up the action

Get Delivery Status of a Message

Setting up the action

Building a complete Zap: step-by-step example

Example use cases

Best practices

Troubleshooting

Need help?