HumationHuman + Automation
Back to Catalog

Send bulk WhatsApp messages from Google Sheets using Rapiwa API

SpaGreen CreativeSpaGreen Creative
1106 views
2/3/2026
ExportPostgreSQLFilesystemDatabaseCSV
Official Page

Bulk WhatsApp Campaign Automation with Rapiwa API (Unofficial Integration)

Who’s it for

This n8n workflow lets you send bulk WhatsApp messages using your own number through Rapiwa API, avoiding the high cost and limitations of the official WhatsApp API. It integrates seamlessly with Google Sheets, where you can manage your contacts and messages with ease. Ideal for easy-to-maintain bulk messaging solution using their own personal or business WhatsApp number. This solution is perfect for small businesses, marketers, or teams looking for a cost-effective way to manage WhatsApp communication at scale.

How it Works / What It Does

  • Reads data from a Google Sheet where the Status column is marked as "pending".
  • Cleans each phone number (removes special characters, spaces, etc.).
  • Verifies if the number is a valid WhatsApp user using the Rapiwa API.
  • If valid:
    • Sends the message via Rapiwa.
    • Updates Status = sent and Verification = verified.
  • If invalid:
    • Skips message sending.
    • Updates Status = not sent and Verification = unverified.
  • Waits for a few seconds (rate-limiting).
  • Loops through the next item.
  • The entire process is triggered automatically every 5 minutes.

How to Set Up

  1. Duplicate the Sample Sheet: Use this format.
  2. Fill Contacts: Add columns like WhatsApp No, Name, Message, Image URL, and set Status = pending.
  3. Connect Google Sheets: Authenticate and link Google Sheets node inside n8n.
  4. Subscribe to Rapiwa: Go to Rapiwa.com and get your API key.
  5. Paste API Key: Use the HTTP Bearer token credential in n8n.
  6. Activate the Workflow: Let n8n take care of the automation.

Requirements

  • Google Sheets API credentials
  • Configured Google Sheet (template linked above)
  • WhatsApp (Personal or Business)
  • n8n instance with credentials setup

How to Customize the Workflow

  • Add delay between messages: Use the Wait node to introduce pauses (e.g., 5–10 seconds).
  • Change message format: Modify the HTTP Request node to send media or templates.
  • Personalize content: Include dynamic fields like Name, Image URL, etc.
  • Error handling: Add IF or SET nodes to capture failed attempts, retry, or log errors.

Workflow Highlights

  • Triggered every 5 minutes using the Schedule Trigger node.
  • Filters messages with Status = pending.
  • Cleans numbers and verifies WhatsApp existence before sending.
  • Sends WhatsApp messages via Rapiwa (Unofficial API).
  • Updates Google Sheets to mark Status = sent or not sent and Verification = verified/unverified.
  • Wait node prevents rapid-fire sending that could lead to being flagged by WhatsApp.

Setup in n8n

1. Connect Google Sheets

  • Add a Google Sheets node
  • Authenticate using your Google account
  • Select the document and worksheet
  • Use filter: Status = pending

2. Loop Through Rows

  • Use SplitInBatches or a Code node to process rows in small chunks (e.g., 5 rows)
  • Add a Wait node to delay 5 seconds between messages

3. Send Message via HTTP Node

  • How the "Send Message Using Rapiwa" Node Sends Messages

  • This node makes an HTTP POST request to the Rapiwa API endpoint:
    https://app.rapiwa.com/api/send-message

  • It uses Bearer Token Authentication with your Rapiwa API key.

  • When this node runs, it sends a WhatsApp message to the specified number with the given text and optional image.

  • The Rapiwa API handles message delivery using your own WhatsApp number connected to their service.

  • JSON Body:

{
  "number": "{{ $json['WhatsApp No'] }}",
  "message": "{{ $json['Message'] }}"
}

Sample Google Sheet Structure

A Google Sheet formatted like this sample

| SL | WhatsApp No | Name | Message | Image URL | Verification | Status | |----|----------------|------------------------|----------------------|---------------------------------------------------------------------------|--------------|---------| | 1 | 8801322827799 | SpaGreen Creative | This is Test Message | https://spagreen.sgp1.cdn.digitaloceanspaces.com/... | verified | sent | | 2 | 8801725402187 | Abdul Mannan Zinnat | This is Test Message | https://spagreen.sgp1.cdn.digitaloceanspaces.com/... | verified | sent |

Tips

  • Modify the Limit node to increase/decrease messages per cycle.
  • Adjust the Wait node to control how fast messages are sent (e.g., 5–10s delay).
  • Make sure WhatsApp numbers are properly formatted (e.g., 8801XXXXXXXXX, no +, no spaces).
  • Store your Rapiwa API key securely using n8n credentials.
  • Use publicly accessible image URLs if sending images.
  • Always mark processed messages as "sent" to avoid duplicates.
  • Use the Error workflow in n8n to catch failed sends for retry.
  • Test with a small batch before going full-scale.
  • Schedule the Trigger node for every 5 minutes to keep automation running.

Useful Links

Support & Community

Need help setting up or customizing the workflow? Reach out here:

Send Bulk WhatsApp Messages from Google Sheets using Rapiwa API

This n8n workflow automates the process of sending bulk WhatsApp messages to contacts listed in a Google Sheet using the Rapiwa API. It's designed to streamline communication for marketing campaigns, notifications, or any scenario requiring personalized messages to a large audience.

What it does

This workflow performs the following steps:

  1. Triggers on Schedule: The workflow is set to run on a predefined schedule (e.g., daily, hourly, or weekly) to check for new messages to send.
  2. Reads Data from Google Sheets: It connects to a specified Google Sheet and retrieves contact information, including phone numbers and message content.
  3. Loops Over Items: Each row (contact) from the Google Sheet is processed individually.
  4. Limits Processing (Optional): A "Limit" node is included, which can be configured to process only a certain number of items per run. This is useful for testing or for adhering to API rate limits.
  5. Prepares WhatsApp Message: A "Code" node processes the data from Google Sheets to format the message and phone number according to the Rapiwa API's requirements.
  6. Sends WhatsApp Message: An "HTTP Request" node sends a POST request to the Rapiwa API endpoint with the prepared message and recipient details.
  7. Conditional Waiting: An "If" node checks the response from the Rapiwa API.
    • On Success: If the message is sent successfully, the workflow waits for a short period (e.g., 5 seconds) before processing the next message. This delay helps prevent API rate limiting.
    • On Failure: If the message sending fails, the workflow does not explicitly handle the error in the provided JSON, but this branch could be extended to log errors or retry.
  8. Sticky Note: A sticky note is included for documentation purposes, indicating the purpose of the conditional wait.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Sheets Account: A Google account with access to the Google Sheet containing your contact list and message content.
  • Rapiwa API Account: An account with Rapiwa API and the necessary API key/credentials to send WhatsApp messages.
  • Google Sheets Credential: An n8n credential configured for Google Sheets (OAuth2 recommended).
  • HTTP Request Credential (Rapiwa API): An n8n credential configured for the Rapiwa API (likely an API Key or Bearer Token).

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON workflow definition.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the JSON content.
  2. Configure Google Sheets Node (Node ID: 18):
    • Select your Google Sheets credential.
    • Specify the "Spreadsheet ID" and "Sheet Name" from which to read your data.
    • Ensure your sheet has columns for phone numbers and message content, and update the "Code" node logic if your column names differ.
  3. Configure Rapiwa API HTTP Request Node (Node ID: 19):
    • Select or create an HTTP Request credential for the Rapiwa API. This typically involves setting up an API Key or Bearer Token in the headers.
    • Update the "URL" to the correct Rapiwa API endpoint for sending messages.
    • Adjust the "Body Parameters" to match the Rapiwa API's expected payload for sending messages, using expressions to pull data from the Google Sheets node (e.g., {{ $json.phone_number }}, {{ $json.message_content }}).
  4. Configure Loop Over Items (Node ID: 39):
    • The batch size can be adjusted if you need to send messages in smaller groups.
  5. Configure Limit Node (Node ID: 1237):
    • By default, this node might be set to a low number for testing. Adjust the "Limit" value to 0 or remove the node if you want to process all items from the Google Sheet.
  6. Configure Wait Node (Node ID: 514):
    • Adjust the "Delay" value as needed to comply with Rapiwa API rate limits. A 5-second delay is a common starting point.
  7. Activate the Workflow:
    • Enable the workflow in n8n.
    • The "Schedule Trigger" node (Node ID: 839) will automatically run the workflow at its configured interval. You can also manually execute it for testing.

Important Notes:

  • Error Handling: The current workflow includes a basic "If" condition for success/failure but does not have robust error handling for API failures. Consider adding nodes like "Error Trigger" or "Send Email" to be notified of issues.
  • Rate Limits: Be mindful of Rapiwa API's rate limits. The "Wait" node helps, but for very large lists, you might need more sophisticated rate-limiting strategies or to process messages in batches over a longer period.
  • Data Structure: Ensure the column names in your Google Sheet match the expressions used in the "Code" and "HTTP Request" nodes (e.g., if your sheet has a column named "Phone Number", use {{ $json["Phone Number"] }}). You might need to adjust the "Code" node to correctly map your sheet's columns to the Rapiwa API's requirements.

Related Templates

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

Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.

gotoHumanBy gotoHuman
353

Ai website scraper & company intelligence

AI Website Scraper & Company Intelligence Description This workflow automates the process of transforming any website URL into a structured, intelligent company profile. It's triggered by a form, allowing a user to submit a website and choose between a "basic" or "deep" scrape. The workflow extracts key information (mission, services, contacts, SEO keywords), stores it in a structured Supabase database, and archives a full JSON backup to Google Drive. It also features a secondary AI agent that automatically finds and saves competitors for each company, building a rich, interconnected database of company intelligence. --- Quick Implementation Steps Import the Workflow: Import the provided JSON file into your n8n instance. Install Custom Community Node: You must install the community node from: https://www.npmjs.com/package/n8n-nodes-crawl-and-scrape FIRECRAWL N8N Documentation https://docs.firecrawl.dev/developer-guides/workflow-automation/n8n Install Additional Nodes: n8n-nodes-crawl-and-scrape and n8n-nodes-mcp fire crawl mcp . Set up Credentials: Create credentials in n8n for FIRE CRAWL API,Supabase, Mistral AI, and Google Drive. Configure API Key (CRITICAL): Open the Web Search tool node. Go to Parameters → Headers and replace the hardcoded Tavily AI API key with your own. Configure Supabase Nodes: Assign your Supabase credential to all Supabase nodes. Ensure table names (e.g., companies, competitors) match your schema. Configure Google Drive Nodes: Assign your Google Drive credential to the Google Drive2 and save to Google Drive1 nodes. Select the correct Folder ID. Activate Workflow: Turn on the workflow and open the Webhook URL in the “On form submission” node to access the form. --- What It Does Form Trigger Captures user input: “Website URL” and “Scraping Type” (basic or deep). Scraping Router A Switch node routes the flow: Deep Scraping → AI-based MCP Firecrawler agent. Basic Scraping → Crawlee node. Deep Scraping (Firecrawl AI Agent) Uses Firecrawl and Tavily Web Search. Extracts a detailed JSON profile: mission, services, contacts, SEO keywords, etc. Basic Scraping (Crawlee) Uses Crawl and Scrape node to collect raw text. A Mistral-based AI extractor structures the data into JSON. Data Storage Stores structured data in Supabase tables (companies, company_basicprofiles). Archives a full JSON backup to Google Drive. Automated Competitor Analysis Runs after a deep scrape. Uses Tavily web search to find competitors (e.g., from Crunchbase). Saves competitor data to Supabase, linked by company_id. --- Who's It For Sales & Marketing Teams: Enrich leads with deep company info. Market Researchers: Build structured, searchable company databases. B2B Data Providers: Automate company intelligence collection. Developers: Use as a base for RAG or enrichment pipelines. --- Requirements n8n instance (self-hosted or cloud) Supabase Account: With tables like companies, competitors, social_links, etc. Mistral AI API Key Google Drive Credentials Tavily AI API Key (Optional) Custom Nodes: n8n-nodes-crawl-and-scrape --- How It Works Flow Summary Form Trigger: Captures “Website URL” and “Scraping Type”. Switch Node: deep → MCP Firecrawler (AI Agent). basic → Crawl and Scrape node. Scraping & Extraction: Deep path: Firecrawler → JSON structure. Basic path: Crawlee → Mistral extractor → JSON. Storage: Save JSON to Supabase. Archive in Google Drive. Competitor Analysis (Deep Only): Finds competitors via Tavily. Saves to Supabase competitors table. End: Finishes with a No Operation node. --- How To Set Up Import workflow JSON. Install community nodes (especially n8n-nodes-crawl-and-scrape from npm). Configure credentials (Supabase, Mistral AI, Google Drive). Add your Tavily API key. Connect Supabase and Drive nodes properly. Fix disconnected “basic” path if needed. Activate workflow. Test via the webhook form URL. --- How To Customize Change LLMs: Swap Mistral for OpenAI or Claude. Edit Scraper Prompts: Modify system prompts in AI agent nodes. Change Extraction Schema: Update JSON Schema in extractor nodes. Fix Relational Tables: Add Items node before Supabase inserts for arrays (social links, keywords). Enhance Automation: Add email/slack notifications, or replace form trigger with a Google Sheets trigger. --- Add-ons Automated Trigger: Run on new sheet rows. Notifications: Email or Slack alerts after completion. RAG Integration: Use the Supabase database as a chatbot knowledge source. --- Use Case Examples Sales Lead Enrichment: Instantly get company + competitor data from a URL. Market Research: Collect and compare companies in a niche. B2B Database Creation: Build a proprietary company dataset. --- WORKFLOW IMAGE --- Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|----------------|-----------| | Form Trigger 404 | Workflow not active | Activate the workflow | | Web Search Tool fails | Missing Tavily API key | Replace the placeholder key | | FIRECRAWLER / find competitor fails | Missing MCP node | Install n8n-nodes-mcp | | Basic scrape does nothing | Switch node path disconnected | Reconnect “basic” output | | Supabase node error | Wrong table/column names | Match schema exactly | --- Need Help or More Workflows? Want to customize this workflow for your business or integrate it with your existing tools? Our team at Digital Biz Tech can tailor it precisely to your use case from automation logic to AI-powered enhancements. Contact: shilpa.raju@digitalbiz.tech For more such offerings, visit us: https://www.digitalbiz.tech ---

DIGITAL BIZ TECHBy DIGITAL BIZ TECH
923