Monitor a Google Sheet for pending rows, clean numbers, verify each via the Rapiwa API, and update the sheet with verification results on a configurable schedule, with an optional send step.
The AI agent reads a Google Sheet, cleans and formats phone numbers, and verifies each one using the Rapiwa verify endpoint. It updates the sheet with Verification and Status fields based on the result and can optionally send messages to verified numbers. All steps run on a configurable schedule with batch processing and delay controls to minimize rate limits and provide auditable records.
A concise, end-to-end view of automated tasks.
Scan the Google Sheet for rows where Status = pending
Clean and normalize phone numbers to digits-only format
Verify numbers using the Rapiwa /api/verify-whatsapp endpoint
Update the sheet with Verification = verified and Status accordingly
Optionally send a message to verified numbers and log outcomes
Process rows in batches with configurable delays to respect rate limits
Before: manual verification and record-keeping caused delays and errors. After: automated verification with auditable logs and clear sheet updates streamline campaigns.
A simple three-step system flow anyone can implement.
Scan the Google Sheet for rows where Status = pending and prepare the numbers for verification.
Clean each number and call the Rapiwa verify endpoint to determine WhatsApp registration.
If verified, update Verification = verified and adjust Status; optionally send a message. If not verified, mark as unverified and not sent.
A realistic usage scenario and outcome.
Scenario: A marketer maintains a Google Sheet with 420 pending numbers. The AI agent runs every 5 minutes, processes batches of 40 numbers, cleans and verifies each via Rapiwa, and updates the sheet with Verification and Status. If configured, it sends a standard message to verified numbers. Outcome: approximately 80–120 verifications per run with auditable logs and updated sheets after each cycle.
Roles that gain concrete value from automated verification.
Needs clean, verified contact lists before campaigns to improve deliverability and response rates.
Wants to validate numbers prior to proactive outreach to reduce bounces and misdirected messages.
Requires an affordable, low-maintenance automation to maintain outreach lists.
Needs reliable verification before sending campaigns to avoid wasted effort.
Prefers scheduled verification and auditable logs for compliance and reporting.
Requires batch processing and rate-limit safeguards to scale outreach.
Key tools used and what the agent does inside each.
Reads rows, checks Status = pending, and updates Verification and Status fields after verification.
Sends verify requests to /api/verify-whatsapp and returns number validity for each entry.
Orchestrates the workflow: triggers Google Sheets read, sends HTTP requests, and updates the sheet in sequence.
Practical scenarios where this AI agent shines.
Common concerns and practical answers.
Rapiwa is an unofficial API. While it provides a cost-effective and developer-friendly route for verification and messaging, review its terms of service and risks before production use. Always test thoroughly with small batches and monitor for changes in availability or limits. Consider having a fallback plan or parallel verification with a supported channel if reliability is critical. Do not rely on it for mission-critical operations without risk assessment.
Yes. The agent is designed to run on a configurable schedule. You can set the interval and batch limits to match your campaign cadence and API tolerance. Scheduling helps keep lists fresh without requiring manual launches. It also supports pauses and resuming after maintenance windows.
The workflow uses batch processing with configurable delays between items to minimize throttling and temporary blocks. If a limit is reached, processing pauses briefly before continuing. You can adjust max items per run and the delay to suit your provider’s guidelines. Monitoring logs helps detect when adjustments are needed.
Unverified numbers are marked with Verification = unverified and Status = not sent or left pending for reattempts depending on configuration. They remain auditable in the sheet. You can requeue them in a future run or remove them from campaigns as needed. This ensures you don’t accidentally send messages to invalid numbers.
Yes, messaging can be enabled as an optional step after verification. You configure the message content and delivery conditions, and the agent will trigger messages for verified numbers. Messages follow the same batch and rate-limit safeguards to minimize blocks. Always test message content and timing in a small batch first.
Store API keys and credentials in a secure credentials store (not in node fields). Use encrypted storage where available and rotate keys regularly. Limit access to authorized users and monitor usage. Never hardcode tokens in scripts or configurations that could be exposed. This helps prevent leaks and abuse.
Yes. The agent matches columns by name, so you can tailor headers to your workflow. Ensure the essential fields like WhatsApp No, Name, Message, Verification, and Status exist and align with the automation. If you modify headers, update the workflow mappings accordingly. Regularly verify header consistency for reliable processing.
Monitor a Google Sheet for pending rows, clean numbers, verify each via the Rapiwa API, and update the sheet with verification results on a configurable schedule, with an optional send step.
