How to Automate Email Marketing with n8n in 2026 (No Per-Email Fees)

How to Automate Email Marketing with n8n in 2026 (No Per-Email Fees)

Most email marketing platforms charge you the same way: a flat monthly fee that scales with your list size, or a per-email fee that grows as your volume grows. At small scale, it's fine. At medium scale, you're paying $200–$400/month for sequences a spreadsheet and a few API calls could handle.

n8n is the escape hatch. It's an open-source workflow automation platform that connects to any email service (Resend, Mailgun, AWS SES, Postmark, even Gmail), runs on your own server, and charges nothing per workflow execution. You pay once for a VPS — typically $5–$20/month — and automate unlimited sends.

This guide walks through the exact workflows to build, what each one does, and how to wire them up in n8n.

Why n8n for Email Marketing?

The standard objection to self-hosted email automation is complexity. It's valid — but the tradeoff makes sense for specific situations:

n8n is the right choice when:

• You're sending high volume (10,000+ emails/month) and per-email costs are adding up
• You need custom logic that Mailchimp or Klaviyo can't handle (conditional branching, multi-source triggers, API lookups mid-sequence)
• You want email automation as one step in a larger workflow that also updates a CRM, logs to a database, or fires a Slack alert
• You're already self-hosting n8n for other workflows and want to consolidate

n8n is the wrong choice when:

• You need a drag-and-drop email builder with pre-built templates
• Your team is non-technical and needs to edit sequences without touching code
• You're doing list-based broadcast campaigns to 100,000+ subscribers (use a dedicated ESP)

If you're a small business owner or agency running automation workflows already, this is your next unlock.

Setup: What You Need Before Building

1. A Running n8n Instance

You need n8n running somewhere accessible. Options:

• Self-hosted on a VPS (DigitalOcean, Vultr, Hetzner) — $5–$20/month, most flexibility
• n8n Cloud — starts at $20/month, managed, no server maintenance (n8n.io)
• Docker on your local machine — good for testing, not for production

If you're already running n8n for other workflows, you're ready. If not, the n8n quickstart guide gets you running in under 30 minutes via Docker.

2. A Transactional Email Provider

n8n doesn't deliver email — it orchestrates it. You need an email provider with an API:

For most small businesses: Resend is the fastest to set up and has excellent deliverability. Get an API key, verify your domain, and you're ready.

3. A Data Source

Your email workflows need to know who to email and when. Common sources in n8n:

• Webhook — a form submission, purchase event, or sign-up fires a POST to your n8n webhook URL
• Database — n8n queries Postgres, MySQL, Supabase, or Airtable on a schedule
• CRM — HubSpot, Pipedrive, or Close CRM record changes trigger the workflow
• Google Sheets — for the simplest setups, a sheet is your list

The 6 Email Marketing Workflows to Build

Workflow 1: Welcome Sequence (New Subscriber → 3-Email Flow)

What it does: When someone joins your list (via form, checkout, or API), they get a timed 3-email welcome sequence: an immediate welcome email, a day-2 value email, and a day-5 offer email.

Why this matters: Welcome sequences generate 4x higher open rates than regular campaigns. Most businesses skip them because setting up timed sequences in code feels hard. In n8n, it's a visual flow.

How to build it:

1. Trigger: Webhook node — Create a webhook URL in n8n. Point your signup form's POST to this URL. The payload should include email, first_name, and optionally source.

2. Immediately: Send Email node — Use your email provider's node (or the HTTP Request node with Resend's API). Send your welcome email. HTML template lives in the node directly.

3. Wait 2 days: Wait node — Set to 2 days. This is n8n's built-in delay. No cron job needed.

4. Day 2 email: Send Email node — Second email in sequence. Link to your best content or a case study.

5. Wait 3 more days: Wait node — Set to 3 days.

6. Day 5 email: Send Email node — Your first offer. A product recommendation, a discount, or a call to book.

n8n tip: Add an IF node before each email that checks "is this contact still subscribed?" Query your database or CRM. If they've unsubscribed, end the flow there.

Workflow 2: Abandoned Cart Recovery

What it does: When a customer adds to cart but doesn't complete checkout, they get 2 follow-up emails: one at 1 hour, one at 24 hours.

How to build it:

1. Trigger: Webhook — Your e-commerce platform (Shopify, WooCommerce, or custom) fires a webhook when a cart is created. Include cart contents, email, and cart ID.

2. Store in Database node — Save the cart data to Postgres or Airtable with a completed: false flag and a timestamp.

3. Wait 1 hour: Wait node

4. Check if purchased: HTTP Request node — Query your order database or Shopify API: did this customer complete a purchase after the cart was created?

5. IF not purchased: Send Email node — Abandoned cart email #1. Include the cart contents (pulled from your saved data). Add a link back to the cart.

6. Wait 23 hours: Wait node (total 24 hours from abandon)

7. Check if purchased again: HTTP Request node

8. IF still not purchased: Send Email node — Abandoned cart email #2. Urgency angle, or a small discount code.

Revenue impact: Even at a 5% recovery rate, this workflow earns real money on autopilot.

Workflow 3: Post-Purchase Follow-Up + Upsell

What it does: After a purchase, trigger a 3-step sequence: order confirmation, day-3 check-in, day-7 upsell.

How to build it:

1. Trigger: Webhook — Shopify, Stripe, or WooCommerce fires a payment_intent.succeeded or order.created webhook.

2. Immediately: Send Email node — Order confirmation. Pull order details from the webhook payload.

3. Wait 3 days: Wait node

4. Day 3: Send Email node — Check-in. "How's it going with [product]?" Light, genuine. Builds relationship.

5. Wait 4 more days: Wait node

6. Day 7: Send Email node — Upsell. Recommend a complementary product. Link to your store.

n8n tip: Before the upsell email, add an HTTP Request node that checks if they've already bought the upsell product. If yes, skip to an alternate email suggesting something else.

Workflow 4: Re-engagement / Win-Back Campaign

What it does: Automatically finds subscribers who haven't opened an email in 90 days and runs them through a 3-email win-back sequence.

How to build it:

1. Trigger: Schedule node — Run every Monday morning.

2. Query Database node — Pull contacts where last_opened_at < NOW() - INTERVAL '90 days' AND subscribed = true AND win_back_sent IS NULL.

3. Split In Batches node — Process 50 contacts at a time to stay within email API rate limits.

4. Send Email node — Win-back email #1: "We miss you. Here's what's new."

5. Update Record node — Set win_back_sent_at = NOW() in your database.

6. Wait 5 days: Wait node

7. Check if opened: HTTP Request node — Query your email provider's API for open events. Resend, Mailgun, and SendGrid all have event APIs.

8. IF not opened: Send Email node — Win-back email #2. Different subject line, sharper hook.

9. IF still not opened after 5 more days: Mark as inactive — Update record. Remove from active list. This protects your sender reputation.

Sender reputation note: Emailing unengaged subscribers tanks your deliverability. This workflow cleans your list automatically — which actually improves performance on your engaged contacts.

Workflow 5: Lead Nurture Sequence (B2B / Service Businesses)

What it does: When a lead downloads a resource or books a call, they enter a 5-touch sequence over 2 weeks that builds trust before a sales ask.

How to build it:

1. Trigger: Webhook — Lead magnet download form or Cal.com/Calendly webhook.

2. CRM Lookup: HTTP Request node — Check if this contact already exists in your CRM (HubSpot, Pipedrive). If yes, update their record. If no, create one.

3. Immediately: Send Email node — Deliver the lead magnet or confirm the call. Set expectations for what's coming.

4. Day 2: Send Email node — Educational email. Solve one specific problem. No pitch.

5. Day 5: Send Email node — Case study or social proof. Real outcome, real numbers.

6. Day 9: Send Email node — FAQ or objection handler. Address the top 3 reasons people don't buy.

7. Day 14: Send Email node — Direct ask. Book a call, start a trial, or make an offer.

n8n tip: Add a branch at each step that checks if the lead has already converted (booked, purchased, or replied). If yes, exit the sequence and trigger a different workflow for active prospects.

Workflow 6: Behavior-Triggered Emails (Advanced)

What it does: Send emails based on specific actions — like visiting a pricing page, clicking a specific link, or reaching a usage milestone in your app.

How to build it:

1. Trigger: Webhook — Your website or app POSTs to n8n when a tracked event occurs. Use a JS snippet or your analytics platform (Segment, PostHog, Mixpanel all support webhook destinations).

2. Route by Event Type: Switch node — Pricing page visit goes to a nurture email. Link click on feature X goes to a feature education email. Trial day 3 goes to a milestone email.

3. Send Email node — Contextual email matched to the behavior. These emails feel personal because they're triggered by what the person just did.

Why this works: Behavior-triggered emails have 2-3x higher conversion rates than time-based sequences because the message matches the person's current intent.

Handling Unsubscribes

This is non-negotiable. Every email you send must have a working unsubscribe link and must honor opt-outs immediately.

In n8n:

1. Create a webhook endpoint that receives unsubscribe requests (your email footer links to https://your-n8n.com/webhook/unsubscribe?email=EMAIL).

2. The webhook workflow updates your database: set subscribed = false, unsubscribed_at = NOW().

3. Before every email node in every workflow, add an IF node that checks the subscribed flag. If false, end the workflow.

4. For the unsubscribe confirmation, send one final "You've been removed" email using your transactional provider.

This is not optional. CAN-SPAM and GDPR require it, and your email deliverability depends on honoring opt-outs immediately.

Email Templates in n8n

n8n doesn't have a drag-and-drop email builder. Your templates live in the workflow nodes as HTML strings. This is either a feature or a bug depending on your skills.

Best practice: Keep templates as expressions that reference variables:

Hi {{$json["first_name"]}},

Thanks for joining — here's what to expect...

For teams that need non-technical editing: store templates in Notion or Airtable as HTML strings, and pull them via the Notion or Airtable node at send time. This separates template management from workflow logic.

Monitoring and Deliverability

Set up these checks in n8n to know when something breaks:

1. Error workflow — In n8n settings, configure an error workflow that fires when any workflow fails. Have it send a Telegram or Slack message with the error details.

2. Weekly send report — A scheduled workflow that queries your email provider's stats API and sends you a weekly summary: sends, opens, clicks, bounces, unsubscribes.

3. Bounce handler — Webhook that receives bounce events from your email provider. Automatically marks bounced emails as invalid in your database. Sending to bounced addresses destroys your sender reputation.

Cost Comparison: n8n vs Dedicated ESPs

Here's what this stack costs at different scales versus a traditional ESP:

The gap widens dramatically at volume. The tradeoff is that you're maintaining infrastructure and writing HTML templates. At low volume, it's not worth it. At medium-to-high volume, the savings are significant.

Getting Started

The fastest path to a working setup:

1. Deploy n8n — Either n8n Cloud or Docker on a VPS. Cloud is faster. Self-hosted is cheaper long-term.
2. Get a Resend account — Free tier covers 3,000 sends/month. Verify your domain (takes 15 minutes).
3. Build Workflow 1 first — The welcome sequence. It has the highest ROI and teaches you the core pattern (webhook → email → wait → email).
4. Add Workflow 2 or 3 next — Based on whether you have an e-commerce store (Workflow 2) or a service business (Workflow 3).
5. Build Workflow 6 last — Behavior-triggered emails require more setup on the data layer. Save it for when the basics are running.

The whole stack — n8n, Resend, and your first 3 workflows — can be running in a weekend. After that, every workflow you add is compounding on infrastructure you've already paid for.

Ready-Made n8n Workflow Templates

Building these workflows from scratch takes time. If you want to skip the setup and start with working templates, the Omni AI store has pre-built n8n workflow JSON files you can import directly — including the Lead Capture and CRM Sync workflow that covers the webhook trigger, CRM lookup, and follow-up email pattern used in Workflows 1 and 5 above.

The AI Department covers practical automation for small businesses. For pre-built n8n workflow templates, visit omniai.gumroad.com.