Problem
Spreadsheets, manual address copying and scattered signature files made delivery, failure and cancellation tracking difficult.
EMAIL CAMPAIGN AUTOMATION
IN PRODUCTIONMala Direta
n8n, queues and reliability
I built an internal product to prepare, review, schedule and track campaigns without requiring the team to work directly in the n8n editor.
Current useCampaign automation with queues, deduplication and delivery history
Technologiesn8n · JavaScript · PostgreSQL · SMTP · Docker
My workProcess · architecture · workflows · interface · deployment · support
SCREENS AND FLOWS
How the team uses the automation
The images show the published interface and workflows with fictional data.
Public scope
The repository contains two workflows, with 158 nodes in the main flow and nine domain Data Tables.
Privacy
Credentials, recipients, real campaigns and internal references were removed.
What I built
A web interface, campaign rules, separate recipient records, queueing, SMTP, history, deduplication, suppression and an error workflow.
Important decision
I moved cancellation checks inside the loop, before every recipient, because checking only at the beginning did not stop an already running campaign correctly.
Current result
- The workflow automates campaigns with queued delivery, deduplication and delivery records.
- Cancellation is checked again for each recipient, including during an active send.
- The complete n8n environment, which also hosts other automations, has accumulated more than 10,000 workflow executions in production.
Current limits
The flow does not claim a formal delivery SLA. Bounce handling, reputation, unsubscribe, SPF, DKIM and DMARC must be monitored as volume grows.
Next evolution
At larger scale, I would separate delivery workers, adopt a managed broker, centralize metrics and formalize retention and suppression policies.
This case presents a sanitized public version of an internal solution in use.
Next projectHelpDesk
Contact