HumationHuman + Automation
Back to Catalog

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

RapiwaRapiwa
183 views
2/3/2026
excelemailautomationattachmentsimap
Official Page

Who Is This For?

This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking.

What This Workflow Does

  • Retrieves all paying customers from your WooCommerce store
  • Identifies each customer's most purchased product
  • Finds the latest product in the same category as their most purchased item
  • Cleans and verifies customer phone numbers for WhatsApp compatibility
  • Sends personalized WhatsApp messages with product recommendations
  • Logs all activities to Google Sheets for tracking and analysis
  • Handles both verified and unverified numbers appropriately

Key Features

  • Customer Segmentation: Automatically identifies paying customers from your WooCommerce store
  • Product Analysis: Determines each customer's most purchased product
  • Smart Recommendations: Finds the latest products in the same category as customer favorites
  • WhatsApp Integration: Uses Rapiwa API for message delivery
  • Phone Number Validation: Verifies WhatsApp numbers before sending messages
  • Dual Logging System: Tracks both successful and failed message attempts in Google Sheets
  • Rate Limiting: Uses batching and wait nodes to prevent API overload
  • Personalized Messaging: Includes customer name and product details in messages

Requirements

  • WooCommerce store with API access
  • Rapiwa account with API access for WhatsApp verification and messaging
  • Google account with Sheets access
  • Customer phone numbers in WooCommerce (stored in billing.phone field)

How to Use — Step-by-Step Setup

1. Credentials Setup

  • WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)")
  • Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token
  • Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access

2. Configure Google Sheets

  • Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section

3. Verify Code Nodes

  • Code (get paying_customer): Filters customers to include only those who have made purchases
  • Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers

4. Configure HTTP Request Nodes

  • Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders
  • Get specific product data: Verify the WooCommerce API endpoint for product details
  • Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category
  • Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation
  • Rapiwa Sender: Verify the Rapiwa endpoint for sending messages

Google Sheet Required Columns

You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly):

| name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://your_shop_domain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://your_shop_domain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://your_shop_domain/p-img-nike | verified | sent |

Important Notes

  • Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format.
  • API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly.
  • Data Privacy: Ensure compliance with data protection regulations when sending marketing messages.
  • Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls.
  • Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification.
  • Testing: Always test with a small batch before running the workflow on your entire customer list.

Useful Links

Support & Help

Send WooCommerce Cross-Sell Offers to Customers via WhatsApp using Rapiwa API

This n8n workflow automates the process of sending personalized cross-sell offers to customers via WhatsApp, leveraging WooCommerce order data and a custom WhatsApp API (Rapiwa API). It helps businesses increase sales by proactively engaging customers with relevant product suggestions.

What it does

This workflow performs the following key steps:

  1. Triggers on a Schedule: The workflow starts at a predefined interval (e.g., daily, weekly) to check for new orders.
  2. Fetches WooCommerce Orders: It retrieves a list of recent orders from your WooCommerce store.
  3. Loops Through Orders: For each order, it processes the order details individually.
  4. Checks for Cross-Sell Eligibility: It uses a custom JavaScript code to determine if the order qualifies for a cross-sell offer (e.g., based on products purchased, order value, or other custom logic).
  5. Retrieves Cross-Sell Products: If an order is eligible, it fetches recommended cross-sell products from a Google Sheet.
  6. Constructs WhatsApp Message: It dynamically creates a personalized WhatsApp message containing the cross-sell offers.
  7. Sends WhatsApp Message: It sends the crafted message to the customer's WhatsApp number using a custom HTTP Request node, presumably configured for the Rapiwa API.
  8. Waits (Optional): Includes a wait step, which could be used for rate limiting or to introduce a delay between messages.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • WooCommerce Account: Access to your WooCommerce store with API credentials configured in n8n.
  • Google Sheets Account: A Google Sheet containing your cross-sell product recommendations, configured with n8n credentials.
  • Rapiwa API (or similar WhatsApp API): An account and API key for a WhatsApp messaging service like Rapiwa API. The HTTP Request node will need to be configured with the appropriate endpoint and authentication.
  • Basic JavaScript Knowledge: To customize the cross-sell eligibility logic within the "Code" node.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click on "Workflows" in the left sidebar.
    • Click "New" and then "Import from JSON".
    • Paste the JSON code and click "Import".
  2. Configure Credentials:
    • WooCommerce Node: Click on the "WooCommerce" node and select or create your WooCommerce API credentials.
    • Google Sheets Node: Click on the "Google Sheets" node and select or create your Google Sheets API credentials. Ensure the spreadsheet ID and sheet name are correctly configured to point to your cross-sell product data.
    • HTTP Request Node: Click on the "HTTP Request" node. Configure it with your Rapiwa API (or chosen WhatsApp API) endpoint, method (likely POST), headers (including API key/token), and body to send the WhatsApp message.
  3. Customize Workflow Logic:
    • Schedule Trigger: Adjust the "Schedule Trigger" node to define how often you want the workflow to run (e.g., every day, every hour).
    • Code Node: Open the "Code" node. This is where you'll define your specific logic for determining which orders are eligible for cross-sell offers and how the cross-sell products are selected.
    • Google Sheets Node: Ensure the "Google Sheets" node is configured to read the correct data from your spreadsheet that contains product IDs, names, or other details relevant for cross-selling.
    • HTTP Request Node: Review the message body in the "HTTP Request" node to ensure the WhatsApp message format is as desired and includes all necessary dynamic data (customer name, product links, etc.).
  4. Activate the Workflow: Once all configurations are complete, save the workflow and activate it by toggling the "Active" switch in the top right corner.

The workflow will now automatically run on its schedule, fetch WooCommerce orders, identify cross-sell opportunities, and send WhatsApp messages to your customers.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31

Automate Gmail responses with GPT and human-in-the-loop verification

Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com

Nick CanfieldBy Nick Canfield
88