Skip to main content
automate-notifyer builds on setup-notifyer. Always run setup-notifyer/scripts/doctor.js before sending templates, creating broadcasts, or configuring webhooks.

What this skill covers

  • Templates: create/list/get/delete; monitor Meta approval lifecycle
  • AI bots: create/update/delete bots; set default bot
  • Broadcasts: create/schedule campaigns using template + recipient CSV
  • Analytics & logs: read rates, delivery rates, message logs
  • Webhooks: create/update/delete dev and IO webhooks; optional HMAC signatures; --incoming and --outgoing so events include messages typed in the WhatsApp Business app

Prerequisites

Some features require a Pro or Agency plan (and an OpenAI key configured in Notifyer settings for bots). If you’re not sure, check with setup-notifyer/scripts/get-user-plan.js.

Setup

Templates

List templates:
Create a template (text with variables):
list-templates.js auto-syncs PENDING template statuses from Meta on each call — you can re-run it to observe approval changes.
Delete a template:

AI bots

Broadcasts

Create and schedule a broadcast (3-step flow):
Phone numbers in the CSV must be integers without +. The schedule format is strictly DD/MM/YYYY HH:mm and is timezone-sensitive.

Analytics & logs

Webhooks

List webhooks:
Create a dev webhook (Make/Zapier/n8n style) that receives incoming and outgoing messages, including replies typed in the WhatsApp Business app:
--outgoing is required if an automation must react to messages sent from the phone app, the Notifyer chat inbox, or other integrations. Payload fields: incoming_message, send_by, was_message_by_human. Full reference: Message webhooks.

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: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_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:
Create an IO webhook (bidirectional pipeline style):
Update/delete:
Dev webhook id is an integer. IO webhook id is a text UUID — treat it as a string.

Next