I will build n8n cold email automation with SMTP rotation and verification


Level 2
About this gig
Need a safer way to send cold emails through multiple SMTP accounts?
I will build an n8n cold email automation that uses a round-robin sender workflow, email verification, and basic risk-control logic before sending.
The workflow can:
- Read leads from your selected source
- Verify email addresses before sending
- Skip invalid or risky addresses based on verification results
- Rotate multiple SMTP accounts using round-robin logic
- Respect configured sender limits
- Add controlled delays between sends
- Track sending status and basic errors
- Continue from the next available sender when required
The goal is to distribute sending across multiple SMTP accounts and reduce avoidable risks such as sending to invalid addresses or overusing a single sender.
NOTE
- This setup does not guarantee inbox placement or zero bounces. Deliverability also depends on your domains, SMTP reputation, email content, and sending practices.
- Need different logic or additional integrations? Message me before ordering for a custom solution.
Get to know Kashif Saeed
IT Services, Deploy Opensource Projects
Level 2
- FromPakistan
- Member sinceJul 2017
- Avg. response time1 hour
- Last delivery1 month
Languages
Urdu, Hindi, English
My Portfolio
FAQ
How does the SMTP sender rotation work?
The workflow selects only active SMTP accounts that are under their daily limit, then rotates sending by choosing the least recently used sender. This helps spread sending across the available SMTP pool.
How many SMTP accounts can be added?
The workflow is built around an SMTP sender pool, so multiple SMTP accounts can be added. Each sender can have its own status, daily limit, sent count, and usage history.
What happens when an SMTP account reaches its daily limit?
A sender is skipped once its sent_today count reaches its configured daily_limit. The workflow then selects another active SMTP account that is still under its allowed limit.
What happens if an SMTP sender fails?
Failed sends increase that sender’s failure count and log the error. In the current workflow, a sender is automatically disabled after 3 consecutive failures, so it is no longer selected for sending.
What does the email verifier check?
It checks email format, domain/MX routing, disposable and role-based addresses, previous bounce history, mailbox response, catch-all behavior, and other risk signals before deciding whether sending is allowed.
Can it check if a mailbox really exists?
Where the mail server allows it, the workflow connects to the recipient’s SMTP server and checks whether the mailbox accepts the address without sending an actual email.
Does it detect catch-all domains?
Yes. For supported cases, it tests a random address on the same domain to see if the server accepts all recipients. Catch-all results are treated as a warning rather than guaranteed mailbox validation.
What kinds of emails can be rejected automatically?
The workflow can reject invalid formats, disposable emails, previous-bounce addresses, role-based emails, invalid mail routing, confirmed invalid mailboxes, and high-risk domains.
Does deep verification work on every server?
No. SMTP mailbox and catch-all checks require outbound access to mail servers, commonly on port 25. If the hosting provider blocks this, the workflow can still run non-SMTP checks but deep mailbox verification may be limited.
Does this workflow require the n8n Execute Command node?
Yes, for deep SMTP mailbox and catch-all checks. The workflow uses Execute Command to run DNS and SMTP verification logic. Without it, the advanced mailbox-level checks will not work as designed.
