Back to Catalog

Send automatic WhatsApp order confirmations from Shopify with Rapiwa API

SpaGreen CreativeSpaGreen Creative
765 views
2/3/2026
Official Page

Send Automatic WhatsApp Order Confirmations from Shopify with Rapiwa API

Who’s it for

This n8n workflow helps Shopify store owners and teams automatically confirm orders via WhatsApp. It checks if the customer's number is valid using Rapiwa API, sends a personalized message, and logs every attempt in Google Sheets—saving time and reducing manual work.

Whether you're a solo entrepreneur or managing a small team, this solution gives you a low-cost alternative to the official WhatsApp Business API, without losing control or personalization.

Features

  • Receives new order details via webhook upon order creation or update.
  • Iterates over incoming data in manageable batches for smoother processing.
  • Extracts and formats customer and order details from the Shopify webhook payload.
  • Strips non-numeric characters from WhatsApp numbers for consistent formatting.
  • Uses Rapiwa API to check if the WhatsApp number is valid and active.
  • Branches the workflow based on number validity — separates verified from unverified.
  • Sends a custom WhatsApp confirmation message to verified customers using Rapiwa.
  • Updates Google Sheet rows with status and validity

How it Works / What It Does

  • Triggered by a Shopify webhook or by reading rows from a Google Sheet.

  • Normalizes and cleans the order payload.

  • Extracts details like customer name, phone, items, shipping, and payment info.

  • Cleans phone numbers (removes special characters).

  • Verifies if the number is registered on WhatsApp via Rapiwa API.

  • If valid:

    • Sends a templated WhatsApp message.
    • Updates Google Sheet with validity = verified and status = sent.
  • If invalid:

    • Skips sending.
    • Updates sheet with validity = unverified and status = not sent.
  • Adds wait/delay between sends to prevent rate limits.

  • Keeps an audit trail in the connected Google Sheet.


How to Set Up

  1. Set up a Shopify webhook for new orders (or connect a Google Sheet).

  2. Create a Google Sheet with columns:

    • name, number, order id, item name, total price, validity, status
  3. Create and configure a Rapiwa Bearer token in n8n.

  4. Add Google Sheets OAuth2 credential in n8n.

  5. Import the workflow in n8n and configure these nodes:

    • Webhook or Sheet Trigger
    • Loop Over Items (SplitInBatches)
    • Normalize Payload (Code)
    • Clean WhatsApp Number (Code)
    • Rapiwa WhatsApp Check (HTTP Request)
    • Conditional Branch (If)
    • Send WhatsApp Message (HTTP Request)
    • Update Google Sheet (Google Sheets)
    • Wait Node (delay per send)

Requirements

  • Shopify store with order webhook enabled (or order list in Google Sheet)
  • A verified Rapiwa API token
  • A working n8n instance with HTTP and Google Sheets nodes enabled
  • A Google Sheet with required structure and valid OAuth credentials in n8n

How to Customize the Workflow

  • Modify the message template with your own brand tone or emojis.
  • Add country-code logic in the Clean Number node if needed.
  • Use a unique order id in your Google Sheet to prevent mismatches.
  • Increase or decrease delay in the Wait node (e.g., 5–10 seconds).
  • Use additional logic in Code nodes to handle discounts, promotions, or more line items.

Workflow Highlights

  • Triggered by Shopify webhook update.
  • Receiving new order data form Shopify using webhook
  • Cleans and extracts order data from raw payload.
  • Normalizing and validating the customer’s WhatsApp number using the Rapiwa API
  • Verifies WhatsApp number using Rapiwa's verify-whatsapp endpoint.
  • Sends order confirmation via Rapiwa's send-message endpoint.
  • Logs every result into Google Sheets (verified/unverified + sent/not sent).

Setup in n8n

1. Check WhatsApp Registration

  • Use an HTTP Request node:

    • URL: https://app.rapiwa.com/api/verify-whatsapp
    • Method: POST
    • Auth: httpBearerAuth using your Rapiwa token
    • Body: { "number": "cleaned_number" }

2. Branch Based on Validity

  • Use an If node:

    • Condition: {{ $json.data.exists }} == true (or "true" if string)

3. Send Message via Rapiwa

  • Endpoint: https://app.rapiwa.com/api/send-message
  • Method: POST
  • Body:
Hi *{{ $json.customer_full_name }}*,
Thank you for shopping with *SpaGreen Creative*! We're happy to confirm that your order has been successfully placed.
🧾 Order Details
• Product: {{ $json.line_item.title }}
• SKU: {{ $json.line_item.sku }}
• Quantity: {{ $json.line_item.quantity }}
• Vendor: {{ $json.line_item.vendor }}
• Order ID: {{ $json.name }}
• Product ID: {{ $json.line_item.product_id }}
📦 Shipping Information
{{ $json.shipping_address.address1 }} {{ $json.shipping_address.address2 }}
{{ $json.shipping_address.city }}, {{ $json.shipping_address.country }} - {{ $json.shipping_address.zip }}
💳 Payment Summary
• Subtotal: {{ $json.subtotal_price }} BDT
• Tax (VAT): {{ $json.total_tax_amount }} BDT
• Shipping: {{ $json.total_shipping_amount }} BDT
• Discount: {{ $json.total_discount_amount }} BDT
• Total Paid: {{ $json.total_price }} BDT
Order Date: {{ $json.created_date }}
Warm wishes,
*Team SpaGreen Creative*

Sample Google Sheet Structure

  • A Google Sheet formatted like this ➤ Sample

| name | number | order id | item name | total price | validity | status | | ----------- | ------------- | ------------- | ------------------------------ | ----------- | -------- | ------ | | Abdul Mannan | 8801322827799| 8986469695806 | Iphone 10 | 1150 | verified | sent | | Abdul Mannan | 8801322827799| 8986469695806 | S25 UltraXXXXeen Android Phone | 23000 | verified | sent |


Tips

  • Always ensure phone numbers have a country code (e.g., 880 for BD).
  • Clean numbers with regex: replace(/\D/g, '')
  • Adjust Rapiwa API response parsing depending on actual structure (true vs "true").
  • Use row_number for sheet updates, or unique order id for better targeting.
  • Use the Wait node to add 3–10 seconds between sends.

Important Notes

  • Avoid reordering sheet rows—updates rely on consistent row_number.
  • shopify-app-auth is the credential name used in the export—make sure it's your Rapiwa token.
  • Use a test sheet before going live.
  • Rapiwa has request limits—avoid rapid sending.
  • Add media/image logic later using message_type: media.

Future Enhancements (Ideas)

  • Add Telegram/Slack alert once the batch finishes.
  • Include media (e.g., product image, invoice) in the message.
  • Detect and resend failed messages.
  • Integrate with Shopify’s GraphQL API for additional data.
  • Auto-mark fulfillment status based on WhatsApp confirmation.

Support & Community


Send Automatic WhatsApp Order Confirmations from Shopify with Rapiwa API

This n8n workflow automates the process of sending WhatsApp order confirmation messages to customers from Shopify, leveraging the Rapiwa API for messaging. It listens for new Shopify orders, retrieves customer and order details, and then sends a personalized WhatsApp message.

What it does

  1. Receives Shopify Orders: Listens for incoming webhook events from Shopify, triggered by new order creations.
  2. Extracts Order Data: Parses the incoming Shopify webhook data to extract relevant order and customer information, such as the customer's phone number, order ID, and total amount.
  3. Formats Phone Number: Uses a Code node to format the customer's phone number into a standardized international format suitable for WhatsApp.
  4. Checks for Valid Phone Number: An If node checks if a valid phone number was extracted and formatted.
  5. Sends WhatsApp Message (Rapiwa API): If a valid phone number exists, an HTTP Request node sends a POST request to the Rapiwa API to deliver a personalized WhatsApp message containing the order confirmation details.
  6. Logs to Google Sheets (Optional): If the phone number is invalid or missing, the order details are logged into a Google Sheet for review or manual follow-up.
  7. Introduces Delay (Optional): A Wait node can be configured to introduce a delay before sending the WhatsApp message, if desired.
  8. Handles Multiple Items (Optional): A "Loop Over Items" node (Split in Batches) is included, suggesting the workflow might be designed to handle multiple items within an order or multiple orders in a batch, though its current connection is not fully defined in the provided JSON.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • Shopify Account: A Shopify store configured to send webhooks for new orders.
  • Rapiwa API Account: An account with Rapiwa API for sending WhatsApp messages, including an API key and any necessary endpoint URLs.
  • Google Sheets Account: (Optional, for logging) A Google Sheets account and a configured spreadsheet to log orders with invalid phone numbers.
  • Google Sheets Credential: An n8n credential for Google Sheets (OAuth2 recommended).
  • HTTP Request Credential: If the Rapiwa API requires authentication (e.g., API Key in headers), an n8n HTTP Request credential might be needed.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure the Webhook Trigger:
    • Set the "Webhook" node to "Catch Hook".
    • Copy the generated webhook URL.
    • In your Shopify store settings, create a new webhook that triggers on "Order creation" and points to the copied n8n webhook URL.
  3. Configure the Code Node:
    • Review the "Code" node to ensure the phone number formatting logic (item.json.phone) matches the expected input from Shopify and the desired output for Rapiwa.
  4. Configure the HTTP Request Node:
    • Update the "HTTP Request" node with your Rapiwa API endpoint URL for sending WhatsApp messages.
    • Configure the request body to include the customer's phone number and the personalized message using expressions to pull data from previous nodes (e.g., {{$json.formattedPhoneNumber}}, {{$json.order_id}}, {{$json.total_price}}).
    • Add any required headers (e.g., Authorization with your Rapiwa API key).
  5. Configure the Google Sheets Node (Optional):
    • If you plan to use the Google Sheets logging, configure the "Google Sheets" node with your Google Sheets credential.
    • Specify the Spreadsheet ID and Sheet Name where you want to log the data.
    • Map the data fields to be written to the sheet (e.g., order ID, customer name, original phone number, reason for failure).
  6. Configure the If Node:
    • Ensure the "If" node correctly evaluates the presence and validity of the formatted phone number (e.g., {{$json.formattedPhoneNumber}} is not empty or null).
  7. Activate the Workflow: Once all nodes are configured, activate the workflow in n8n.

Now, whenever a new order is created in your Shopify store, n8n will automatically process it and send a WhatsApp confirmation message to the customer (if a valid phone number is available) or log the details for review.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942