Connect InboxKit Mailboxes to Za-Zu in Under 4 Minutes

Za-Zu connects via standard credential handoff in the InboxKit Sequencers Connect screen. Paste your Za-Zu login email and password, click Connect Account, and InboxKit pushes every selected mailbox into your Za-Zu account for use in sequences. The actual connect completes in about 90 seconds. There is no API key, no workspace dropdown, and no multi-step validation. Za-Zu uses the simplest flow of any sequencer in the InboxKit catalog.

This is the integration to pick if you are a Clay user doing AI personalization at scale and you want real Google Workspace or Microsoft 365 mailboxes (not shared-IP mailboxes) as the sending layer underneath Za-Zu's sequences.

Za-Zu markets itself as 'the outreach tool Clay users pick.' The reason: Za-Zu accepts data directly from Clay tables, runs AI-personalized first touches, and supports multi-account management across many senders. What Za-Zu does not do is provision mailboxes for you, so you bring your own.

For Clay-heavy workflows, the typical stack is Clay → Za-Zu → InboxKit mailboxes. Clay hydrates the prospect rows, Za-Zu writes the AI first touch, InboxKit sends from a real mailbox. Each tool owns one layer of the pipeline and none of them overlap.

Before clicking Connect in InboxKit:

The IMAP-at-OU prerequisite. Za-Zu reads replies via IMAP, same as Instantly and Salesforge. If IMAP is disabled for the OU that contains your InboxKit mailboxes, Za-Zu will show zero replies even though sending works fine. Fix by enabling IMAP in the Google Workspace admin console before you connect. It takes 30 seconds and saves a half-hour of post-connect debugging. For a complete checklist of these Google Workspace admin prerequisites, see the cold email domain setup checklist.

The clean path from InboxKit dashboard to a connected Za-Zu account:

Total: about 90 seconds.

Za-Zu does not require a separate workspace selection step (unlike Master Inbox) and does not use a custom API-key validation flow (unlike BrandJet or Supersend). It is the most direct credential flow in the catalog.

If you are pairing Za-Zu with Clay, the workflow after the InboxKit connect looks like this:

Step 1: Inside Clay. Build or import your prospect table. Add enrichment columns (company description, recent news, pain points) using Clay's built-in providers.

Step 2: Inside Za-Zu. Connect the Clay table to a Za-Zu sequence. Za-Zu reads each row as a prospect, pulls the enrichment data, and generates the AI first touch.

Step 3: Inside Za-Zu. Assign the sequence to a mailbox pool. This is where your InboxKit mailboxes live now, and they show up as a dropdown after the connect step above. Pick the pool you want for this campaign.

Step 4: Launch. Za-Zu starts sending via the mailboxes' SMTP credentials, paces according to your daily limits, and routes replies into Za-Zu's inbox for you to handle.

The hand-off points are clean. Clay owns the data and enrichment. Za-Zu owns the AI writing and the sending orchestration. InboxKit owns the actual mailbox, the thing Gmail and Outlook see on the other end. Each tool handles exactly one layer.

Set these inside Za-Zu after the import completes:

Za-Zu does not ship its own warmup product. If you want warmup on these mailboxes, use one of:

• InboxKit isolated warmup add-on: $3/mailbox/month, separate peer network, stays with the mailbox regardless of which sequencer you use
• Third-party warmup tool: TrulyInbox, Warmy, MailToaster, or Warmforge

Pick one. Do not run two warmup engines on the same mailbox. It roughly doubles warmup-sent volume and confuses reputation signals at Gmail Postmaster. See email warmup tools comparison for a deeper look at each warmup engine.

The failure modes you are likely to hit:

On Clay-specific errors: Za-Zu connects to Clay via webhook, and that connection is maintained inside Za-Zu, not inside InboxKit. If your Clay integration breaks, that has nothing to do with the InboxKit mailbox side. It is a Za-Zu ↔ Clay issue. Check Za-Zu → Integrations → Clay → Webhook Status first before touching anything on the InboxKit side.

Smoke test every new Za-Zu connection:

Test 1: send test email from one mailbox. In Za-Zu → Mailboxes → (pick one) → Send Test. Confirm delivery <30 seconds.

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

Test 3: one-prospect pilot sequence. Before loading 500 prospects, run a 1-prospect test sequence end-to-end. You are verifying that Za-Zu's AI generates a reasonable first touch, sends it from the InboxKit mailbox, and logs the event correctly. If all three work, scale the sequence.

Test 4: inbox placement test. Send a seed-list test (Gmail, Outlook, Yahoo, Hotmail). Target: 9/10+ score. Below 8/10 means something in the DNS or warmup layer needs work. See inbox placement testing explained for the full methodology and common failure modes.