Automated Email Sending & Lead Status Tracking with n8n

Built with n8n
1

Recently, I built an n8n workflow to automate outbound email handling and lead status tracking, making the process fully streamlined from trigger to CRM update.

The goal was to manage multiple email sends, track their status, and handle replies without manual intervention.

:puzzle_piece: Workflow Overview

The workflow starts with a webhook trigger and routes leads based on conditions. Depending on the scenario, it updates lead records, sends emails via API, and responds back through webhooks.

It also handles cases where a lead replies, updating the CRM accordingly.

:gear: How It Works

1. Webhook Trigger
The flow starts when data is received via webhook.

2. Conditional Check (If Node)
Determines whether the lead should go through the email flow or reply handling.

:outbox_tray: Email Sending Flow

3. Switch Node (Rules-based Routing)
Routes leads into multiple paths depending on logic (e.g., email sequence stage).

4. Update Lead Record
Marks the lead with the correct email stage (Sent, Sent1, Sent2, etc.).

5. Send Email (HTTP Request)
Calls an external API (e.g., Instantly or similar) to send emails.

6. Respond to Webhook
Confirms execution back to the source system.

:inbox_tray: Reply Handling Flow

7. Detect Reply Condition (If Node)
Checks if the lead has responded.

8. Update Lead Status
Marks lead as “Replied” in CRM.

9. Respond to Webhook
Sends confirmation after updating status.

:light_bulb: What This Solves

Managing outbound emails manually is:
Time-consuming
Hard to track
Error-prone

This automation:
:check_mark: Handles multi-step email sequences
:check_mark: Tracks email status inside CRM
:check_mark: Sends emails via API automatically
:check_mark: Updates leads when replies are received

:high_voltage: Key Learning

Using a Switch node for sequence management makes it easy to scale email flows.

Instead of building separate workflows:
:backhand_index_pointing_right: One system handles multiple stages
:backhand_index_pointing_right: Clean routing keeps logic maintainable

:brain: Tech Stack

n8n for orchestration
CRM (Airtable or similar) for lead tracking
Email API (Instantly or similar) for sending emails
Webhooks for real-time triggers

:pushpin: Final Thought

This setup creates a solid base for a fully automated outbound system.

You can extend it further with:
AI-based personalization
Follow-up optimization
Lead scoring before sending

n.07
n.071005Ă—756 167 KB

1 Like
2

This is a super clean architecture. Using a Switch node for sequence routing instead of a spaghetti of IF nodes or separate workflows is definitely the right way to scale these out.

Since this handles live lead gen and relies on external APIs like Instantly, how are you dealing with monitoring and silent failures? In my experience with cold outreach flows, the biggest headache is when an HTTP request fails quietly (like a rate limit or API hiccup) or a webhook payload drops. The workflow might just stop without throwing a hard platform error, and suddenly leads are sitting in the wrong stage for days.

Do you have an error route pushing these silent drops to a Slack/Telegram channel, or are you just relying on the built-in execution logs for now?

3

This is really well structured! :clap:

The Switch node idea for managing email sequence stages is smart — never thought of using it that way. Usually I see people building separate workflows for each stage which becomes a mess to maintain.

One thing I’m curious about — when a lead replies, how do you detect that in real time? Does the email API (like Instantly) send a webhook back to n8n, or are you polling for replies on a schedule?

Would love to see the actual workflow JSON if you’re willing to share!