Connect InboxKit Mailboxes to Emelia in Under 4 Minutes

Emelia connects to InboxKit via a standard credential form in the Sequencers Connect screen. You paste your Emelia login email and password, InboxKit validates them against Emelia's API, and every selected InboxKit mailbox gets provisioned inside Emelia as a new sender. The entire connect takes about 90 seconds end to end.

Emelia positions itself as the 'beginner-friendly' option in the outreach category: one dashboard for cold email plus LinkedIn, a built-in warmup engine, and a unified view of both channels. That design choice matters for InboxKit users because Emelia's LinkedIn side does not touch the InboxKit mailbox at all, it runs from your LinkedIn session. The InboxKit connection only handles the email half of the pipeline.

Gather these before opening the Sequencers Connect screen:

The beginner note. Emelia's UX is more hand-holdy than Smartlead or Instantly, but the underlying SMTP/IMAP mechanics are identical. The same Google Workspace admin settings that block a Smartlead connection will block an Emelia connection, IMAP at OU level, 2-Step Verification for Gmail app passwords, and Authenticated SMTP for Microsoft 365. Don't let Emelia's friendly wizard fool you into skipping those prereqs. See the cold email domain setup checklist for the complete admin checklist.

The full click path:

Total: about 90 seconds.

Emelia uses the standard credential flow: no workspace picker, no API key, no custom validation UI. Validation happens on submit, so you'll know within 2 seconds whether the credentials are correct.

Emelia is one of the few outreach tools that bundles LinkedIn automation into the same dashboard as cold email. For InboxKit users, it is important to understand that the LinkedIn side of Emelia runs entirely off your LinkedIn session, it has nothing to do with your InboxKit mailboxes.

The practical implication. If you are using Emelia's multichannel sequences, only the email steps hit your InboxKit mailboxes and count against your daily send limits. The LinkedIn steps run from your LinkedIn session and are limited by LinkedIn's own rate limits (~100 connection requests per week, ~80 messages per day).

If cold email is the priority and LinkedIn is secondary, Emelia is fine. If LinkedIn is the priority, you may want a LinkedIn-first tool instead. For InboxKit users focused mostly on email, Smartlead or Instantly typically deliver more campaign-management power per dollar.

Emelia ships a built-in warmup engine as part of every paid plan. The InboxKit isolated warmup add-on costs an extra $3/mailbox/month. You have to pick one per mailbox.

Emelia's warmup is a shared-pool design, your mailbox's warmup traffic mingles with other Emelia tenants' warmup. That is typical for bundled-warmup outreach tools and is fine for most use cases. InboxKit's isolated warmup is a separate peer network, which gives you cleaner reputation signals but costs $3/month extra.

Do not run both at once. Running two warmup engines on one mailbox roughly doubles warmup-sent volume, confuses reputation signals at Google Postmaster Tools, and can cause a deliverability dip. Toggle one off when the other turns on. For a deeper look at how warmup networks work internally, see cold email warmup guide.

Set these inside Emelia → Accounts → (select mailbox) → Daily Limit after the import completes:

Emelia's ramp-up recommendation is slightly more conservative than Instantly's by default, it tends to cap new mailboxes at 10/day for the first two weeks of real sending. You can override this inside Emelia → Campaign Settings, but for deliverability reasons, keep the cap low in the first two weeks even if the tool allows more. See cold email sending volume limits guide for the math on how ramp-up affects reputation.

The typical failure modes for InboxKit → Emelia connections:

The LinkedIn failure mode is important to flag because the error can masquerade as an InboxKit connection problem. If the email steps work fine but the LinkedIn step fails, that is entirely on Emelia's LinkedIn integration and has nothing to do with your InboxKit mailboxes. Debug it from Emelia → Integrations → LinkedIn, not InboxKit.

Four checks before launching your first sequence:

Test 1: mailbox test send. In Emelia → Accounts → (select InboxKit mailbox) → Send Test. Confirm delivery in <30 seconds with DKIM passing in headers.

Test 2: reply round-trip. Reply to the test. Within 2 minutes, Emelia's unified inbox should show the reply. If not, IMAP is broken: fix that before anything else.

Test 3: pilot sequence. Run a 10-prospect test sequence from one mailbox for 2 days. Watch for zero bounces, zero complaints, and Emelia's deliverability score ≥85%. If all green, scale the sequence.

Test 4: inbox placement test. Send a seed-list test (Gmail, Outlook, Yahoo, Hotmail). Look for 9/10+. Below 8/10 means the DNS or warmup layer needs more time. See inbox placement testing explained for the diagnostic tree.