Outreach & Warmup

Connect a cold-email platform to SpiderMail and you get one deliverability view across every sending account, plus a way to push verified leads into a campaign. This page covers connecting a provider, reading sender health, the warmup behaviour that catches people out, and where deliverability problems actually come from.

What you can connect

SpiderMail holds brand-scoped connections to three platforms: Smartlead, lemlist and Instantly. A connection is scoped to a brand. Reads work with a standard access token; writes require brand-admin.

Connecting does not move your sending. Campaigns keep running in the platform you already use. SpiderMail reads the sending accounts behind the connection and keeps them in sync.

Connect a provider

Add the provider API key as an integration, then create the connection for your brand. Once it exists, run a sync to pull the current sending accounts:

POST /api/v1/brands/{brand_id}/mail/outreach/connections/{connection_id}/sync

Sync is safe to re-run. It refreshes the sending accounts and their warmup state from the provider.

Read sender health

Three reads cover the whole surface:

• List senders — every sending account across the brand's connections, with its provider, whether warmup is enabled, its status, and the local mailbox it matches.

• Sender health — one account's latest snapshot: health score, sent / inbox / spam / bounce / reply counts over 24 hours and 7 days, and when it was last polled.

• Health overview — the same snapshot for every sending account at once. This is the grid to check first.

A warmup trend endpoint is also available, so you can read direction over time instead of a single day's number.

Warmup pauses itself and does not resume

Warning: Warmup auto-pauses after persistent domain failures, and it does NOT switch itself back on. A paused warmup and a working one look the same from the outside — check status, not appearances.

Re-enable warmup only after the domain is healthy again. Fix the underlying domain problem first, or it will pause again.

One detail that costs people time: the blocked-reason text on a paused account is stale. It keeps the original message, with its original date, until the next successful warmup cycle. Trust the ACTIVE / INACTIVE status, not the reason string.

Push verified leads into a campaign

A SpiderIQ campaign's verified leads can be pushed into a Smartlead campaign you choose. List the remote campaigns to pick one, then push.

Three properties matter in practice. The push is idempotent, so an email already pushed to that connection and campaign is skipped rather than duplicated. It is quota-aware: if the push would exceed the account's lead cap it fails with a clear error, and passing a limit trims to the available headroom instead. And it is reversible — removing leads frees the account's lead credits back up.

Check available headroom and per-campaign counts before a large push with the push-status read.

Choosing a push filter

Two opt-in filters restrict the push: only leads carrying a VayaPin pin, or only leads carrying a VayaPin SEO article. Set both and they combine — a lead must have both to qualify.

These are not equivalent in practice. Across 52 restaurant lead campaigns totalling 9,322 verified leads, measured 9 August 2026, 64.2% carried a pin and 18.8% carried an SEO article; the pin filter qualified more leads in 32 of those 52 campaigns. For pin-centric outreach, the pin filter is the correct gate. Measure your own campaigns before assuming the same ratio.

Where deliverability problems actually come from

This surface reports deliverability. It does not fix it, and most failures you see here originate outside SpiderMail. Two common ones look similar and have different owners:

• A domain_does_not_exist or NXDOMAIN warmup bounce is a DNS problem. Fix the zone at your DNS provider.

• A 553 Relaying disallowed error while DNS is healthy is your mail host blocking the domain — typically because domain ownership needs re-verifying there. Inbound mail keeps working, which is why this one hides.

Note: An SMTP probe that stops before the DATA stage returns 250 even when the domain is send-blocked. To confirm a sender can really send, send a real message — a note to an internal address on the same domain is a safe check.

For agents

The outreach surface is available to agents through the mail skill, over both the CLI and MCP: list and inspect connections, update or remove one, sync a provider, list senders, read one sender's health or the whole brand's, and run or reverse a lead push.