Connect InboxKit Mailboxes to Hothawk in Under 4 Minutes

Hothawk connects via standard email + password in the InboxKit Sequencers Connect screen. You paste your Hothawk login, InboxKit validates against Hothawk's API, and every selected InboxKit mailbox gets provisioned inside Hothawk as a shared team inbox. The entire connect takes about 90 seconds.

Hothawk is the only outreach-adjacent tool in the InboxKit catalog that lives in the Inbox Management category (alongside Master Inbox), not the Outreach category. That distinction matters: Hothawk is not a cold email sender. It is a shared inbox and pipeline tool for sales teams to collaborate on replies from cold email sequences they're already running elsewhere. You still need a sender like Instantly or Smartlead to actually send the first touches. Hothawk handles the reply side.

The InboxKit Sequencers Connect screen groups platforms by category: Outreach, Warmup, and Inbox Management. Hothawk sits in Inbox Management because its entire value prop is on the reply side of the funnel, not the send side.

What this means for your stack: run Instantly or Smartlead as the sender, run Hothawk as the shared inbox and pipeline layer, and use InboxKit to provision the real mailboxes underneath both. When a prospect replies, the reply lands in Gmail / Outlook as normal, Hothawk pulls it via IMAP, auto-assigns it to the right rep, and tracks it through the pipeline. Your senders on the cold email tool side (Instantly / Smartlead) still see the reply in their own Unibox, but the team-management layer is handled by Hothawk.

Have these ready:

IMAP is non-negotiable. Hothawk's entire model is reading replies from connected mailboxes, classifying them, and assigning them to reps. It does this via IMAP. If IMAP is disabled for the Google Workspace OU containing your InboxKit mailboxes, Hothawk will show the mailbox as 'connected' but pull zero replies, a state that looks like the tool is broken but is actually a one-line admin fix. See the cold email domain setup checklist for the full list of Google Workspace admin settings that cold email tools require.

The full click path:

Total: about 90 seconds.

Hothawk uses the standard credential form, no workspace picker, no API key. Validation is synchronous on submit. If you have a multi-workspace Hothawk setup and your login is associated with multiple workspaces, Hothawk defaults to your current active workspace, switch inside Hothawk before running the export if you need to target a specific one.

Once the connect is live, here is what happens to a reply sent to one of your InboxKit mailboxes:

The reply-send flow uses the InboxKit mailbox. When a rep replies inside Hothawk, Hothawk uses the stored SMTP credentials of the InboxKit mailbox to send the reply. This is why your InboxKit warmup and daily-send limits still matter for Hothawk workflows. Every rep reply counts against the mailbox's daily quota just like a sequence send would. See email sending limits google microsoft for the underlying Google and Microsoft caps.

Hothawk does not ship a warmup product. It is an inbox management tool, not an outreach tool. If you want warmup on your InboxKit mailboxes while running them through Hothawk, pair with one of:

• InboxKit isolated warmup add-on: $3/mailbox/month, separate peer network, stays with the mailbox regardless of which tool you send from
• Dedicated warmup tool: TrulyInbox, Warmy, MailToaster, or Warmforge
• Bundled warmup in your sender: Instantly, Smartlead, Lemlist all ship their own warmup

The typical Hothawk stack runs: Instantly (send + warmup) → Hothawk (reply management) → InboxKit (mailbox provision). In this setup, Instantly handles warmup as part of its plan, and Hothawk never touches the warmup side. For a deeper look at which warmup engine to pick, see email warmup tools comparison.

The failure modes you are likely to hit:

On IMAP polling interval. Hothawk defaults to a 60-second IMAP poll. If you need faster reply routing (e.g. for a high-response-rate campaign), upgrade to a Hothawk tier that supports 30-second polling. Below 30 seconds, you hit Google's IMAP rate limits and start getting throttled, which causes missed replies, a strictly worse state than 60-second polling with reliable pickup.

Three smoke tests before you trust Hothawk with a real pipeline:

Test 1, reply round-trip. Send yourself a test email from one of your InboxKit mailboxes (use the mailbox's Gmail webmail directly). Reply to it from a different address. Within 2 minutes, the reply should appear in Hothawk's shared inbox and get auto-assigned according to your routing rules. If it doesn't appear, IMAP is broken.

Test 2, rep reply from inside Hothawk. Reply to that test from inside the Hothawk UI as one of your team members. Confirm the outgoing message actually reaches the prospect inbox in <30 seconds with DKIM passing. This verifies Hothawk can use the stored SMTP credentials to send.

Test 3, pipeline state change. Move the test conversation across Hothawk's pipeline stages (New → Contacted → Replied → Interested → Closed). Confirm each move triggers the notifications you expect for the assigned rep. This isn't an integration test. It is a workflow test for your team's pipeline setup.