How to Send Automated WhatsApp Messages

Sending automated WhatsApp messages means you stop typing the same text one recipient at a time and instead bind sending to a trigger — a panel action, a clock, or an API call. This article explains how automation differs from a plain bulk blast, which triggers drive it, the path a message follows once it enters the system, the anti-ban regime that keeps your number alive, and real scenarios like order and appointment notifications. Note up front: this is not the official Business API. It is an open-source, self-hosted whatsapp-web.js system that pairs your phone by QR code.

1. Automated vs. bulk: what is the difference?

The two terms get mixed up but they are not the same. A bulk message is one content sent to a list once — a campaign announcement to 800 people. An automated message binds sending to an event: an order confirmation when a purchase completes, a reminder the day before an appointment, a receipt when a payment lands. Bulk sends are usually one-off; automation is continuous and often personalized.

In practice the two overlap. In this system both land in the same queue and pass through the same rate discipline. For the bulk side, see WhatsApp bulk messaging software; here the focus is the triggers and flow behind automation.

2. The three triggers of automated sending

For a message to count as "automated", something has to start it. The system offers three ways:

2.1 Panel-driven automation

The simplest path. You enter the recipient list and text, hit send, and the worker does the rest. Compared with typing to 500 people by hand, this is already automation — you drop it once and the system runs for hours at a safe pace.

2.2 Scheduled automation

You plan a message for a future moment such as "tomorrow at 10:00". The queue holds it as a delayed job and releases it when the time arrives. Watch out: the time you set is the start time. Because of the anti-ban window and wait rules, the message leaves in sequence from that time, not at that exact minute. See scheduling WhatsApp messages for the details.

2.3 API-triggered automation

The most powerful path. Your own software — an e-commerce backend, an appointment system, a CRM or a web form — hits the server directly when an event fires, so a message goes out with no human in the loop. We cover this in depth in HTTP API integration.

3. What happens after a message enters the system?

The reason automated sending stays safe is that the sending job is separated from the panel. Whatever trigger you use, the message always flows the same way:

Here is why the split matters: the rate limit lives in exactly one place — the worker. Even 100 requests per second to the panel or API cannot push WhatsApp traffic past human speed. The worker runs at concurrency 1, so it sends one message at a time and waits between each. The server never sends directly, which rules out "accidental fast blasting" at the architectural level.

4. The anti-ban regime that makes automation safe

The biggest danger of automated sending is speed: tell a machine to "send" and it can fire hundreds of messages in seconds, getting your number flagged as spam instantly. To prevent this, the rules are hard-coded and not exposed as user settings:

5. Real automation scenarios

5.1 E-commerce: order and shipping notifications

Your order system hits the API on a "payment received" event and the customer gets an order confirmation over WhatsApp. When the courier generates a tracking number, a second automated message goes out. These are not marketing — they are service notifications, since the customer already transacted with you. For the full scenario and templates, see order and shipping notifications.

5.2 Appointment reminders

For a clinic, salon or consultant, a no-show is lost revenue. A scheduled reminder 24 hours and 2 hours before the appointment noticeably lowers no-show rates. You set this up with the scheduling trigger; see appointment reminders for details.

5.3 Dues, receipts and recurring notices

Recurring notices like membership dues, course fees or subscription renewals get wired to a monthly schedule, so you no longer prepare a list by hand every month.

6. Setup summary: automation in three steps

1. Run supabase/migrations/001_init.sql in the Supabase SQL Editor.
2. Fill in .env; generate REDIS_PASSWORD and WA_CONTROL_SECRET with openssl rand -hex 32. That second secret authenticates your API trigger.
3. Run docker compose up -d --build, scan the QR from the panel's Connection page with your phone, and launch your first automated send.

Once installed, the panel gives you both manual sending and a scheduling UI out of the box; for API triggering, your software just POSTs to the server's send endpoint with the secret.

Frequently asked questions