N8N Workflow: Select Available Cold Email Inbox via NocoDB UUID

Select an available cold email inbox from NocoDB (UUID included) — automatically

This n8n workflow checks your NocoDB-backed sending limits and inbox counters, then randomly selects an eligible cold email sender inbox for the current email sequence—returning selected_email, an emails_available flag, and a uuid for the calling workflow.

What this workflow does

• Receives the email sequence: It’s designed to be called as a sub-workflow and reads _firstItem (sequence number) from an Execute Workflow Trigger.
• Fetches sending limits from NocoDB: Queries NocoDB to determine the configured sending limit for the selected email sequence.
• Loads up to 100 sender inbox records: Retrieves sender inbox entries that include per-sequence sent counts and a “has limit reached” indicator.
• Aggregates results: Combines the retrieved inbox records into a single list for evaluation.
• Filters and randomly selects: Excludes inboxes that have reached the sequence limit, then randomly picks one eligible inbox (if any).
• Returns selection data: Outputs selected_email, emails_available, and uuid to the calling workflow.

Use cases

• When running multi-step cold email campaigns, automatically choose a sender inbox that hasn’t hit its per-sequence cap.
• Balance deliverability and throughput by distributing sends across multiple configured inboxes.
• Prevent over-sending by enforcing NocoDB limits before each sequence step.

Technical details

• HTTP integration with NocoDB: Uses HTTP Request nodes with an xc-token header (replace with your NocoDB API token/credential).
• Nodes used: set, code, wait, aggregate, sticky note, http request.
• NocoDB schema requirements: Update the two NocoDB API URLs and ensure field names like "email N limit" and "email N sent" match your tables.
• Expected I/O: Import into the same n8n instance, and ensure the calling workflow passes _firstItem and receives selected_email, emails_available, and uuid.