Bulk verify WhatsApp numbers using Rapiwa API and Google Sheets
WhatsApp Bulk Number Verification in Google Sheets Using Unofficial Rapiwa API
Who’s it for
This workflow is for marketers, small business owners, freelancers, and support teams who want to automate WhatsApp messaging using a Google Sheet without the official WhatsApp Business API. It’s suitable when you need a budget-friendly, easy-to-maintain solution that uses your personal or business WhatsApp number via an unofficial API service such as Rapiwa.
How it works / What it does
- The workflow looks for rows in a Google Sheet where the
Statuscolumn ispending. - It cleans each phone number (removes non-digits).
- It verifies the number with the Rapiwa verify endpoint (
/api/verify-whatsapp). - If the number is verified:
- The workflow can send a message (optional).
- It updates the sheet:
Verification = verified,Status = sent(or leavesStatusfor the send node to update).
- If the number is not verified:
- It skips sending.
- It updates the sheet:
Verification = unverified,Status = not sent.
- The workflow processes rows in batches and inserts short delays between items to avoid rate limits.
- The whole process runs on a schedule (configurable).
Key features
- Scheduled automatic checks (configurable interval; recommended 5–10 minutes).
- Cleans phone numbers to a proper format before verification.
- Verifies WhatsApp registration using Rapiwa.
- Batch processing with limits to control workload (recommended max per run configurable).
- Short delay between items to reduce throttling and temporary blocks.
- Automatic sheet updates for auditability (verified/unverified, sent/not sent).
Defaults recommended in this workflow
- Trigger interval: every 5–10 minutes (adjustable).
- Max items per run: configurable (example: 200 max per cycle).
- Delay between items: 2–5 seconds (example uses 3 seconds).
How to set up
- Duplicate the sample Google Sheet: ➤ Sample
- Fill contact rows and set
Status = pending. Include columns likeWhatsApp No,Name,Message,Verification,Status. - In n8n, add and authenticate a Google Sheets node pointed to your sheet.
- Create an HTTP Bearer credential in n8n and paste your Rapiwa API key.
- Configure the workflow nodes (Trigger → Google Sheets → Limit/SplitInBatches → Code (clean) → HTTP Request (verify) → If → Update Sheet → Wait).
- Enable the workflow and monitor first runs with a small test batch.
Requirements
- n8n instance with Google Sheets and HTTP Request nodes enabled.
- Google Sheets OAuth2 credentials configured in n8n.
- Rapiwa account and Bearer token (stored in n8n credentials).
- Google Sheet formatted to match the workflow columns.
Why use Rapiwa
- Cost-effective and developer-friendly REST API for WhatsApp verification and sending.
- Simple integration via HTTP requests and n8n.
- Useful when you prefer not to use the official WhatsApp Business API.
Note: Rapiwa is an unofficial service — review its terms and risks before production use.
How to customize
- Change schedule frequency in the Trigger node.
- Adjust maxItems in Limit/SplitInBatches for throughput control.
- Change the Wait node delay for safer sending.
- Modify the HTTP Request body to support media or templates if the provider supports it.
- Add logging or a separate audit sheet to record API responses and errors.
Best practices
- Test with a small batch first.
- Keep the sheet headers exact and consistent.
- Store API keys in n8n credentials (do not hardcode).
- Increase Wait time or reduce batch size if you see rate limits.
- Keep a log sheet of verified/unverified rows for troubleshooting.
Example HTTP verify body (n8n HTTP Request node)
{
"number": "{{ $json['WhatsApp No'] }}"
}
Notes and best practices
- Test with a small batch before scaling.
- Store the Rapiwa token in n8n credentials, not in node fields.
- Increase Wait delay or reduce batch size if you see rate limits or temporary blocks.
- Keep the sheet headers consistent; the workflow matches columns by name.
- Log API responses or errors for troubleshooting.
Optional
- Add a send-message HTTP Request node after verification to send messages.
- Append successful and failed rows to separate sheets for easy review.
Support & Community
Need help setting up or customizing the workflow? Reach out here:
- WhatsApp: Chat with Support
- Discord: Join SpaGreen Server
- Facebook Group: SpaGreen Community
- Website: SpaGreen Creative
- Envato: SpaGreen Portfolio
n8n Workflow: Bulk Verify WhatsApp Numbers using Rapiwha API and Google Sheets
This n8n workflow automates the process of bulk verifying WhatsApp numbers by reading them from a Google Sheet, sending them to the Rapiwha API for verification, and then updating the Google Sheet with the verification results.
It's designed to streamline the task of cleaning up phone number lists, ensuring that only valid WhatsApp numbers are targeted for communication.
What it does
- Triggers on Schedule: The workflow starts automatically at predefined intervals.
- Reads WhatsApp Numbers from Google Sheet: It connects to a specified Google Sheet and retrieves a list of WhatsApp numbers from a designated column.
- Splits Data into Batches: To manage API rate limits and processing efficiency, the retrieved numbers are split into smaller batches.
- Verifies Numbers via Rapiwha API: For each batch, it makes an HTTP request to the Rapiwha API to verify the WhatsApp status of the numbers.
- Processes API Response: It then processes the API response to extract the verification status for each number.
- Filters Valid Numbers: The workflow includes logic to identify and filter out numbers that are confirmed as valid WhatsApp numbers.
- Updates Google Sheet: Finally, it updates the original Google Sheet with the verification results, marking each number as "Valid" or "Invalid" in a specified column.
- Applies Rate Limiting: A
Waitnode is included to introduce a delay between API calls, preventing rate limit issues with the Rapiwha API. - Limits Items for Processing: A
Limitnode is used to control the number of items processed in each run, useful for testing or managing large datasets incrementally.
Prerequisites/Requirements
- n8n Instance: A running instance of n8n.
- Google Account: A Google account with access to Google Sheets.
- Rapiwha API Key: An API key for the Rapiwha WhatsApp verification service.
- Google Sheet: A Google Sheet containing a column with WhatsApp numbers to be verified. You will need to specify the Spreadsheet ID and the name of the sheet.
- Google Sheets Credential: An n8n credential configured for Google Sheets (OAuth2 recommended).
- HTTP Request Credential (API Key): An n8n credential for the Rapiwha API (likely an API key or bearer token).
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Google Sheets: Set up or select your Google Sheets credential.
- HTTP Request: Set up a new HTTP Request credential for the Rapiwha API, providing your API key.
- Configure Google Sheets Node (ID: 18):
- Specify the Spreadsheet ID of your Google Sheet.
- Enter the Sheet Name where your WhatsApp numbers are located.
- Set the Range to cover the column containing the numbers (e.g.,
A:Aif numbers are in column A). - Identify the column name that contains the WhatsApp numbers.
- Configure HTTP Request Node (ID: 19):
- Update the URL to the Rapiwha API endpoint for number verification.
- Configure the Headers to include your Rapiwha API key (e.g.,
Authorization: Bearer YOUR_API_KEYor a custom header as required by Rapiwha). - Adjust the Body to send the WhatsApp numbers in the format expected by the Rapiwha API.
- Configure Code Node (ID: 834):
- Review and adjust the JavaScript code to correctly parse the Rapiwha API response and extract the verification status.
- Configure If Node (ID: 20):
- Ensure the condition correctly identifies "Valid" WhatsApp numbers based on the output from the Code node.
- Configure Google Sheets Node (for updating):
- Specify the Spreadsheet ID and Sheet Name again.
- Set the Operation to "Update Row" or "Update Cell".
- Map the "WhatsApp Number" and "Status" (e.g., "Valid", "Invalid") to the appropriate columns in your Google Sheet.
- Activate the Workflow: Once configured, activate the workflow. It will run according to the schedule defined in the "Schedule Trigger" node.
- Manual Execution: You can also execute the workflow manually for testing purposes.
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.
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
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.