← Blog

March 18, 2026 · 6 min read

Best n8n workflow templates for email automation

Why n8n is a strong choice for email automation, with specific templates you can import today. Covers inbox routing, digest workflows, and Slack integration.

Email automation is one of those problems that sounds simple until you try to build it. You need triggers, filters, conditional logic, and integrations with at least two or three other services. Most no-code tools either lock you into their ecosystem or charge per execution.

n8n is different. It is open source, self-hostable, and built around a visual workflow editor that developers actually like using. You wire up nodes, connect APIs, and deploy workflows that run on your own infrastructure. No per-execution fees. No vendor lock-in.

Why n8n works well for email

Email automation needs three things: reliable triggers, flexible routing, and good integrations. n8n handles all three.

Triggers can fire on a schedule (poll IMAP every 5 minutes), on a webhook (forwarded emails), or from another workflow. Routing is handled through IF nodes, Switch nodes, and code nodes where you can write JavaScript for complex conditions. Integrations cover Gmail, Outlook, IMAP, SMTP, SendGrid, Mailgun, and dozens more.

The visual editor makes it easy to see the full flow at a glance. You know exactly what happens when an email arrives, where it gets routed, and what actions fire. No hidden logic buried in config files.

Template 1: Email Automation Workflow

The n8n-email-automation-workflow template in the Runbooks gallery handles inbound email processing end to end. It polls your inbox on a schedule, classifies emails by sender and subject, and routes them to different actions.

Client emails get forwarded to your CRM. Receipts get logged to a Google Sheet. Newsletters get archived. Everything else lands in a summary notification.

This is the template to start with if you want a general-purpose email router. It handles the 80% case and is easy to extend.

Template 2: Email Digest to Slack

The n8n-email-digest-to-slack template collects emails over a time window and sends a single digest to a Slack channel. Instead of getting pinged for every email, your team sees one clean summary.

It works well for support inboxes, shared team email accounts, and any situation where multiple people need visibility into incoming messages without the noise of real-time forwarding.

The digest groups emails by sender, includes subject lines and a preview of the body, and links back to the original message. Runs every hour by default, configurable to whatever interval you want.

Template 3: Lead Capture Pipeline

This template watches for emails matching specific patterns (contact form submissions, demo requests, partnership inquiries) and creates records in your CRM automatically. It extracts name, company, and email from the message body, creates the lead, and sends a Slack notification to your sales channel.

Useful for small teams that do not have a dedicated sales ops person but still want leads tracked properly.

Template 4: Invoice and Receipt Tracker

Watches for emails with attachments that look like invoices or receipts. Extracts the amount, vendor, and date using a code node with basic regex patterns. Logs everything to a Google Sheet and flags anything over your configured threshold.

Not as sophisticated as a dedicated accounting tool, but it covers the common case of tracking expenses without manual data entry.

How to import a template

Every n8n template in the Runbooks gallery includes a JSON workflow file. Importing takes about 30 seconds.

  1. Download the JSON file from the template page at tryrunbooks.com
  2. Open your n8n instance and go to Workflows
  3. Click Import from File and select the JSON
  4. Update the credential nodes with your own API keys and OAuth tokens
  5. Activate the workflow

Here is a simplified example of what the workflow JSON looks like:

{
  "nodes": [
    {
      "name": "IMAP Trigger",
      "type": "n8n-nodes-base.imapEmail",
      "parameters": {
        "mailbox": "INBOX",
        "options": { "allowUnauthorizedCerts": false }
      },
      "position": [250, 300]
    },
    {
      "name": "Classify Email",
      "type": "n8n-nodes-base.switch",
      "parameters": {
        "rules": {
          "rules": [
            { "value1": "={{$json.from}}", "operation": "contains", "value2": "client.com" }
          ]
        }
      },
      "position": [450, 300]
    },
    {
      "name": "Post to Slack",
      "type": "n8n-nodes-base.slack",
      "parameters": {
        "channel": "#email-alerts",
        "text": "New email from {{$json.from}}: {{$json.subject}}"
      },
      "position": [650, 300]
    }
  ],
  "connections": {
    "IMAP Trigger": { "main": [[{ "node": "Classify Email" }]] },
    "Classify Email": { "main": [[{ "node": "Post to Slack" }]] }
  }
}

Setup tips

  • Use IMAP over Gmail API if you want to avoid OAuth setup. IMAP works with any email provider and only needs an app password.
  • Set reasonable polling intervals. Every 5 minutes is fine for most use cases. Every 30 seconds is usually overkill and burns resources.
  • Test with a dedicated email account first, not your primary inbox. You do not want a misconfigured workflow archiving real emails.
  • Use n8n's built-in error workflow to catch failures. Route errors to Slack so you know immediately if something breaks.

Get started

All of these templates are available in the Runbooks gallery at tryrunbooks.com. Each one includes the workflow JSON, a setup guide, and a list of required credentials. Import one, customize it for your stack, and stop processing email by hand.

More posts

October 27, 2026

Your GitHub Actions run history is not your bill

October 23, 2026

A DNS record changed. Should your OpenClaw monitor alert?

October 20, 2026

Zero errors is not always good news: checking the log pipeline before an agent alerts

October 17, 2026

A running container is not a healthy service: an OpenClaw monitoring runbook

October 14, 2026

OpenClaw database backup checks vs restore tests: what each proves

October 5, 2026

OpenClaw automation ran, but no message arrived: diagnose execution and delivery

October 2, 2026

OpenClaw SecretRefs for recurring workflows: a practical migration checklist

September 29, 2026

The scheduled blog queue ran dry: a runway check that catches it early

August 24, 2026

Agent workflow validation checklist before you reuse a template

August 21, 2026

Bounded background tasks for coding agents

August 18, 2026

Agent runbook status files that actually work

August 15, 2026

7 OpenClaw workflows worth running, and 5 that are not

August 12, 2026

The OpenClaw workflow security checklist we use before turning on tools

August 9, 2026

Your HEARTBEAT.md should be boring

August 6, 2026

How to build an OpenClaw automation that survives retries

August 3, 2026

OpenClaw cron vs heartbeat: the production rule that actually works

April 30, 2026

OpenClaw just shipped real voice agent calls. Here are 5 workflows worth setting up.

March 27, 2026

The best OpenClaw skills nobody knows about

March 25, 2026

Top AI agent workflow templates for developers in 2026

March 23, 2026

OpenClaw vs n8n: when to use each for agent automation

March 20, 2026

How to automate Make.com workflows with AI agents

March 15, 2026

OpenClaw starter packs: the fastest way to a useful agent

March 12, 2026

How to build your own OpenClaw runbook from scratch

March 9, 2026

5 OpenClaw workflows that save 10 hours/week