How can I rotate 10 Titan SMTP accounts in n8n?

Hello n8n Team,

I need help with a specific email-sending setup.

I have 10 separate Titan email inboxes. All 10 inboxes have already been warmed up, and I want to use these same warmed-up inboxes for my email outreach campaigns.

My goal is to automatically rotate these 10 Titan SMTP accounts using a round-robin system.

For example:

Lead 1 → Titan SMTP #1
Lead 2 → Titan SMTP #2
Lead 3 → Titan SMTP #3
Lead 4 → Titan SMTP #4
…
Lead 10 → Titan SMTP #10
Lead 11 → Titan SMTP #1
Lead 12 → Titan SMTP #2
…and so on.

Each Titan inbox has its own SMTP credentials.

I would like n8n to:

  1. Connect all 10 Titan SMTP accounts separately.
  2. Automatically select the next SMTP account for each outgoing email.
  3. Rotate the SMTP accounts using round-robin.
  4. Maintain a separate daily sending limit for each SMTP account.
  5. Add a configurable delay between emails.
  6. Skip an SMTP account if its daily limit has been reached or if it temporarily fails.
  7. Send the email using the correct From address for the selected Titan account.
  8. Ideally detect replies and associate them with the correct lead and sending account.
  9. Receive leads from GoHighLevel through webhook/API.
  10. Send the email through the selected Titan SMTP account.
  11. Return the sending result/message ID to GoHighLevel if possible.

The desired architecture is:

GoHighLevel
↓
n8n
↓
SMTP Rotation / Round Robin
↓
Titan SMTP #1
Titan SMTP #2
Titan SMTP #3
…
Titan SMTP #10
↓
Prospect

My main questions are:

  • Can n8n use 10 different SMTP credentials in one workflow?
  • Can n8n dynamically select a different SMTP credential for each email?
  • What is the recommended way to implement round-robin SMTP rotation?
  • Can each SMTP account have its own daily sending limit?
  • Can n8n automatically skip a failed SMTP account and use the next one?
  • Can this be connected to GoHighLevel using webhooks/API?
  • Is there an official n8n workflow/template for this use case?

I have already seen an n8n workflow example involving SMTP rotation, but I want to know the recommended architecture for using 10 separate SMTP accounts.

Please provide a step-by-step recommendation if this is possible.

Thank you.

Credentials can’t be set by expression, so one node can’t switch SMTP accounts. Ten Send Email nodes behind a Switch node is the supported shape.

Hold the rotation index and per-account daily counts in a Data table, or in $getWorkflowStaticData(‘global’) from a Code node. That Code node picks the next index, skips any account at its cap or marked failed today, and the Switch routes on that value.

On each Send Email node set Settings > On Error > Continue (using error output) and wire the error output back to the picker, so it marks that account down and takes the next.

Set From Email per node to its own inbox. Pace with Loop Over Items at batch size 1 and a Wait node.

Webhook node receives the lead, Send Email returns messageId, an HTTP Request node posts it back.

Replies: one IMAP Email Trigger per inbox, matching In-Reply-To to the stored messageId. No official template exists.

I can take this on. Scope as I read it: round-robin ten Titan SMTP accounts in n8n for GoHighLevel-sourced leads, with a per-account daily send cap, automatic skip on cap or failure, the correct From address per account, and reply-to-lead matching back to n8n. That’s a full mailer system: ten send nodes, a rotation/cap tracker, error rerouting, a webhook in, a status callback out, plus reply-matching triggers. That’s past the 8-node bounded-repair range, so it’s written scope and quote first rather than a flat price. Payment is Venmo, so US clients only right now. If that works, DM me your webhook payload shape, today’s per-inbox daily limits, and whether reply-matching exists anywhere yet, and I’ll send a scoped price and delivery window within an hour.