How to connect
Add an MCP Client module to the scenario — or an MCP tool from an AI Agent’s configuration — create a connection and set the server URL to https://nilyo.com/mcp with OAuth authentication. A browser window opens to authorize, the same Nilyo sign-in ChatGPT and Claude use, with no Make-specific account to create.
Which WhatsApp you actually need
A brand sending order confirmations at scale wants the Business Cloud API and its templates. A team answering clients, suppliers and colleagues wants its own number. The second is what most Make scenarios are really trying to do, and it is where templates and reply windows only get in the way.
Resolve the contact by name
Scenarios carry names from a CRM, not phone identifiers. A resolution module turns a name into the exact conversation, ranked by most recent exchange, and returns the candidates when several match rather than picking one. That refusal is what keeps a scenario from messaging the wrong client.
Twenty new conversations a day
Starting a brand new chat is capped at twenty per day per account and spaced fifteen seconds apart, enforced server-side. Replies inside existing conversations are unrestricted. A scenario that iterates over a list of strangers will stop on an explicit error — which is the intended outcome, not a bug.
A realistic scenario
An invoice goes overdue; the scenario finds the existing WhatsApp conversation with that client, checks the last message so it does not repeat a reminder sent yesterday, and sends a short note. If no conversation exists, it routes to email instead of cold-messaging a number.
Watch for inbound messages
Instead of listing chats on a schedule, a realtime destination hands the scenario each new WhatsApp message as it arrives, with the chat and message identifiers needed to fetch the thread. The scenario then reads the conversation before answering, which is what stops it from replying to a message that was already handled on your phone.
“When an invoice is overdue, check the last message before sending a reminder.”
“Route to email when the client has no existing WhatsApp conversation.”
Common questions
Do I need a WhatsApp Business account?
No. The number you already use is paired by QR code; templates and the Business Cloud API belong to the brand route.
Can a scenario read attachments?
Yes, they come back as files, so a voice note or a PDF can feed a transcription or parsing module.
What stops a scenario from spamming?
New conversations are capped at twenty a day and spaced fifteen seconds apart, server-side, with an explicit error at the ceiling.
How WhatsApp works with Nilyo
Connection. Scan a QR code shown in the conversation (WhatsApp › Linked devices), or type a pairing code on your phone. The line stays linked like any other device.
What your agent can do. Contacts and chats, message history, text, media and native voice notes, reactions, groups, checking whether a number is on WhatsApp.
Pacing and safety. 20 new conversations per day with 15 seconds between them; existing chats are not limited beyond serialization.
- “Send a WhatsApp to Julien” resolves the person among your recent chats and contacts; two matches mean the agent asks.
- Disconnecting from the phone marks the account for reconnection; the same account is re-linked with a new QR, never duplicated.
All WhatsApp guides
Related guides
Give Nilyo to your agent.
Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.