Job post to sales lead pipeline with Scrape.do, Apollo.io & OpenAI
Lead Sourcing by Job Posts For Outreach With Scrape.do API & Open AI & Google Sheets
Overview
This n8n workflow automates the complete lead generation process by scraping job postings from Indeed, enriching company data via Apollo.io, identifying decision-makers, and generating personalized LinkedIn outreach messages using OpenAI. It integrates with Scrape.do for reliable web scraping, Apollo.io for B2B data enrichment, OpenAI for AI-powered personalization, and Google Sheets for centralized data storage.
Perfect for: Sales teams, recruiters, business development professionals, and marketing agencies looking to automate their outbound prospecting pipeline.
Workflow Components
1. β° Schedule Trigger
| Property | Value | |----------|-------| | Type | Schedule Trigger | | Purpose | Automatically initiates workflow on a recurring schedule | | Frequency | Weekly (Every Monday) | | Time | 00:00 UTC |
Function: Ensures consistent, hands-off lead generation by running the pipeline automatically without manual intervention.
2. π Scrape.do Indeed API
| Property | Value |
|----------|-------|
| Type | HTTP Request (GET) |
| Purpose | Scrapes job listings from Indeed via Scrape.do proxy API |
| Endpoint | https://api.scrape.do |
| Output Format | Markdown |
Request Parameters:
| Parameter | Value | Description | |-----------|-------|-------------| | token | API Token | Scrape.do authentication | | url | Indeed Search URL | Target job search page | | super | true | Uses residential proxies | | geoCode | us | US-based content | | render | true | JavaScript rendering enabled | | device | mobile | Mobile viewport for cleaner HTML | | output | markdown | Lightweight text output |
Function: Fetches Indeed job listings with anti-bot bypass, returning clean markdown for easy parsing.
3. π Parse Indeed Jobs
| Property | Value | |----------|-------| | Type | Code Node (JavaScript) | | Purpose | Extracts structured job data from markdown | | Mode | Run once for all items |
Extracted Fields:
| Field | Description | Example | |-------|-------------|---------| | jobTitle | Position title | "Senior Data Engineer" | | jobUrl | Indeed job link | "https://indeed.com/viewjob?jk=abc123" | | jobId | Indeed job identifier | "abc123" | | companyName | Hiring company | "Acme Corporation" | | location | City, State | "San Francisco, CA" | | salary | Pay range | "$120,000 - $150,000" | | jobType | Employment type | "Full-time" | | source | Data source | "Indeed" | | dateFound | Scrape date | "2025-01-15" |
Function: Parses markdown using regex patterns, filters invalid entries, and deduplicates by company name.
4. π Add New Company (Google Sheets)
| Property | Value | |----------|-------| | Type | Google Sheets Node | | Purpose | Stores parsed job postings for tracking | | Operation | Append rows | | Target Sheet | "Add New Company" |
Function: Creates a historical record of all discovered job postings and companies for pipeline tracking.
5. π’ Apollo Organization Search
| Property | Value |
|----------|-------|
| Type | HTTP Request (POST) |
| Purpose | Enriches company data via Apollo.io API |
| Endpoint | https://api.apollo.io/v1/organizations/search |
| Authentication | HTTP Header Auth (x-api-key) |
Request Body:
{
"q_organization_name": "Company Name",
"page": 1,
"per_page": 1
}
Response Fields:
| Field | Description | |-------|-------------| | id | Apollo organization ID | | name | Official company name | | website_url | Company website | | linkedin_url | LinkedIn company page | | industry | Business sector | | estimated_num_employees | Company size | | founded_year | Year established | | city, state, country | Location details | | short_description | Company overview |
Function: Retrieves comprehensive company intelligence including LinkedIn profiles, industry classification, and employee count.
6. π€ Extract Apollo Org Data
| Property | Value | |----------|-------| | Type | Code Node (JavaScript) | | Purpose | Parses Apollo response and merges with original data | | Mode | Run once for each item |
Function: Extracts relevant fields from Apollo API response and combines with job posting data for downstream processing.
7. π₯ Apollo People Search
| Property | Value |
|----------|-------|
| Type | HTTP Request (POST) |
| Purpose | Finds decision-makers at target companies |
| Endpoint | https://api.apollo.io/v1/mixed_people/search |
| Authentication | HTTP Header Auth (x-api-key) |
Request Body:
{
"organization_ids": ["apollo_org_id"],
"person_titles": [
"CTO",
"Chief Technology Officer",
"VP Engineering",
"Head of Engineering",
"Engineering Manager",
"Technical Director",
"CEO",
"Founder"
],
"page": 1,
"per_page": 3
}
Response Fields:
| Field | Description | |-------|-------------| | first_name | Contact first name | | last_name | Contact last name | | title | Job title | | email | Email address | | linkedin_url | LinkedIn profile URL | | phone_number | Direct phone |
Function: Identifies key stakeholders and decision-makers based on configurable title filters.
8. π Format Leads
| Property | Value | |----------|-------| | Type | Code Node (JavaScript) | | Purpose | Structures lead data for outreach | | Mode | Run once for all items |
Function: Combines person data with company context, creating comprehensive lead profiles ready for personalization.
9. π€ Generate Personalized Message (OpenAI)
| Property | Value | |----------|-------| | Type | OpenAI Node | | Purpose | Creates custom LinkedIn connection messages | | Model | gpt-4o-mini | | Max Tokens | 150 | | Temperature | 0.7 |
System Prompt:
You are a professional outreach specialist. Write personalized LinkedIn connection request messages. Keep messages under 300 characters. Be friendly, professional, and mention a specific reason for connecting based on their role and company.
User Prompt Variables:
| Variable | Source |
|----------|--------|
| Name | $json.fullName |
| Title | $json.title |
| Company | $json.companyName |
| Industry | $json.industry |
| Job Context | $json.jobTitle |
Function: Generates unique, contextual outreach messages that reference specific hiring activity and company details.
10. π Merge Lead + Message
| Property | Value | |----------|-------| | Type | Code Node (JavaScript) | | Purpose | Combines lead data with generated message | | Mode | Run once for each item |
Function: Merges OpenAI response with lead profile, creating the final enriched record.
11. πΎ Save Leads to Sheet
| Property | Value | |----------|-------| | Type | Google Sheets Node | | Purpose | Stores final lead data with personalized messages | | Operation | Append rows | | Target Sheet | "Leads" |
Data Mapping:
| Column | Data | |--------|------| | First Name | Lead's first name | | Last Name | Lead's last name | | Title | Job title | | Company | Company name | | LinkedIn URL | Profile link | | Country | Location | | Industry | Business sector | | Date Added | Timestamp | | Source | "Indeed + Apollo" | | Personalized Message | AI-generated outreach text |
Function: Creates actionable lead database ready for outreach campaigns.
Workflow Flow
β° Schedule Trigger
β
βΌ
π Scrape.do Indeed API βββΊ Fetches job listings with JS rendering
β
βΌ
π Parse Indeed Jobs βββΊ Extracts company names, job details
β
βΌ
π Add New Company βββΊ Saves to Google Sheets (Companies)
β
βΌ
π’ Apollo Org Search βββΊ Enriches company data
β
βΌ
π€ Extract Apollo Org Data βββΊ Parses API response
β
βΌ
π₯ Apollo People Search βββΊ Finds decision-makers
β
βΌ
π Format Leads βββΊ Structures lead profiles
β
βΌ
π€ Generate Personalized Message βββΊ AI creates custom outreach
β
βΌ
π Merge Lead + Message βββΊ Combines all data
β
βΌ
πΎ Save Leads to Sheet βββΊ Final storage (Leads)
Configuration Requirements
API Keys & Credentials
| Credential | Purpose | Where to Get | |------------|---------|--------------| | Scrape.do API Token | Web scraping with anti-bot bypass | scrape.do/dashboard | | Apollo.io API Key | B2B data enrichment | apollo.io/settings/integrations | | OpenAI API Key | AI message generation | platform.openai.com | | Google Sheets OAuth2 | Data storage | n8n Credentials Setup |
n8n Credential Setup
| Credential Type | Configuration |
|-----------------|---------------|
| HTTP Header Auth (Apollo) | Header: x-api-key, Value: Your Apollo API key |
| OpenAI API | API Key: Your OpenAI API key |
| Google Sheets OAuth2 | Complete OAuth flow with Google |
Key Features
π Intelligent Job Scraping
- Anti-Bot Bypass: Residential proxy rotation via Scrape.do
- JavaScript Rendering: Full headless browser for dynamic content
- Mobile Optimization: Cleaner HTML with mobile viewport
- Markdown Output: Lightweight, easy-to-parse format
π’ B2B Data Enrichment
- Company Intelligence: Industry, size, location, LinkedIn
- Decision-Maker Discovery: Title-based filtering
- Contact Information: Email, phone, LinkedIn profiles
- Real-Time Data: Fresh information from Apollo.io
π€ AI-Powered Personalization
- Contextual Messages: References specific hiring activity
- Character Limit: Optimized for LinkedIn (300 chars)
- Variable Temperature: Balanced creativity and consistency
- Role-Specific: Tailored to recipient's title and company
π Automated Data Management
- Dual Sheet Storage: Companies + Leads separation
- Timestamp Tracking: Historical records
- Deduplication: Prevents duplicate entries
- Ready for Export: CSV-compatible format
Use Cases
π― Sales Prospecting
- Identify companies actively hiring in your target market
- Find decision-makers at companies investing in growth
- Generate personalized cold outreach at scale
- Track pipeline from discovery to contact
π₯ Recruiting & Talent Acquisition
- Monitor competitor hiring patterns
- Identify companies building specific teams
- Connect with hiring managers directly
- Build talent pipeline relationships
π Market Intelligence
- Track industry hiring trends
- Monitor competitor expansion signals
- Identify emerging market opportunities
- Benchmark salary ranges by role
π€ Partnership Development
- Find companies investing in complementary areas
- Identify potential integration partners
- Connect with technical leadership
- Build strategic relationship pipeline
Technical Notes
| Specification | Value | |---------------|-------| | Processing Time | 2-5 minutes per run (depending on job count) | | Jobs per Run | ~25 unique companies | | API Calls per Run | 1 Scrape.do + ~25 Apollo Org + ~25 Apollo People + ~75 OpenAI | | Data Accuracy | 90%+ for company matching | | Success Rate | 99%+ with proper error handling |
Rate Limits to Consider
| Service | Free Tier Limit | Recommendation | |---------|-----------------|----------------| | Scrape.do | 1,000 credits/month | ~40 runs/month | | Apollo.io | 100 requests/day | Add Wait nodes if needed | | OpenAI | Based on usage | Monitor costs (~$0.01-0.05/run) | | Google Sheets | 300 requests/minute | No issues expected |
Setup Instructions
Step 1: Import Workflow
- Copy the JSON workflow configuration
- In n8n: Workflows β Import from JSON
- Paste configuration and save
Step 2: Configure Scrape.do
- Sign up at scrape.do
- Navigate to Dashboard β API Token
- Copy your token
- Token is embedded in URL query parameter (already configured)
To customize search:
Change the `url` parameter in "Scrape.do Indeed API" node:
- q=data+engineer (search term)
- l=Remote (location)
- fromage=7 (last 7 days)
Step 3: Configure Apollo.io
- Sign up at apollo.io
- Go to Settings β Integrations β API Keys
- Create new API key
- In n8n: Credentials β Add Credential β Header Auth
- Name:
x-api-key - Value: Your Apollo API key
- Name:
- Select this credential in both Apollo HTTP nodes
Step 4: Configure OpenAI
- Go to platform.openai.com
- Create new API key
- In n8n: Credentials β Add Credential β OpenAI
- Paste API key
- Select credential in "Generate Personalized Message" node
Step 5: Configure Google Sheets
- Create new Google Spreadsheet
- Create two sheets:
- Sheet 1: "Add New Company"
- Columns:
companyName | jobTitle | jobUrl | location | salary | source | postedDate
- Columns:
- Sheet 2: "Leads"
- Columns:
First Name | Last Name | Title | Company | LinkedIn URL | Country | Industry | Date Added | Source | Personalized Message
- Columns:
- Sheet 1: "Add New Company"
- Copy Sheet ID from URL
- In n8n: Credentials β Add Credential β Google Sheets OAuth2
- Update both Google Sheets nodes with your Sheet ID
Step 6: Test and Activate
- Manual Test: Click "Execute Workflow" button
- Verify Each Node: Check outputs step by step
- Review Data: Confirm data appears in Google Sheets
- Activate: Toggle workflow to "Active"
Error Handling
Common Issues
| Issue | Cause | Solution | |-------|-------|----------| | "Invalid character: [" | Empty/malformed company name | Check Parse Indeed Jobs output | | "Node does not have credentials" | Credential not linked | Open node β Select credential | | Empty Parse Results | Indeed HTML structure changed | Check Scrape.do raw output | | Apollo Rate Limit (429) | Too many requests | Add 5-10s Wait node between calls | | OpenAI Timeout | Too many tokens | Reduce batch size or max_tokens | | "Your request is invalid" | Malformed JSON body | Verify expression syntax in HTTP nodes |
Troubleshooting Steps
- Verify Credentials: Test each credential individually
- Check Node Outputs: Use "Execute Node" for debugging
- Monitor API Usage: Check Apollo and OpenAI dashboards
- Review Logs: Check n8n execution history for details
- Test with Sample: Use known company name to verify Apollo
Recommended Error Handling Additions
For production use, consider adding:
- IF node after Apollo Org Search to handle empty results
- Error Workflow trigger for notifications
- Wait nodes between API calls for rate limiting
- Retry logic for transient failures
Performance Specifications
| Metric | Value | |--------|-------| | Execution Time | 2-5 minutes per scheduled run | | Jobs Discovered | ~25 per Indeed page | | Leads Generated | 1-3 per company (based on title matches) | | Message Quality | Professional, contextual, <300 chars | | Data Freshness | Real-time from Indeed + Apollo | | Storage Format | Google Sheets (unlimited rows) |
API Reference
Scrape.do API
| Endpoint | Method | Purpose |
|----------|--------|---------|
| https://api.scrape.do | GET | Direct URL scraping |
Documentation: scrape.do/documentation
Apollo.io API
| Endpoint | Method | Purpose |
|----------|--------|---------|
| /v1/organizations/search | POST | Company lookup |
| /v1/mixed_people/search | POST | People search |
Documentation: apolloio.github.io/apollo-api-docs
OpenAI API
| Endpoint | Method | Purpose |
|----------|--------|---------|
| /v1/chat/completions | POST | Message generation |
Documentation: [platform.openai.com
n8n Form Trigger to Google Sheets with OpenAI and HTTP Request
This n8n workflow automates the process of capturing form submissions, enriching the data using OpenAI, and then storing it in a Google Sheet. It's designed to streamline data collection and intelligent processing, making it ideal for lead generation, feedback collection, or any scenario where form data needs immediate analysis and storage.
What it does
This workflow performs the following key steps:
- Listens for Form Submissions: It starts by waiting for a submission from an n8n form.
- Enriches Data with OpenAI: The submitted data is then passed to OpenAI, which can be configured to analyze, summarize, categorize, or extract specific information from the form fields (e.g., generating a lead qualification score, summarizing comments, or extracting key entities).
- Transforms Data: A "Code" node is used to process and format the data, likely preparing it for storage or further API calls. This could involve mapping fields, combining values, or performing calculations.
- Makes an HTTP Request: An HTTP Request node sends the processed data to an external API. This could be for posting to a CRM, another data store, or triggering a subsequent action in a different system.
- Stores Data in Google Sheets: Finally, the enriched and processed data is appended as a new row in a specified Google Sheet, providing a centralized record of all form submissions and their enhanced details.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Google Sheets Account: Access to a Google Sheets account and a specific spreadsheet where data will be stored.
- OpenAI API Key: An OpenAI API key with access to the models you intend to use for data enrichment.
- External API Endpoint: If the HTTP Request node is configured to send data, you will need the URL and any necessary authentication for that external API.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the copied JSON.
- Configure Credentials:
- Google Sheets: Configure your Google Sheets credential. You'll need to authenticate your Google account and grant n8n access to your spreadsheets.
- OpenAI: Set up your OpenAI credential by providing your API key.
- Configure Nodes:
- n8n Form Trigger: Design your form fields within this node to match the data you expect to receive.
- OpenAI: Adjust the OpenAI node's configuration (e.g., model, prompt) to perform the desired data enrichment based on your form submission data.
- Code: Review and modify the JavaScript code within the "Code" node to ensure it correctly transforms your data as needed.
- HTTP Request: Configure the URL, method (GET, POST, PUT, etc.), headers, and body for your external API call.
- Google Sheets: Specify the Google Sheet ID and the sheet name where you want to append the data. Map the input fields from the previous nodes to the columns in your Google Sheet.
- Activate the Workflow: Once all configurations are complete, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
Now, every time your n8n form is submitted, the workflow will automatically process the data, enrich it with OpenAI, potentially send it to an external API, and log it in your Google Sheet.
Related Templates
AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp
This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The βvirtual executive team,β is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier π― Core Features π§βπΌ 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. π 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. π΅οΈββοΈ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. β° 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline β key traits for early-stage success. ποΈ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. π¬ WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. βοΈ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. π§© Integrations Required Gemini API β for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API β for business and competitor analysis SerpAPI β for market research and opportunity scouting Google OAuth β to connect Sheets, Calendar, and Gmail WhatsApp Business API β for message triggers and responses π Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. π§° Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startupβs needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you π‘ Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business
π How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From β senderβs email address To β recipientβs email address Subject β email subject line Summary β short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits β Full Automation: Eliminates manual reading and data entry from incoming emails. β Multi-Source Integration: Handles data from different email providers seamlessly. β AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. β Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. β Time Efficiency: Processes emails in real time, improving productivity and response speed. *β Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.
Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API
Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. Itβs designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this β€ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait 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) 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. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. 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