Notifyer System Integration with Make

Automate your WhatsApp messaging workflows with Make and Notifyer System

This guide covers every module available for the Notifyer System inside Make — including all triggers, actions, and the search module — so you can build fully automated WhatsApp workflows.

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 modules at a glance

The Notifyer System is part of the WhatsAble for WhatsApp Business app on Make. Once installed, you get access to the following modules using your Notifyer API key:

Triggers (Instant)

Incoming Messages from console (Notifyer System)
Incoming & Outgoing Messages from console (Notifyer System)

Actions

Send WhatsApp Message
Schedule a follow-up Message
Update a Contact

Search

Get delivery status of a message

All modules in this guide are part of the WhatsAble for WhatsApp Business app on Make. 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

Make Account

Access to Make 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 Make.

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 Make connection

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

Connect Notifyer System to Make

Install the app in Make

Log in to your Make account
Navigate to your Notifyer System dashboard and select Connect to Make in the side menu
Click Continue in the connection guide popup
Click Install, select your Make organization at the bottom of the screen, then click Install again

You need Admin, Owner, or App Developer role in your Make organization to install apps.

The WhatsAble for WhatsApp Business app is now installed and ready to use in your Make scenarios

Create a new Make scenario

Log in to your Make account at make.com
Click + Create a new scenario
You are now ready to add your first module — follow the trigger setup guide in the Module Reference section below

Module Reference

Triggers

Instant triggers fire in real time whenever a qualifying event occurs in your Notifyer console. Both triggers below use the WhatsAble for WhatsApp Business app in Make and require a webhook plus your Notifyer API key connection.

Both triggers are Instant — they fire immediately when a message event occurs in your Notifyer console.

Setting up a Notifyer trigger in Make

Both Notifyer triggers follow the same 5-step setup in Make. The only difference is which trigger you select in Step 1.

Step 1 — Select your trigger

In your scenario, click the large + button to add a module
Search for WhatsAble or WhatsAble for WhatsApp Business
Open the WhatsAble for WhatsApp Business app
Under Triggers, select the trigger you need:

Trigger	When to use it
Incoming Messages from console (Notifyer System)	Fires only when a contact sends your business a message
Incoming & Outgoing Messages from console (Notifyer System)	Fires on every message — both incoming and outgoing, including replies typed in the WhatsApp Business app

Step 2 — Create a webhook

After selecting the trigger, the module configuration window opens. The first required field is Webhook.

Click the Add button next to the Webhook dropdown (the dropdown will show “Choose a hook…” if no webhook exists yet)
This opens the Create a webhook dialog

Step 3 — Name your webhook and set up a connection

In the Create a webhook dialog:

Enter a Webhook name — use something descriptive so you can identify it later (e.g. My Notifyer Systems webhook)
Under Connection, either:
- Select an existing connection if you have already connected Notifyer to Make before, or
- Click Add next to the Connection dropdown to create a new connection (continue to Step 4)
If you already have a connection selected, click Save to create the webhook and skip to Step 5

Step 4 — Create your Notifyer connection (first time only)

If you clicked Add in Step 3, the Create a connection dialog opens on top of the webhook dialog.

Enter a Connection name (e.g. My Notifyer only connection)
Paste your Notifyer API key in the API Key field — get this from your Notifyer API Keys page
Click Save

Make validates your API key automatically. Once saved, you return to the Create a webhook dialog with your new connection selected.

You only need to create this connection once. All future Notifyer modules in Make can reuse the same saved connection.

Back in the Create a webhook dialog, click Save to finish creating the webhook.

Step 5 — Save the trigger and activate your scenario

You are now back in the main module configuration window. The webhook you created is selected and a Webhook URL is displayed (e.g. https://hook.eu1.make.com/...).

Confirm your webhook is selected in the Webhook dropdown
Click Save to finish configuring the trigger module
Toggle your scenario to Active (or click Run once to test first)

Your trigger is now live. When a matching message event occurs in your Notifyer console, Make will run your scenario automatically.

Set the scenario schedule to Immediately as data arrives (shown in the bottom toolbar) so instant triggers fire without delay.

Incoming Messages from console (Notifyer System)

Type: Instant Trigger | Connection: Notifyer only

Fires every time an incoming message arrives in your Notifyer console. This is the full-featured trigger for building AI chatbot workflows, lead qualification, CRM updates, and real-time automations — it exposes all conversation context fields including the AI note, conversation history, and scheduling data. Description in Make: “Incoming Messages from console (Notifyer System)” How to set up: Follow the 5-step trigger setup guide above. In Step 1, select Incoming Messages from console (Notifyer System) from the Triggers list. Output fields — everything your scenario receives when triggered:

Contact identity

text

The phone number of the person who sent the message (e.g. 14155550187)

text

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

text

The first name or display name used by the AI to address this contact in conversation

text

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

Message data

text

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

boolean

true for this trigger — confirms this is an inbound message from the contact

text

Empty on this incoming-only trigger. On the incoming and outgoing trigger, this identifies the sending system or teammate (see below)

boolean

true when a person sent the message

text

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

boolean

true if triggered 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. Each item includes: type (user/bot), content, timestamp, content_type. Useful for passing full history to an AI

text

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

text

The most recent message your business sent to this contact — helps AI avoid repeating itself

number

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

number

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

text

A flat, readable version of the full conversation history — ideal for passing directly to an AI/LLM prompt without parsing 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 this via the Update a Contact action or directly in the Notifyer console

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 queued/scheduled to be sent to this contact at a future time

Incoming & Outgoing Messages from console (Notifyer System)

Type: Instant Trigger | Connection: Notifyer only

Fires on both incoming and outgoing messages — every message sent or received in your Notifyer console triggers this, including messages typed by hand in the WhatsApp Business app. Use it for conversation logging, CRM sync, or automations that must react when a teammate replies on their phone. Description in Make: “Get your sent and incoming messages data through a single webhook.” How to set up: Follow the same 5-step trigger setup guide above. In Step 1, select Incoming & Outgoing Messages from console (Notifyer System) instead. Key difference: This trigger also fires when your business sends a message. Use the incoming_message field to branch your logic:

incoming_message = true → a contact sent your business a message
incoming_message = false → your business sent a message to a contact (phone app, Notifyer inbox, or automation)

Output fields: Identical to the Incoming Messages from console trigger above, with these differences:

boolean

true when the contact sent a message, false when your business sent a message. Add a Router or Filter module after this trigger to branch logic based on direction

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

boolean

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

The scheduled_messages field is only available in the Incoming Messages from console trigger, not this one.

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, and updating contacts.

Send WhatsApp Message

Type: Action | Connection: Notifyer only

Description in Make: “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) and non-template messages (within an active 24-hour window). Labels and notes set here appear directly in your Notifyer console — making this the primary send module for Notifyer System users. API endpoint: https://api.insightssystem.com/api:pqxobaAo/send How to configure:

Add the module

Click + → search for WhatsAble or WhatsAble for WhatsApp Business → under Actions, select Send WhatsApp Message

Select your connection

Choose your existing connection or create a new one with your Notifyer API key

Choose your configuration

Select 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 or reach out proactively. Requires a Meta-approved template.

text

required

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

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 has variables ({{1}}, {{2}}…), a field appears for each. Map them to dynamic data from previous modules

text

If your template has a media header (image, video, document), enter the publicly accessible URL of that file

text

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

text

AI context about this contact (name, email, preferences, language). The AI reads this to personalize future replies and qualify leads more accurately

multiselect

Labels to apply to this conversation for internal tracking and routing. Labels appear in your Notifyer console

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

text

required

Phone number in international format — digits only (e.g. 14155550187)

dropdown

required

Choose the type of message to send:

Text Message

text

required

The text content to send

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 (JPEG, PNG, etc.)

text

Optional caption text below the image

Video Message

url

required

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

text

Optional caption text below the video

Document Message

url

required

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

text

Optional caption for the document

text

required

Filename to display (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 replies

Schedule a follow-up Message

Type: Action | Connection: Notifyer only

Description in Make: “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 message if the recipient responds before it sends. This is one of Notifyer’s most powerful automation features — use it to build no-reply follow-up sequences, re-engagement drips, and smart nurture workflows. How to configure:

Add the module

Click + → search for WhatsAble or WhatsAble for WhatsApp Business → under Actions, select Schedule a follow-up Message

Select your connection

Choose your Notifyer only connection

Choose your message type

Select from the Configuration dropdown — either a template message or a non-template message. The fields are identical to the Send WhatsApp Message action above (phone number, template/message type, variables, labels, note).

Set when to send it

Relative (Delay)
Specific Date & Time

Send the message after a delay from the time the scenario 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 cancel the scheduled message if the recipient replies within the specified timeframe — preventing follow-ups to contacts who are already engaged.

select

Condition	When the message is cancelled
Recipient did not reply after my last message	Cancelled if the contact replies at any point before scheduled send
Recipient never replied to any of my messages	Cancelled only if the contact has never replied to you at all
Recipient did not reply within 20 minutes	Cancelled if contact replies within 20 minutes
Recipient did not reply within 45 minutes	Cancelled if contact replies within 45 minutes
Recipient did not reply within 3 hours	Cancelled if contact replies within 3 hours
Recipient did not reply within 6 hours	Cancelled if contact replies within 6 hours
Recipient did not reply within 12 hours	Cancelled if contact replies within 12 hours
Recipient did not reply within 24 hours	Cancelled if contact replies within 24 hours
Recipient did not reply within 48 hours	Cancelled if contact replies within 48 hours
Recipient did not reply within 72 hours	Cancelled if contact replies within 72 hours

“Recipient did not reply after my last message” is the recommended default for most follow-up sequences — it ensures no follow-up is sent to contacts who are already in conversation with you.

Set a label condition (optional)

Restrict the scheduled message to only send if the contact has (or does not have) a specific label:

select

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

select

The label to evaluate against

Scheduled messages are visible in your Notifyer console under the contact’s conversation. You can view or cancel them there at any time.

Update a Contact

Type: Action | Connection: Notifyer only

Description in Make: “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 labels, or update the AI context note on their conversation. Use this to keep Notifyer contacts in sync with your CRM, form responses, or other external data. API endpoint: https://api.insightssystem.com/api:hFrjh8a1/make/recipient/details/update (PUT) How to configure:

Add the module

Click + → search for WhatsAble or WhatsAble for WhatsApp Business → under Actions, select Update a Contact

Select your connection

Choose your Notifyer only connection

Fill in the fields

text

required

The phone number of the contact to update, in international format — digits only (e.g. 14155550187). This is used to look up the contact in Notifyer

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 conversations. A well-structured note significantly improves AI response 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 for routing, filtering, and automation conditions

multiselect

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

Place Update a Contact at the very start of your scenario — before sending any message — to populate the AI Note from form or CRM data. This ensures the AI has full context before the first message is even sent.

Search

Get delivery status of a message

Type: Search | Connection: Notifyer only

Description in Make: “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 delivered. Use this to build fallback automation — if a message was not delivered (e.g. incorrect number), automatically trigger an alternative action such as sending a fallback email. API endpoint: https://api.insightssystem.com/api:5l-RgW1B/conversation/{{messageId}} (GET) How to configure:

Add the module

Click + → search for WhatsAble or WhatsAble for WhatsApp Business → under Searches, select Get delivery status of a message

Select your connection

Choose your Notifyer only connection

Enter the Message ID

text

required

The ID of the message to check. This is the ID returned in the output bundle of a previous Send WhatsApp Message or Schedule a follow-up Message action in the same scenario

Connect a Router module after this search to handle two paths: one for successfully delivered messages, and one for undelivered messages where you trigger a fallback (e.g. send a Gmail or Outlook email).

Building a complete scenario: 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 instant trigger that fires when someone fills in your lead capture form

Action: Update a Contact

Add Notifyer — 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 Notifyer — Send WhatsApp Message set to the template configuration. Select your approved welcome template and map the recipient’s phone number and any template variables from the form data

Action: Schedule a follow-up Message

Add Notifyer — Schedule a follow-up Message. Configure:

Message: a follow-up template (e.g. Hi {{1}}, just checking in...)
Schedule: 24 hours (Relative)
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 Run once to test with real data
Verify each module shows a green checkmark
Toggle the scenario Active switch to go live

Example use cases

AI chatbot lead qualification

Trigger on incoming messages, pass the 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 automatically cancel when the lead engages

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

Full conversation logging

Use Incoming & Outgoing Messages trigger to log every WhatsApp exchange to a Google Sheet, Airtable, or CRM

Best practices

Set the AI Note before sending

Always use Update a Contact before Send WhatsApp Message in new-lead scenarios. 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. “Recipient did not reply after my last message” is the safest choice — it ensures no follow-up annoys contacts who are already in an active conversation with you. This also protects your WhatsApp account reputation.

Use labels and notes on every send

The Send WhatsApp Message action lets you attach labels and a note alongside every message. Use labels to tag conversations (e.g. Hot Lead, Form Submission) and the note field to keep AI context current. Both appear immediately in your Notifyer console.

Use conversation_paragraph for AI prompts

When building AI chatbot scenarios, pass the conversation_paragraph field to your AI model. It is a pre-formatted, flat text version of the conversation — much simpler to include in a prompt than parsing the last_messages JSON array.

Use Incoming & Outgoing trigger for full logging

If you need to log every message exchange to a CRM or database, use Incoming & Outgoing Messages from console and filter by incoming_message to handle both directions with separate scenario branches.

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 the scenario is active

Instant triggers only fire when the scenario is toggled Active in Make. Also confirm the schedule is set to Immediately as data arrives

Verify the webhook is configured

Open the trigger module and confirm a webhook is selected in the Webhook dropdown and a Webhook URL is displayed. If the field is empty, follow the trigger setup guide to create one

Verify your connection

Open the connection settings and confirm your Notifyer API key is valid and the connection shows a green tick

Re-register the webhook

Try deactivating and reactivating the scenario — this re-registers the webhook with Notifyer. Check your Notifyer console to confirm messages are arriving there

Check Notifyer console

If messages appear in your Notifyer console but the trigger does not fire, contact support

Messages not sending?

Check the connection

Verify your Notifyer API key is valid and the correct connection is selected

Check phone number format

Phone number must be digits only, 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

Non-template messages can only be sent within 24 hours of the contact’s last incoming message. Outside this window you must use a 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 — ensure none are empty or mapped to empty values

Check the template preview

The template dropdown shows a live preview of the body text and example variable 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 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 time, the message was intentionally cancelled. Check the contact’s conversation in your Notifyer console

Check the scheduled time

Verify the delay value and unit are correct (minutes vs hours vs days)

Check scenario run history

Go to Make scenario history to confirm the Schedule a follow-up module executed without errors 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. If the contact doesn’t exist yet, the update creates the record

Check you're using the right connection

Update a Contact requires the Notifyer only connection — make sure you are not using a different connection type

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 Make

​Available modules at a glance

Triggers (Instant)

Actions

Search

​Prerequisites

Notifyer System Account

Make Account

​Setting up your Notifyer System account

​Connect Notifyer System to Make

​Module Reference

​Triggers

​Setting up a Notifyer trigger in Make

​Incoming Messages from console (Notifyer System)

​Incoming & Outgoing Messages from console (Notifyer System)

​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

​Schedule a follow-up Message

​Update a Contact

​Search

​Get delivery status of a message

​Building a complete scenario: 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

Full conversation logging

​Best practices

​Troubleshooting

​Need help?

Email support

Schedule a demo

Live chat

Notifyer System Integration with Make

Available modules at a glance

Prerequisites

Setting up your Notifyer System account

Connect Notifyer System to Make

Module Reference

Triggers

Setting up a Notifyer trigger in Make

Incoming Messages from console (Notifyer System)

Incoming & Outgoing Messages from console (Notifyer System)

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

Schedule a follow-up Message

Update a Contact

Search

Get delivery status of a message

Building a complete scenario: step-by-step example

Example use cases

Best practices

Troubleshooting

Need help?