Back to Catalog

Automated cold email campaigns with random templates & Google Sheets tracking

Anir AgramAnir Agram
731 views
2/3/2026
Official Page

πŸ“Š Google Sheets Leads β†’ 🎲 Random Templates β†’ βœ‰οΈ Personalized Emails β†’ πŸ“ Status Tracking

What this workflow does

  • πŸ“Š Reads leads list from Google Sheets (Name, Email, Send Status)
  • πŸ” Filters out already-contacted leads (skips "SENT" status)
  • 🎲 Randomly selects email template from template library
  • ✏️ Personalizes subject and body with lead's name
  • πŸ“§ Sends emails one-by-one with delays between sends
  • βœ… Updates Google Sheet with send status and timestamp
  • πŸ” Loops through all unsent leads automatically

Why it's useful

  • ⚑ Automate cold outreach without manual copy-paste
  • 🎯 Avoid duplicate sendsβ€”tracks who's been contacted
  • πŸ“ Rotate email templates for A/B testing and variety
  • πŸ‘€ Personalization makes emails feel human, not spammy
  • ⏱️ Built-in delays prevent spam flags and rate limits
  • πŸ“Š Full audit trail of who received what and when

How it works

  • πŸ“Š Google Sheets (Leads) β†’ reads Name, Email, Send Status
  • 🚦 IF Node β†’ filters leads where Send Status β‰  "SENT"
  • πŸ”„ Loop Over Items β†’ processes leads one-by-one
  • πŸ“§ Google Sheets (Templates) β†’ fetches Subject + Body templates
  • 🎲 Code Node β†’ picks random template
  • πŸ”€ Merge β†’ combines lead data with template
  • ✏️ Edit Fields β†’ replaces [Name] with actual lead name
  • πŸ“¨ Send Email β†’ delivers personalized message
  • ⏳ Wait β†’ adds delay between sends (avoids spam flags)
  • βœ… Google Sheets (Update) β†’ marks as "SENT" with timestamp

What you'll need

  • πŸ“Š Google Sheet #1: Leads (columns: Name, Email, Send Status, Time)
  • πŸ“§ Google Sheet #2: Templates (columns: Subject, Body)
  • πŸ“¬ SMTP credentials (SendGrid, Mailgun, etc.)
  • πŸ” Google Sheets OAuth

Setup steps

  • πŸ“Š Create "Leads" sheet with columns: Name | Email | Send Status | Time
  • πŸ“§ Create "Templates" sheet with columns: Subject | Body (use [Name] placeholder)
  • πŸ”— Connect Google Sheets OAuth credentials
  • πŸ“¬ Add SMTP email credentials
  • 🧭 Update both Google Sheets node IDs to point to your sheets
  • βš™οΈ Set "From Email" in Send Email node
  • πŸ§ͺ Test with 2-3 test leads first

Customization ideas

  • ⏱️ Adjust Wait time (30s-5min) to control send rate
  • πŸ“Š Add click tracking with UTM parameters
  • πŸ”” Send Slack/Telegram notification when campaign completes
  • 🎯 Add lead scoringβ€”prioritize high-value leads first
  • πŸ“ˆ Log opens/replies to separate tracking sheet

Who it's for

  • πŸ§‘β€πŸ’» Freelancers doing cold outreach to agencies
  • πŸ“ˆ Sales teams running lead generation campaigns
  • πŸš€ Startups reaching out to potential customers
  • 🎯 Marketers testing email copy variations
  • πŸ’Ό Business developers nurturing prospect lists

Quick Setup Guide

  • Before You Start - What You Need: πŸ“Š Google account for Sheets access
  • πŸ“§ SMTP email account (Gmail, custom domain, or email service)
  • πŸ“ List of leads (names + emails)
  • βœ‰οΈ Email templates ready (with [Name] placeholders)

Want help customizing?

πŸ“§ anirpoke@gmail.com πŸ”— LinkedIn

Automated Cold Email Campaigns with Random Templates and Google Sheets Tracking

This n8n workflow automates the process of sending cold emails, incorporating random email templates and tracking the campaign's progress in Google Sheets. It's designed to streamline outreach efforts and add a layer of personalization through template variation.

What it does

This workflow simplifies and automates your cold email outreach by:

  1. Triggering Manually: The workflow is initiated manually, allowing you to control when a batch of emails is sent.
  2. Fetching Data from Google Sheets: It reads contact information and email template details from a Google Sheet.
  3. Looping Over Contacts: It processes each contact individually, ensuring personalized emails.
  4. Selecting Random Email Template: For each contact, it dynamically selects a random email template from the available options.
  5. Composing and Sending Emails: It constructs the email using the contact's data and the chosen template, then sends it via an SMTP server.
  6. Updating Google Sheets: After sending an email, it updates the Google Sheet to track which template was used and when the email was sent, preventing duplicate outreach to the same contact.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Sheets Account: A Google account with access to Google Sheets. You'll need a spreadsheet containing your contact list (e.g., Name, Email, Company, etc.) and a separate sheet or section for your email templates.
  • SMTP Credentials: Access to an SMTP server for sending emails (e.g., Gmail, Outlook, SendGrid, Mailgun, etc.). You'll need the host, port, username, and password.

Setup/Usage

  1. Import the Workflow:

    • Copy the provided JSON code.
    • In your n8n instance, click "New" in the workflows section.
    • Click the three dots in the top right corner and select "Import from JSON".
    • Paste the JSON code and click "Import".
  2. Configure Credentials:

    • Google Sheets Node: Click on the "Google Sheets" node. You will need to set up a Google Sheets credential. Follow the n8n documentation for connecting your Google account. Ensure the account has read/write access to your campaign spreadsheet.
    • Send Email Node: Click on the "Send Email" node. You will need to configure an SMTP credential. Provide your SMTP host, port, username, password, and sender email address.
  3. Customize Google Sheet Details:

    • Google Sheets (Read): In the Google Sheets node that reads data, specify the "Spreadsheet ID" and "Sheet Name" where your contact list and templates are located.
    • Google Sheets (Update): In the Google Sheets node that updates data, specify the "Spreadsheet ID" and "Sheet Name" for tracking.
  4. Customize Email Templates and Logic:

    • Code Node: The "Code" node is likely where the logic for selecting a random template and constructing the email body/subject resides. Review and adjust the JavaScript code within this node to match your specific template structure and personalization fields.
    • Edit Fields Node: The "Edit Fields" (Set) node is used to prepare the data for the email. Ensure the fields being set (e.g., toEmail, subject, body) correctly map to your Google Sheet columns and the output of the Code node.
    • If Node: The "If" node likely contains logic to determine if an email should be sent (e.g., if a contact hasn't been emailed yet). Adjust its conditions as needed.
  5. Activate and Execute:

    • Once all credentials and configurations are set, save the workflow.
    • Click "Activate" to enable the workflow.
    • To run the campaign, click the "Execute Workflow" button on the "Manual Trigger" node.

Remember to test the workflow with a small subset of data first to ensure everything is configured correctly before running a large campaign.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch πŸ”— LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247