Brevo Cold Email & IP Warming: Dedicated SMTP Deliverability

This technical breakdown contains affiliate links. If you deploy this stack using my links, I earn a commission at no extra cost to you.

Mastering cold email deliverability is the foundational pillar of modern B2B outbound sales. When launching high-volume campaigns using Brevo (formerly Sendinblue) and n8n workflow orchestration, relying on shared IP pools exposes your domain to shared spam penalties and blacklisting. Deploying a dedicated IP address backed by a disciplined 30-day automated IP warming schedule is the mandatory strategy for achieving 98%+ inbox placement across major Internet Service Providers (ISPs).

Why Is Dedicated IP Warming Critical for Brevo Cold Email Outreach?

Dedicated IP warming is critical for Brevo cold email outreach because major Internet Service Providers (ISPs) like Google Workspace and Microsoft 365 evaluate sender reputation based on IP sending patterns, history, and engagement metrics. When dispatching cold outbound campaigns from a fresh dedicated IP address, ISPs have zero historical data to evaluate whether your messages are legitimate business correspondence or unsolicited spam. If a sender suddenly blasts thousands of cold emails from an un-warmed IP, spam filters flag the abrupt volume spike, instantly placing your domain and IP on global blacklists like Spamhaus. IP warming is the deliberate process of gradually increasing email daily sending volume over a 30-day schedule while maintaining high engagement rates. This process establishes positive domain reputation, satisfies ISP algorithmic security checks, and ensures your cold outbound emails consistently reach prospect primary inboxes rather than spam folders.

Below is the technical lifecycle of dedicated IP warming and deliverability governance:

graph TD
    A[Fresh Brevo Dedicated IP] --> B[DNS Security Setup: SPF + DKIM + DMARC]
    B --> C[n8n Daily Throttling Engine]
    C --> D[Week 1: 50 emails/day High Engagement]
    D --> E[Week 2: 100 emails/day Monitoring Bounces]
    E --> F[Week 3: 250 emails/day Controlled Cold Outreach]
    F --> G[Week 4: 500+ emails/day Full Outbound Velocity]
    G --> H[98%+ Primary Inbox Placement]

How Do You Configure SPF, DKIM, and DMARC Records for Brevo SMTP?

Configuring SPF, DKIM, and DMARC authentication records for Brevo SMTP is the mandatory technical prerequisite for establishing sender domain authority and bypassing strict ISP spam filters. Sender Policy Framework (SPF) specifies which mail servers are authorized to send email on behalf of your domain, implemented by adding an official TXT record containing include:spf.brevo.com. DomainKeys Identified Mail (DKIM) adds a cryptographic signature to every outgoing header, verified by publishing Brevo's public key TXT record in your DNS settings. Domain-based Message Authentication, Reporting, and Conformance (DMARC) instructs receiving mail servers how to handle emails failing SPF or DKIM checks, configured with a policy of p=none initially before graduating to p=reject. Validating these technical DNS records inside Brevo guarantees message integrity, prevents domain spoofing attacks, and boosts primary inbox placement rates across all outbound cold email campaigns.

Here is the exact DNS record setup matrix for Brevo SMTP deliverability:

What Is the 30-Day Automated IP Warming Schedule for B2B Outbound?

The 30-day automated IP warming schedule for B2B outbound is a structured, ramped volume plan designed to safely build sending reputation on a new Brevo dedicated IP. Week 1 begins with a conservative daily limit of 50 emails, targeted strictly at highly engaged existing contacts or internal warm lead accounts to generate high open and click-through rates. Volume doubles during Week 2 to 100 emails per day, while monitoring hard bounce rates to ensure they remain strictly below 1%. Week 3 scales daily outbound capacity to 250 emails, introducing cold prospect cohorts gradually while maintaining active reply monitoring. By Week 4, daily sending capacity reaches 500 to 1,000 emails, fully establishing the dedicated IP's reputation across major ISPs. Strict adherence to this 30-day schedule prevents premature blacklisting, protects corporate domain authority, and safeguards long-term email deliverability.

How Do You Automate Volume Throttling in n8n Using Code Nodes?

Automating volume throttling in n8n using Code Nodes enforces strict daily IP warming limits programmatically, preventing campaign batch spikes from exceeding ISP thresholds. Within an n8n workflow, a custom JavaScript Code Node tracks the number of dispatched emails for the current calendar day against a maximum limit stored in workflow static data or an external Redis store. Before calling the Brevo SMTP API node, the JavaScript node checks the current execution count; if the daily allocation limit (such as 100 emails during Week 2) is reached, the Code Node diverts remaining prospect records into a delay queue table in PostgreSQL. The workflow schedules a cron trigger to resume queue processing at midnight UTC when daily counters reset. Building this automated throttling logic inside n8n eliminates human oversight errors and enforces disciplined sending habits during IP warming.

Below is the n8n JavaScript Code Node for automated daily volume throttling:

// n8n Code Node: Automated IP Warming Volume Throttler
const staticData = $getWorkflowStaticData('global');
const today = new Date().toISOString().split('T')[0];

// Initialize daily counter static data
if (staticData.lastResetDate !== today) {
  staticData.lastResetDate = today;
  staticData.dailySentCount = 0;
}

// Set maximum daily limit according to warming schedule (e.g. Week 2 = 100 emails)
const DAILY_MAX_LIMIT = 100;

const items = $input.all();
const approvedBatch = [];
const deferredBatch = [];

for (const item of items) {
  if (staticData.dailySentCount < DAILY_MAX_LIMIT) {
    staticData.dailySentCount++;
    approvedBatch.push({
      json: {
        ...item.json,
        dispatchApproved: true,
        currentDailyCount: staticData.dailySentCount
      }
    });
  } else {
    deferredBatch.push({
      json: {
        ...item.json,
        dispatchApproved: false,
        deferReason: 'Daily IP Warming Limit Reached'
      }
    });
  }
}

// Return approved batch for immediate Brevo SMTP dispatch
return approvedBatch;

Import this n8n Workflow JSON Blueprint for Brevo SMTP dispatch with throttling:

{
  "name": "Brevo Dedicated IP Warming & Throttled SMTP Blueprint",
  "nodes": [
    {
      "parameters": {
        "rule": {
          "interval": [
            {
              "field": "cronExpression",
              "expression": "0 9 * * 1-5"
            }
          ]
        }
      },
      "name": "Daily Dispatch Trigger",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.1,
      "position": [240, 300]
    },
    {
      "parameters": {
        "url": "https://api.brevo.com/v3/smtp/email",
        "sendHeaders": true,
        "headerParameters": {
          "parameters": [
            {
              "name": "api-key",
              "value": "={{ $env.BREVO_API_KEY }}"
            }
          ]
        }
      },
      "name": "Brevo Transactional SMTP Dispatch",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 3,
      "position": [480, 300]
    }
  ],
  "connections": {
    "Daily Dispatch Trigger": {
      "main": [
        [
          {
            "node": "Brevo Transactional SMTP Dispatch",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  }
}

How Do You Monitor Sender Reputation and Spam Trap Rates in Brevo?

Monitoring sender reputation and spam trap rates in Brevo requires tracking real-time delivery metrics, ISP feedback loops, and email list hygiene analytics within your RevOps dashboard. Key indicators of deliverability health include maintaining a hard bounce rate below 0.5%, a spam complaint rate below 0.05%, and an overall open rate above 30%. Brevo provides native webhooks that log bounce events, unsubscribe requests, and spam flags instantaneously; connecting these webhooks to an n8n workflow enables automatic contact suppression, instantly removing hard-bounced addresses from future mailing lists. Furthermore, RevOps teams must periodically cross-reference dedicated IPs against major blacklists using Google Postmaster Tools and MXToolbox. Consistently monitoring deliverability telemetry allows operations teams to identify deliverability degradation early, pause campaigns proactively, maintain pristine domain reputation, and ensure maximum email inbox placement over time. By centralizing these performance metrics, RevOps teams move from reactive cleanup to proactive reputation management, establishing an indestructible foundation for long-term B2B cold email performance and high-volume scalability.

(To connect Apollo leads cleanly into your warmed Brevo SMTP pipeline, follow our guide on Apollo to Brevo n8n Pipeline: B2B Automated Outreach Guide).