Get Started
Back to Templates

Auto-Send WooCommerce Invoices via WhatsApp with Rapiwa API

Created by

Created by: Rapiwa || rapiwa

Rapiwa

Last update

Last update 19 hours ago

Categories

Share

Who is this for?

This workflow listens for new or updated WooCommerce orders, cleans and structures the order data, processes orders in batches, and standardizes WhatsApp phone numbers. It verifies phone numbers via the Rapiwa API, sends invoice links or messages to verified numbers, and logs results into separate Google Sheets tabs for verified and unverified numbers. Throttling and looping are managed using batch processing and wait delays.

What this Workflow Does

  • Receives order events (e.g., order.updated) from WooCommerce or a similar trigger.
  • Extracts customer, billing/shipping address, product list, and invoice link from the order payload.
  • Processes orders/items in batches for controlled throughput.
  • Cleans and normalizes phone numbers by removing non-digit characters.
  • Verifies whether a phone number is registered on WhatsApp using the Rapiwa API.
  • If verified, sends a personalized message or invoice link via Rapiwa's send-message endpoint.
  • If not verified, logs the customer as unverified in Google Sheets.
  • Logs every send attempt (status and validity) into Google Sheets.
  • Uses Wait nodes and batching to avoid API rate limits.

Key Features

  • Trigger-based automation (WooCommerce trigger; adaptable to Shopify webhook).
  • Batch processing using SplitInBatches for stable throughput.
  • Phone number cleaning using JavaScript (waNoStr.replace(/\D/g, "")).
  • Pre-send WhatsApp verification via Rapiwa to reduce failed sends.
  • Conditional branching (IF node) between verified and unverified flows.
  • Personalized message templates that include product and customer fields.
  • Logging to Google Sheets with separate flows for verified/sent and unverified/not sent.
  • Wait node for throttling and looping control.

Requirements

  • Running n8n instance with nodes: HTTP Request, Code, SplitInBatches, IF, Google Sheets, Wait, and a WooCommerce trigger (or equivalent).
  • Rapiwa account and Bearer token for verify/send endpoints.
  • Google account and Google Sheets access with OAuth2 credentials.
  • WooCommerce store access credentials (or Shopify credentials if adapting).
  • Incoming order payloads containing billing and line_items fields.

Google Sheet format (example rows)

A Google Sheet formatted like this ➤ Sample

Customer Name Phone Number Email Address Address Product Title Product ID Size Quantity Total Price Product Image Invoice Link Status Validity
Abdul Mannan 8801322827799 [email protected] mirpur T-Shirt - XL 110 XL 1 BDT 499.00 https://your_shop_domain/Product/gg.img https://your_shop_domain/INV/DAS sent verified
Abdul Mannan 8801322827799 [email protected] mirpur T-Shirt - XL 110 XL 1 BDT 499.00 https://your_shop_domain/Product/gg.img https://your_shop_domain/INV/DAS not sent unverified

Important Notes

  • The Code nodes assume billing and line_items exist in the incoming payload; update mappings if your source differs.
  • The message template references products[0]; if orders contain multiple items, update logic to summarize or iterate products.
  • Start testing with small batches to avoid accidental mass messaging and to respect Rapiwa rate limits.

Useful Links

Support & Help