Hi @Ali4 , welcome to the n8n community! I don’t have experience with this, but I looked into the n8n docs and here are some points covered in the material:
N8N DOCS
-
Use templates for business‑initiated messages
For messages you initiate (not replies within 24h), you must use approved templates; otherwise delivery will fail or be blocked. [Standard bot guide; 24h window note]
Also, Meta has spam‑prevention and template disabling if users complain, so always ensure consent. [Template usage] -
Respect WhatsApp’s 24‑hour window and template rules
- Free‑form replies are only allowed within 24h after the user messages you. [24h window]
- Outside that window, you must use templates; otherwise messages won’t be delivered. [24h/template requirement]
-
Add delays in n8n to avoid rate‑limit spikes
n8n suggests handling rate limits by:- Looping over items and inserting a Wait node to pause between each message. [Wait usage; Loop + Wait pattern]
- Community examples explicitly recommend a Wait node inside a loop to add 20–60s between items when sending many messages or calling APIs. [Loop delay example; Google Sheet → WhatsApp loop; General rate‑limit advice]
A typical pattern for your case (300+ messages/month) is:
- Read contacts (e.g. from Google Sheets or your data source).
- Use Loop Over Items.
- Inside the loop:
Wait(fixed duration like 20–60s) → WhatsApp Business Cloud node (Send Template).
-
Check delivery and errors, not just HTTP 200
Even if n8n shows HTTP 200, WhatsApp can still reject messages (e.g. permission issues, template problems). You should:- Inspect the response body for errors.
- Use WhatsApp webhook status callbacks to see why messages weren’t delivered. [Status/webhook advice]
-
Account safety / bans
The sources mention that Meta can restrict or disable templates/accounts if messages are seen as spam or violate rules, and that you must have prior consent. [Template consent note; Spam / safety FAQ]
There is also a community case where a WhatsApp Business account was restricted, but the answer points to external guidance (Sinch) rather than n8n‑specific limits. [Restriction thread]
Putting it together for your scenario (300+ / month):
- Use approved templates for all business‑initiated sends.
- Ensure explicit consent and clear expectations (they know they’ll receive PDFs via WhatsApp).
- Implement a Loop Over Items + Wait pattern and add a per‑message delay (e.g. 20–60 seconds) using the Wait node; this is the recommended n8n pattern for staying under rate limits, though the exact delay value isn’t specified in the docs. [Rate‑limit handling; Loop delay example]
- Monitor webhook delivery statuses and adjust volume/delay if you see errors or throttling. [Status/webhook advice]
Because the knowledge sources don’t include concrete WhatsApp numeric thresholds (messages per second/day), you’ll need to combine this n8n pattern with Meta’s official WhatsApp Business rate‑limit and quality documentation.