Events: start a WhatsApp follow-up when something happens
Connect messages a person on WhatsApp when something happens in your product: a form is filled, someone signs up or logs in, a payment is left unpaid, a fee is due, a class or appointment is booked. You turn on the matching recipe in Connect (Connectors → Recipes), pick its follow-up, and then tell Connect each time it happens. There are four ways to tell it, and all are automatic (nobody at Nevorai sets anything up).
| Recipe | Event name | Follow-up it starts |
|---|---|---|
| Someone fills in a form | form_filled | Enquiry |
| Someone signs up or logs in | signup | Welcome |
| A payment isn't completed | payment_pending | an hour later, next morning, after 3 days |
| A payment is due | payment_due | 3 days before, on the day, 2 days after |
| A class, webinar or session is booked | class_booked | confirmation, a day before, an hour before, "we're live" |
| An appointment is booked | appointment_booked | confirmation, the day before |
1. From your website (the one line)
If your site has the one-line snippet, call this after the person has agreed to get WhatsApp messages:
window.NevoraiConnect?.event("payment_pending", { name, phone, consent: true, f: { amount: "999", item: "Gold plan" } });It works only from the address you connected, needs the person's tick (consent: true), and runs the recipe of YOUR business.
2. From your server (an API key)
Make a key under Connectors → Developers. Keep it in a server-side secret such as CONNECT_API_KEY, never in browser code.
curl -X POST https://connect.nevorai.com/api/v1/events \
-H "Authorization: Bearer $CONNECT_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "event": "payment_pending", "phone": "919876543210", "name": "Ravi",
"fields": { "amount": "999", "item": "Gold plan" }, "ref": "order_123" }'eventis required.phone(orto) is the person, with country code (a bare 10-digit number is taken as Indian).fieldscarries what the recipe's messages use (forpayment_pending:amount,item,pay_link; for bookings:event_at, India time like2026-10-12T19:00). The Recipes screen lists each recipe's fields, with copy-ready code in curl, Node, PHP and Python.refis your own id for this event. The samerefagain does nothing, so a retry is safe. Without arefthe same person is added once a day.
Answer (200): { "ok": true, "result": "added", "message": "…" }.
| HTTP | code | meaning |
|---|---|---|
| 400 | invalid_event | the event name is missing or malformed |
| 400 | (no phone) | no valid phone number in the event |
| 401 | unauthorized | the key is missing, wrong or revoked |
| 404 | event_not_found | that recipe isn't turned on yet (Connectors → Recipes) |
| 409 | the recipe is switched off | |
| 413 | too_big | more than 64 KB |
| 422 | a detail the recipe needs is missing (the message says which) | |
| 429 | rate_limited / limit | too many requests, or the recipe's daily cap (3,000) |
| 503 | our side failed: try again with the same ref |
3. From Zapier, Make, Pabbly or any no-code tool
Turn the recipe on, open Zapier · Make · Pabbly, and copy its private address. In your tool add a step "send a webhook (POST)" to that address with the fields phone, name and the recipe's details. Keep the address private: anyone who has it can add people.
4. Ask an AI builder
The Ask an AI tab gives a ready prompt for Lovable, Claude Code, Cursor or similar, with the private address and the fields. It never contains a key.
Stop it when they pay
A reminder must stop once the person has paid or booked:
curl -X POST https://connect.nevorai.com/api/v1/followups/stop \
-H "Authorization: Bearer $CONNECT_API_KEY" -H "Content-Type: application/json" \
-d '{ "to": "919876543210" }'Rules
- Message only people who agreed to get WhatsApp messages. Browser events need
consent: true. - Anyone who replies STOP gets nothing more, from every route.
- Follow-ups send approved templates from your own number, so Meta bills your WhatsApp account directly.
- Test first: Test with my number on each recipe card sends the whole follow-up to you with sample details.