This article provides a complete, practical walkthrough of the Code Filter Create Scheduled n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Sure! Here's a short article based on your n8n workflow along with the requested metadata elements:
   
   ---
   
   Title:  
   Automated Email Campaigns with n8n: Sending Smart Sequences and Timely Follow-Ups  
   
   Meta Description:  
   Learn how to build a fully automated cold email workflow in n8n using Gmail and Google Sheets. This setup manages first contact, follow-ups, personalization, and detects replies to stop messaging.  
   
   Keywords:  
   n8n, email automation, Gmail API, Google Sheets API, cold outreach, follow-up emails, workflow automation, personalized messaging, sales emails, email sequences  
   
   Third-Party APIs Used:
   
   - Gmail API (via OAuth2) – For sending emails, retrieving threads, and replying.
   - Google Sheets API (via OAuth2) – For reading and updating a contact list.
   
   Article:
   
   Automated Email Campaigns with n8n: Sending Smart Sequences and Timely Follow-Ups
   
   Outreach is essential—whether you’re nurturing leads, booking sales calls, or conducting customer research. But where many efforts fail is in consistency. That’s where this n8n workflow comes in: designed to automate initial cold outreach as well as timed, intelligent follow-ups—all without messaging someone who’s already replied.
   
   Let’s explore how this sophisticated workflow works and how it leverages email sequencing, contact tracking, and intelligent filters to power your campaign reliably.
   
   🛠 Overview
   
   At the heart of this workflow are two main data sources:
   
   - A Google Sheet with contact records (name, email, company, etc.). 
   - A Gmail account that sends and manages these messages.
   
   It’s broken down into three main sections:
   
   1. Initial Email Dispatch
   2. Follow-Up Detection and Logic
   3. Sub-workflow to Send the Email
   
   The entire system is triggered hourly, but is sensitive to business timing—it will never send emails during weekends.
   
   📤 Sending Initial Emails
   
   Every hour, the workflow checks a Google Sheet for new contacts that haven’t yet been emailed. When it finds someone with an empty “first_emailed” field, it prepares the first email using a defined sequence and template.
   
   These templates include placeholders (e.g., {name} or {company}) pulled from each row. If a placeholder used in the email has no corresponding column in the sheet, the workflow throws an error to prevent inaccurate or awkward messages.
   
   After personalization, the message is sent using Gmail. The system logs the first contact date back into the spreadsheet.
   
   🔁 Follow-Up Emails: Smart and Respectful
   
   Once follow-ups begin, timing and logic are key:
   
   - The system looks up prior message threads matching the campaign’s subject.
   - It checks whether the full sequence of previous messages was sent.
   - If someone has replied, no more emails are sent—that lead is already warm.
   - If no reply is found, and enough days have passed, the next email is prepared.
   - It even extracts the exact data used in the previous emails, using embedded HTML metadata, ensuring consistent personalization across messages.
   
   Only when all conditions are met is the next message in the sequence sent—either as a new thread or a reply to the original message. This ensures you're not simply spamming inboxes, but offering timely nudges that maintain context.
   
   🔂 Sub-Workflow: Modular and Clean Execution
   
   Rather than duplicating logic across the original contacts and replies flows, the workflow invokes a sub-workflow responsible for:
   
   - Filling in message placeholders
   - Constructing the HTML with metadata
   - Deciding whether it’s a new message or reply
   - Sending the email with Gmail
   - Finally, updating the “first_emailed” field on first contact
   
   This design pattern keeps things modular, maintainable, and easier to test.
   
   ✅ Key Workflow Features
   
   - Skip weekends: Emails are only sent on weekdays.
   - Email throttling: Triggered once per hour to avoid burst-sending.
   - Placeholder validation: Prevents emails from being sent with missing dynamic content.
   - Reply detection: Stops the sequence automatically if an actual human response is received.
   - Metadata tracking: Every email embeds campaign details hidden in HTML—useful for later analytics or reprocessing.
   
   📈 Use Cases
   
   This workflow is great for:
   
   - Sales teams needing a reliable top-of-funnel outreach solution
   - Recruiters reaching out to passive candidates
   - Founders validating a product idea
   - Nonprofits seeking partnerships or donor engagement
   
   🔧 Getting Started
   
   To try it out:
   
   1. Clone the Google Sheet template mentioned in the workflow.
   2. Input your contact details, ensuring columns match the placeholders used in your email templates.
   3. Adjust the "Email Sequence" node to define your message flow and delay timings (via send_on_day).
   4. Deploy the workflow on an hourly schedule—then watch it work.
   
   Conclusion
   
   This n8n email campaign workflow combines flexibility, thoughtful sequencing, and solid user context to take the heavy lifting out of follow-ups. By using built-in nodes for Gmail and Google Sheets, and wrapping logic with intelligent filters and metadata tracking, you have a low-code, high-impact solution for smarter email automation.
   
   Stay timely, stay personal—and let n8n help you scale your outreach with confidence.
   
   ---
   
   Let me know if you’d like a visual diagram, deployment guide, or customization options for this workflow.

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.