Connect InboxKit Mailboxes to Reply.io in Under 4 Minutes

Reply.io connects to InboxKit via standard email + password in the Sequencers Connect screen. Paste your Reply.io login, InboxKit validates, and every selected InboxKit mailbox lands in Reply.io as a new email sender. The connect takes about 90 seconds.

Reply.io is the most channel-diverse tool in the InboxKit catalog. It runs email, LinkedIn messages, SMS, and even phone calls inside a single sequence. For InboxKit users, the important thing to understand is that only the email channel of Reply.io touches your InboxKit mailboxes, LinkedIn, SMS, and calls all use their own infrastructure inside Reply.io and are unrelated to the mailbox connect. This is similar to Emelia's LinkedIn-plus-email design, but Reply.io goes further by adding SMS and calls.

Reply.io's value prop is that a single sequence can mix channels to improve reply rates. A typical multichannel flow looks like this:

The email steps go through your InboxKit mailboxes and count against your daily send quota. The LinkedIn, SMS, and call steps are unrelated to InboxKit. This matters because if you're planning a 6-email sequence, each mailbox's daily quota has to handle the combined send volume of all email steps across the campaign.

See cold email reply rate benchmarks 2026 for the data on how multichannel sequences compare against email-only for reply rates. Published benchmarks suggest 2-3x lift at the cost of 3-5x the complexity.

Gather these:

Important scope note on credentials. Reply.io supports both traditional username/password authentication and an API key option inside their UI. The InboxKit connect uses the username/password path because it's universally supported across all Reply.io plans. API-key-only integrations are available inside Reply.io itself for direct API work, but the InboxKit mailbox push uses credentials. This is different from tools like SendKit or BrandJet that use API keys exclusively.

The full click path:

Total: about 90 seconds.

Reply.io uses the standard credential form. No workspace picker, no API key. Validation happens on submit. After the export completes, the mailboxes show up inside Reply.io → Email Accounts, ready to attach to a sequence.

Because multichannel sequences fire multiple emails per prospect over a 2-week window, your daily send budget has to account for the combined email volume. Here is the math:

The math assumes 40 emails/day per mailbox as the practical safe ceiling. Google's published hard cap is higher, but staying under 50/day protects reputation. If you are running 5,000-prospect multichannel campaigns, you need InboxKit Enterprise at $299/month for 100 mailboxes to have comfortable headroom.

Warmup interaction. Reply.io does not ship built-in warmup on all plans, so pair your InboxKit mailboxes with one of: InboxKit isolated warmup add-on ($3/mailbox/month), TrulyInbox, MailToaster, or Warmy.io. Pick one: running two on the same mailbox is always a bad idea.

Reply.io's LinkedIn channel is separate from InboxKit. Here's what you should know if you plan to use multichannel:

• LinkedIn channel runs off your LinkedIn session cookie. Reply.io's LinkedIn module opens a browser tab (or uses their cloud extension) to drive your actual LinkedIn account. If your LinkedIn gets restricted, the LinkedIn steps fail regardless of InboxKit.
• Rate limits are LinkedIn's, not Reply.io's. LinkedIn caps ~100 connection requests/week and ~80 messages/day per account. You can't bypass this by connecting 10 InboxKit mailboxes, they don't apply to LinkedIn.
• LinkedIn Sales Navigator is strongly recommended. Reply.io's LinkedIn module works with free LinkedIn but restrictions hit much faster. Sales Navigator gives you higher per-day caps and better prospect search.
• LinkedIn failures don't break email steps. If a LinkedIn step fails (restricted account, rate limit, etc.), the email step continues to fire. Reply.io just flags the LinkedIn step as 'skipped' in the campaign log.

The bottom line: InboxKit handles the email side. Reply.io's LinkedIn side is a separate tool that happens to live in the same dashboard. If the LinkedIn side breaks, it has nothing to do with your InboxKit mailbox connection.

The typical failure modes for InboxKit → Reply.io connections:

The per-account throttle is worth understanding. Reply.io throttles sends at the account level to prevent individual mailboxes from burning reputation. If you configure a mailbox for 40/day but Reply.io's throttler decides the mailbox is too new, it caps at 15/day and the difference just doesn't send. Check Reply.io → Settings → Daily Limits if you see your effective volume consistently below configured.

Four smoke tests:

Test 1: mailbox test send. In Reply.io → Email Accounts → (pick InboxKit mailbox) → Send Test. Confirm delivery in <30 seconds with DKIM passing.

Test 2: reply round-trip. Reply to the test. Check Reply.io's Unibox within 2 minutes. If the reply appears, IMAP is working.

Test 3: multichannel pilot. Run a 3-prospect test sequence with email step 1, LinkedIn step 2, email step 3. Confirm all three fire. Email steps verify the InboxKit connection; LinkedIn step verifies your LinkedIn session is active in Reply.io.

Test 4: inbox placement test. Run a seed-list test across Gmail, Outlook, Yahoo, Hotmail. Target 9/10+. Reply.io's per-account throttler is strict, so a clean test here validates that your outgoing emails are passing every filter.