Connect InboxKit Mailboxes to Smartlead in 3 Minutes

Smartlead accepts InboxKit Google Workspace and Microsoft 365 mailboxes three ways: Gmail/Google OAuth (1-click, most reliable), app password + SMTP/IMAP (when OAuth is blocked by admin policy), and SmartSenders CSV upload (for 20+ mailboxes at once). OAuth finishes in under 60 seconds per mailbox. App password takes around 4 minutes because you must enable 2-Step Verification and generate the 16-character password first. CSV import handles 100 mailboxes in a single upload.

This guide walks through all three paths with the exact Smartlead menu locations, the Google admin prerequisites that cause the most common failures, and the ramp-up numbers that keep new mailboxes out of spam.

Before opening Smartlead, confirm these items. Skipping any of them causes the 'Test Connection' step to fail silently:

IMAP OU setting is the #1 cause of Smartlead connection failures. Smartlead's help docs explicitly call this out: 'Ask your admin to go to admin.google.com, navigate to Apps > Google Workspace > Gmail > End User Access, and ensure IMAP Access is enabled for your organizational unit.' InboxKit mailboxes provisioned under a new Google Workspace tenant usually have this on by default, but legacy tenants migrated years ago often have it off.

InboxKit handles the DNS row automatically. SPF, DKIM, DMARC, and MX records are provisioned in under 60 seconds via Cloudflare at the moment a mailbox is created. Verify with any dig TXT yourdomain.com check or the cold email domain setup checklist.

Google OAuth is the more secure and reliable method. It does not require storing passwords and reduces the risk of disconnection from security policy changes. This is Smartlead's own recommendation.

Total: about 70 seconds per mailbox.

Admin whitelist for Google Workspace: If your workspace blocks third-party OAuth apps, a pop-up appears saying 'This app is blocked by your admin.' Fix: admin.google.com → Security → Access and data control → API controls → Manage Third-Party App Access → add Smartlead as Trusted. Source: Smartlead Gmail OAuth guide.

When OAuth is blocked (common in enterprise Google Workspace tenants), use an app password. Smartlead calls this 'Connect Gmail with SMTP' and it is the most compatible path.

Generate the Google app password first:

Connect in Smartlead:

Why this fails: 70% of failures come from using the regular account password instead of the app password, 25% from 2-Step Verification not being enabled (you cannot generate an app password without it), and 5% from the workspace having IMAP disabled. Source: Smartlead Connect Gmail With SMTP.

For 20+ InboxKit mailboxes, SmartSenders CSV is the only sane option. Smartlead's DFY Mailboxes feature specifically supports CSV upload for bulk provisioning.

Step 1: Export from InboxKit. InboxKit Mailboxes page → select all → Export CSV. The export includes email, first name, last name, app password, SMTP host/port, IMAP host/port pre-filled for each mailbox. The InboxKit Exports page tracks every export with status and retry capability.

Step 2: Format for Smartlead. Smartlead expects these exact column headers:

Step 3: Upload. app.smartlead.ai → Email Accounts → Bulk Upload CSV → drag the file. Smartlead validates each row and shows inline errors. A 50-mailbox upload takes about 3 minutes to fully validate and activate.

Step 4: Turn on warmup in bulk. Filter by 'Not Warmed Up', select all, click Enable Warmup. If you are using InboxKit's isolated warmup add-on at $3/mailbox/month, disable Smartlead's built-in warmup. Running two warmup networks simultaneously doubles sent volume on new mailboxes and sends bad signals to Google.

Keep this table handy for every SMTP error screen:

Microsoft 365 specific: Since 2022, Microsoft disables SMTP AUTH by default on all new tenants. Your admin must enable it per-mailbox: Exchange Admin Center → Recipients → Mailboxes → (select) → Manage email apps → toggle Authenticated SMTP on. If this is off, Smartlead returns: 'Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant.' For the deeper comparison between the two providers for cold email, see Google Workspace vs Microsoft 365.

Smartlead's default daily limit is 50, which is too high for a brand-new mailbox. Use this schedule instead:

Why not higher than 50? Google throttles outbound SMTP relay above ~500 per day for Workspace mailboxes regardless of your plan. Hitting that ceiling triggers 421 temporary errors and deliverability drops. The practical cold email ceiling is ~40-50 per mailbox. Scale horizontally: 50 mailboxes × 40/day = 2,000 daily sends. See how many domains you need for cold email and scale cold email 100 to 10000.

Smartlead's API lets you bulk-update daily limits via PATCH /api/v1/email-accounts/{id} if you prefer scripting the ramp instead of editing in the UI.

From reviewing InboxKit → Smartlead exports, these five account for 85% of failures:

Smartlead-specific footgun: The Smartlead dashboard shows 'Connected' even when IMAP is broken. Run the verification flow below, do not trust the checkmark.

Do not launch a campaign until these three tests pass:

Test 1: Test email. Smartlead → Email Accounts → (select mailbox) → Send Test Email to yourself. Expect it in your inbox within 30 seconds.

Test 2: Reply sync check. Reply to the test. Check Smartlead → Master Inbox. If the reply appears in 2 minutes, IMAP is healthy. If not, IMAP is silently broken, so fix before launching.

Test 3: Warmup engagement. After 24 hours, check the mailbox's Warmup tab. Expect to see 10-15 sent warmup messages, 8-12 opened, 5-8 replied. If these numbers are zero, warmup is not running. The mailbox is still in 'setup' mode. See cold email warmup guide for what healthy warmup looks like in week one.