Back to Catalog

Automatically send WhatsApp discount codes to Shopify customers using Rapiwa

RapiwaRapiwa
56 views
2/3/2026
Official Page

Automatically Send WhatsApp Discount Codes to Shopify Customers Using Rapiwa

Who is this for?

This n8n workflow automatically sends WhatsApp promotional messages to top customers whenever a new discount code is created in Shopify. It’s perfect for store owners, marketers, sales teams, or support agents who want to engage their best customers effortlessly. The workflow fetches customer data, filters high-spending customers, verifies their WhatsApp numbers using the Rapiwa API, sends discount messages to verified contacts, and logs all activity in Google Sheets. Designed for non-technical users who don’t use the official WhatsApp Business API, this automation simplifies customer outreach and tracking without any manual work.

What this Workflow Does

This n8n workflow connects with a Google Sheet that contains a list of contacts. It reads rows marked for processing, cleans the phone numbers, checks their validity using Rapiwa's WhatsApp validation API, sends WhatsApp messages to valid numbers, and updates the status of each row accordingly.

Key Features

  • Runs Every 5 Minutes: Automatically triggers the workflow
  • Google Sheets Integration: Reads and writes data from a specific sheet
  • Phone Number Validation: Confirms if a WhatsApp number is active via Rapiwa API
  • Message Sending: Sends a message using Rapiwa's /send-message endpoint
  • Status Update: Sheet is updated with success or failure status
  • Safe API Usage: Delays added between requests to prevent rate limits
  • Batch Limit: Processes max 60 rows per cycle
  • Conditional Checks: Skips rows without a "check" value

Requirements

  • A Google Sheet with necessary columns
  • Rapiwa account with active subscription (you can free 200 message)
  • Your WhatsApp number connected to Rapiwa
  • Valid Bearer Token
  • n8n Instance (self-hosted or cloud)
    • Google Sheets node configured
    • HTTP Request node access

How to Use

Step-by-Step Setup

  1. Webhook

    • Receives Shopify Webhook (discount creation) via HTTP POST request.
      This is triggered when a discount is created in your Shopify store.
  2. Configure Google Sheets in n8n

    • Use the Google Sheets node with OAuth2 access
  3. Get Rapiwa API Token

    • Create an account on Rapiwa
    • Connect your WhatsApp number
    • Copy your Bearer Token from the Rapiwa dashboard
  4. Set Up HTTP Request Nodes

    • Validate number via: https://app.rapiwa.com/api/verify-whatsapp
    • Send message via: https://app.rapiwa.com/api/send-message
    • Add your bearer token to the headers

Google Sheet Column Structure

  • A Google Sheet formatted like this ➤ Sample

| discount_code | created_at | shop_domain | name | number | verify | status | | -------------------------------------------- | ------- | ------------------------- | ----------------------- | -------------- | ------------- | ---------- | -------- | | V8ZGVRDFP5TB | 2025-09-25T05:26:40-04:00 | your_shop_domain | Abdul Mannan | 8801322827798| unverified | not sent | | V8ZGVRDFP5TB | 2025-09-25T05:26:40-04:00 | your_shop_domain | Abdul Mannan | 8801322827799| verified | sent |


Support & Help

n8n Workflow: Automate Discount Code Distribution via WhatsApp

This n8n workflow simplifies and automates the process of distributing discount codes to customers. It acts as an API endpoint, receiving customer data and then simulating the distribution of discount codes, potentially via a service like Rapiwa for WhatsApp.

What it does

This workflow performs the following key steps:

  1. Receives a Webhook Trigger: The workflow starts by listening for an incoming HTTP POST request (webhook). This request is expected to contain customer data, likely including details needed for discount code distribution.
  2. Processes Data (Placeholder): A "Code" node is included, which typically allows for custom JavaScript logic. In its current state (based solely on the JSON), it acts as a placeholder for processing or transforming the incoming data.
  3. Loops Over Items (Placeholder): A "Loop Over Items (Split in Batches)" node is present, suggesting that the workflow is designed to handle multiple items (e.g., multiple customers) received in a single webhook. This node would iterate through each item.
  4. Conditional Logic (Placeholder): An "If" node is included, indicating that there might be conditional logic to determine whether a discount code should be sent or how it should be handled based on certain criteria.
  5. Simulates Discount Code Generation/Lookup (Placeholder): A "Google Sheets" node is present. While its exact operation is not defined in the JSON, it commonly interacts with Google Sheets to read, write, or update data. This could be used to look up existing discount codes, record sent codes, or even generate new ones.
  6. Simulates WhatsApp Message Sending (Placeholder): An "HTTP Request" node is included. This node is typically used to make API calls to external services. In the context of the directory name "rapiwa", this node would likely be configured to send WhatsApp messages via the Rapiwa API, including the discount code.
  7. Introduces a Delay (Placeholder): A "Wait" node is present, which pauses the workflow for a specified duration. This can be useful for rate limiting when interacting with external APIs or to simulate a more natural distribution pace.
  8. Provides a Sticky Note: A "Sticky Note" is included, which is used for documentation within the workflow itself, likely to provide context or instructions for specific parts of the flow.

Prerequisites/Requirements

To fully utilize this workflow, you would typically need:

  • n8n Instance: A running instance of n8n to import and execute the workflow.
  • Webhook Source: An external system (e.g., Shopify, CRM, custom application) configured to send data to the n8n Webhook URL.
  • Google Account: For the "Google Sheets" node, a Google account with access to the relevant spreadsheet.
  • Rapiwa Account (or similar WhatsApp API): For sending WhatsApp messages, an account with Rapiwa or another WhatsApp Business API provider, along with the necessary API credentials.
  • API Key/Credentials: Any required API keys or authentication tokens for Rapiwa and other external services.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure the Webhook:
    • Activate the "Webhook" node.
    • Copy the generated webhook URL. This URL will be used by your external system to trigger the workflow.
  3. Configure Credentials:
    • Google Sheets: Set up your Google Sheets credentials in n8n. Configure the "Google Sheets" node to interact with your desired spreadsheet (e.g., to read customer data, store discount codes, or log activity).
    • HTTP Request (Rapiwa): Configure the "HTTP Request" node with your Rapiwa API endpoint, authentication details (e.g., API key in headers or body), and the message payload for sending WhatsApp messages. You'll need to dynamically insert customer phone numbers and discount codes into the request body.
  4. Customize Code and If Nodes:
    • Code: Modify the "Code" node to perform any necessary data transformation, validation, or discount code generation logic.
    • If: Adjust the conditions in the "If" node to control when and how discount codes are distributed (e.g., only for new customers, specific order values, etc.).
  5. Adjust Loop and Wait Nodes:
    • Loop Over Items: Configure the batch size if you expect to process many items simultaneously to prevent hitting API rate limits.
    • Wait: Adjust the delay duration in the "Wait" node as needed to comply with API rate limits or desired timing.
  6. Activate the Workflow: Once configured, activate the workflow in n8n.
  7. Trigger the Workflow: Send a POST request to the webhook URL from your external system with the customer data.

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

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

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 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 Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section 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 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://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/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 Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

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