Generate personalized cold emails with Anthropic, GPT-4 & Google Sheets
Your Cold Email is Now Researched. This pipeline finds specific bottlenecks on prospect websites and instantly crafts an irresistible pitch
π― Problem Statement
Traditional high-volume cold email outreach is stuck on generic personalization (e.g., "Love your website!"). Sales teams, especially those selling high-value AI Receptionists, struggle to efficiently find the one Unique Operational Hook (like manual scheduling dependency or high call volume) needed to make the pitch relevant. This forces reliance on expensive, slow manual research, leading to low reply rates and inefficient spending on bulk outreach tools.
β¨ Solution
This workflow deploys a resilient Dual-AI Personalization Pipeline that runs on a batch basis. It uses the Filter (Qualified Leads) node as a cost-saving Quality Gate to prevent processing bad leads. It executes a Targeted Deep Dive on successful leads, using GPT-4 for analytical insight extraction and Claude Sonnet for coherent, human-like copy generation. The entire process outputs campaign-ready data directly to Google Sheets and sends a critical QA Draft via Gmail.
βοΈ How It Works (Multi-Step Execution)
1. Ingestion and Cost Control (The Quality Gate)
-
Trigger and Ingestion: The workflow starts via a Manual Trigger, pulling leads directly from Get All Leads (Google Sheets).
-
Cost Filtering: The Filter (Qualified Leads) node removes leads that lack a working email or website URL.
-
Execution Isolation: The Loop Over Leads node initiates individual processing. The Capture Lead Data (Set) node immediately captures and locks down the original lead context for stability throughout the loop.
-
Hybrid Scraping: The Scrape Site (HTTP Request) and Extract Text & Links (HTML) nodes execute the Hybrid Scraping strategy, simultaneously capturing website text and external links.
-
Data Shaping & Status: The Filter Social & Status (Code) node is the control center. It filters links, bundles the context, and critically, assigns a status of 'Success' or 'Scrape Fail'.
-
Cost Control Branch: The If (IF node) checks this status. Items with 'Scrape Fail' bypass all AI steps (saving 100% of AI token costs) and jump directly to Log Final Result. Successful items proceed to the AI core.
2. Dual-AI Coherence & Dispatch (The Executive Output)
-
Analytical Synthesis: The Summarize Website (OpenAI) node uses GPT-4 to synthesize the full context and extract the Unique Operational Hook (e.g., manual booking overhead).
-
Coherent Copy Generation: The Generate Subject & Body (Anthropic) node uses the Claude Sonnet model to generate the subject and the multi-line body, guaranteeing coherence by creating both simultaneously in a single JSON output.
-
Final Parsing: The Parse AI Output (Code) node reliably strips markdown wrappers and extracts the clean subject and body strings.
-
Final Delivery: The data is logged via Log Final Result (Google Sheets), and the completed email is sent to the user via Create a draft (Gmail) for final Quality Assurance before sending.
π οΈ Setup Steps
Before running the workflow, ensure these credentials and data structures are correctly configured:
Credentials
-
Anthropic: Configure credentials for the Language Model (Claude Sonnet).
-
OpenAI: Configure credentials for the Analytical Model (GPT-4/GPT-4o).
-
Google Services: Set up OAuth2 credentials for Google Sheets (Input/Output) and Gmail (Draft QA and Completion Alert).
Configuration
-
Google Sheet Setup: Your input sheet must include the columns email, website_url, and an empty Icebreaker column for initial filtering.
-
HTTP URL: Verify that the Scrape Site node's URL parameter is set to pull the website URL from the stabilized data structure: ={{ $json.website_url }}.
-
AI Prompts: Ensure the Anthropic prompt contains your current Irresistible Sales Offer and the required nested JSON output structure.
β Benefits
-
Coherence Guarantee: A single Anthropic node generates both the subject and body, guaranteeing the message is perfectly aligned and hits the same unique insight.
-
Maximum Cost Control: The IF node prevents spending tokens on bad or broken websites, making the campaign highly budget-efficient.
-
Deep Personalization: Combines website text and social media links, creating an icebreaker that implies thorough, manual research.
-
High Reliability: Uses robust Code nodes for data structuring and parsing, ensuring the workflow runs consistently under real-world conditions without crashing.
-
Zero-Risk QA: The final Gmail (Create a draft) step ensures human review of the generated copy before any cold emails are sent out.
Generate Personalized Cold Emails with Anthropic/GPT-4 & Google Sheets
This n8n workflow automates the creation and optional sending of highly personalized cold emails. It leverages data from a Google Sheet, uses either Anthropic's Claude or OpenAI's GPT-4 to generate tailored email content, and then updates the Google Sheet with the generated email. Optionally, it can also send these emails via Gmail.
What it does
- Triggers Manually: The workflow is initiated manually, allowing you to control when the email generation process begins.
- Retrieves Data from Google Sheets: It fetches a list of recipients from a specified Google Sheet, specifically looking for rows where the "Email Sent" column is empty.
- Loops Over Items: For each qualifying recipient, the workflow processes their data individually.
- Prepares Data: It sets up the necessary data fields for email generation, including the recipient's name, company, and any other relevant information from the Google Sheet.
- Generates Personalized Email (Anthropic/OpenAI):
- It uses a "Code" node to dynamically construct a prompt for the AI model, incorporating details from the recipient's row.
- It then sends this prompt to either an Anthropic (Claude) or OpenAI (GPT-4) node to generate a personalized cold email draft.
- Extracts Email Content: An "HTML" node is used to extract the plain text email content from the AI's response, ensuring it's clean and ready for use.
- Filters for Valid Emails: It checks if an email was successfully generated by the AI.
- Updates Google Sheet:
- If an email was generated, it updates the original Google Sheet row with the generated email content and marks the "Email Sent" column as "Generated".
- Sends Email (Optional):
- An "If" node checks a condition (e.g., if the "Email Sent" column is "Generated").
- If the condition is met, the workflow sends the personalized email to the recipient via Gmail.
- After sending, it updates the Google Sheet again, marking the "Email Sent" column as "Sent".
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Google Sheets Account: With a spreadsheet containing recipient data (e.g., Name, Company, Email, Email Sent column).
- Anthropic API Key OR OpenAI API Key: For generating email content. You will need to configure credentials for either the Anthropic or OpenAI node.
- Gmail Account: For sending the personalized emails. You will need to configure credentials for the Gmail node.
Setup/Usage
- Import the workflow: Download the JSON provided and import it into your n8n instance.
- Configure Credentials:
- Google Sheets: Set up your Google Sheets credentials to allow n8n to read and write to your spreadsheet.
- Anthropic/OpenAI: Configure your API key for either the Anthropic or OpenAI node, depending on which AI model you choose to use.
- Gmail: Set up your Gmail credentials to allow n8n to send emails on your behalf.
- Configure Google Sheets Node (ID: 18):
- Specify the Spreadsheet ID and Sheet Name where your recipient data is located.
- Ensure the "Email Sent" column exists in your sheet and is initially empty for new recipients.
- Configure AI Node (Anthropic ID: 1312 or OpenAI ID: 1250):
- Review the "Code" node (ID: 834) preceding the AI node to understand the prompt structure. Adjust the prompt as needed to generate the desired email style and content.
- Select your preferred AI model (Anthropic or OpenAI) and ensure its credentials are set up.
- Configure Gmail Node (ID: 356):
- Set the "To" field to dynamically pull the recipient's email address from the Google Sheet data.
- Set the "Subject" and "Body" fields to use the generated email content.
- Activate the workflow: Once configured, activate the workflow.
- Execute Manually: Click "Execute workflow" in the Manual Trigger node to start the process. The workflow will then iterate through your Google Sheet and generate/send emails.
Important Notes:
- Testing: It is highly recommended to test the workflow with a small subset of data and with the Gmail "Send" action disabled initially to ensure the email generation and Google Sheet updates work as expected before sending actual emails.
- Rate Limits: Be mindful of API rate limits for Anthropic, OpenAI, and Gmail.
- Prompt Engineering: The quality of the generated emails heavily depends on the prompt provided to the AI model. Experiment with different prompts in the "Code" node to achieve optimal results.
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.