Automate lead generation with Apollo, AI parsing, and timed email follow-ups
Good to know:
- The workflow runs every hour with a randomized delay of 5–20 minutes to help distribute load.
- It records the exact date and time a lead is emailed so you can track outreach.
- Follow-ups are automatically scheduled two days after the initial email.
How it works:
- After apify completes, the JSON data is retrieved and inserted into the proper JSON node (only the JSON is removed — nothing else).
- The agent then runs on its own, parsing the data and pushing it to Google Sheets.
- When a lead is emailed, the system tags it with the date and time for tracking.
- Two days later the workflow automatically triggers a follow-up, again on an hourly schedule with the same time delay.
How to use:
- Start by connecting your apify account to retrieve data.
- Place the returned JSON into the designated JSON node.
- Configure your Google Sheet where the data will be stored.
- Adjust the time delay window or follow-up period if needed.
- Insert your email credentials and the message.
Requirements:
- Apify account with active leads/data.
- Google Sheet for storing and managing parsed lead information.
- n8n credentials configured for your accounts.
- email credentials
Customising this workflow:
You can easily extend this template to include other CRMs, different time delays, or additional notification steps. For example, push new leads to Slack, send SMS notifications, or trigger downstream analytics dashboards automatically.
n8n Apollo AI Lead Generation and Timed Follow-ups Workflow
This n8n workflow automates the process of generating leads using Apollo.io, enriching lead data with AI parsing, and sending timed email follow-ups via Gmail. It's designed to streamline your outreach efforts and ensure consistent engagement with potential leads.
What it does
This workflow performs the following key steps:
- Triggers on Demand or Schedule: The workflow can be manually triggered or run on a predefined schedule.
- Fetches Leads from Google Sheets: It reads lead data from a specified Google Sheet, acting as the primary source for lead information.
- Iterates Through Leads: Each lead from the Google Sheet is processed individually.
- Enriches Lead Data with Apollo.io: For each lead, it makes an HTTP request to Apollo.io to retrieve additional details, likely company or contact information.
- Parses Data with AI Agent: An AI Agent (likely powered by OpenAI) analyzes the data obtained from Apollo.io to extract and structure relevant information, such as contact details, company insights, or personalized talking points.
- Structures AI Output: The AI's parsed output is then structured using a Structured Output Parser, ensuring consistency and usability for subsequent steps.
- Saves Parsed Data to Google Sheets: The enriched and AI-parsed lead data is written back to a Google Sheet, updating the lead records with valuable insights.
- Sends Initial Follow-up Email: An initial personalized email is sent to the lead via Gmail, incorporating the AI-parsed insights.
- Waits for 3 Days: The workflow pauses for 3 days to allow time for the lead to respond to the initial email.
- Checks for Response: After the waiting period, it checks if the lead has responded to the email using an "If" condition.
- Sends Second Follow-up (If No Response): If no response is detected, a second follow-up email is sent via Gmail.
- Waits for 7 Days: The workflow then waits for another 7 days.
- Sends Third Follow-up (If No Response): If still no response, a third and final follow-up email is sent via Gmail.
- Limits Processing (Optional): A "Limit" node is present, which could be used to restrict the number of leads processed in a single run, useful for testing or managing API quotas.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Google Account: With access to Google Sheets for storing and retrieving lead data.
- Apollo.io Account: For lead enrichment via its API.
- OpenAI Account: An OpenAI API key for the AI Agent and Chat Model nodes.
- Gmail Account: Configured as a credential in n8n for sending emails.
- n8n Credentials: Appropriate n8n credentials configured for Google Sheets, HTTP Request (for Apollo.io), OpenAI, and Gmail.
Setup/Usage
- Import the workflow: Download the JSON file and import it into your n8n instance.
- Configure Credentials:
- Set up your Google Sheets credentials.
- Set up your HTTP Request credentials for Apollo.io (API key/authentication).
- Set up your OpenAI credentials (API key).
- Set up your Gmail credentials.
- Update Google Sheet IDs:
- In the "Google Sheets" nodes, update the Spreadsheet ID and Sheet Name to point to your lead data sheet.
- Ensure your Google Sheet has columns for lead names, email addresses, and any other data you wish to enrich or use in emails.
- Configure Apollo.io HTTP Request: Adjust the URL and body of the "HTTP Request" node to match the Apollo.io API endpoint and parameters for lead enrichment.
- Customize AI Agent and Chat Model:
- Review and adjust the prompts and configurations in the "AI Agent" and "OpenAI Chat Model" nodes to ensure they extract and parse the desired information accurately from the Apollo.io response.
- Modify the "Structured Output Parser" schema to match the expected output structure from your AI agent.
- Customize Email Content:
- Edit the "Gmail" nodes to personalize the subject lines and body content of your follow-up emails.
- Utilize expressions to dynamically insert lead data and AI-parsed insights into your emails.
- Adjust Wait Times: Modify the duration in the "Wait" nodes if you want to change the timing of the follow-up emails.
- Activate the workflow: Once configured, activate the workflow. You can trigger it manually using "When clicking 'Execute workflow'" or set up a schedule using "Schedule Trigger".
Related Templates
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements 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) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | 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. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. 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
Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.