Sequencers, CRMs, warmup networks, analytics and enrichment connect with scoped access in minutes. If nothing here fits, the REST API underneath is the same one every connector uses.
Find the connector for your stack
Search by name or description, then narrow by category and rollout status.
24 integrations
Cadence
Multi-step outbound sequences with per-mailbox send-rate limits.
Reachpilot
Sequence builder with reply detection and auto-pause on bounces.
Waypost
Territory-based sequencing for distributed SDR teams.
Fernwave
Conversation-style sequences that branch on intent signals.
Cascadia Reach
Account-based sequencing with shared calendars across a pod.
Northloop CRM
Pipeline CRM that syncs every send, open and reply back to the deal.
Signalcrest
Lightweight CRM built around lifecycle stages and owner routing.
Lucent CRM
Revenue CRM with custom objects for multi-product pipelines.
Meridian CRM
CRM for agencies managing pipeline across many client accounts.
Beacon Warmup
Peer-network warmup with configurable ramp curves per mailbox.
Groundwire
Warmup scheduling that adapts to your existing send volume.
Sparrowhold
Slow-ramp warmup profiles tuned for brand-new domains.
Vantage Grid
Cross-mailbox deliverability dashboards with blocklist alerts.
Kestrel Analytics
Cohort reporting on inbox placement, spam rate and reply rate.
Tallow Analytics
Attribution reporting that ties opens and replies to pipeline.
Glasswing
Executive rollups of fleet health across every workspace.
Tessera
Contact and company enrichment with verified role-based email.
Hallmark Data
Firmographic enrichment with technographic signals included.
Ironvale
Real-time waterfall enrichment across multiple data sources.
Copperlane
Intent data enrichment layered onto existing contact records.
Orbitline
No-code workflows that trigger on any fleet or deliverability event.
Pipeworks
Automation canvas for routing leads between tools on a schedule.
Driftline
Event-driven automations with built-in retry and audit logs.
Nettleform
Rules engine for pausing sequences the moment health drops.
Connector, webhook or raw REST: one permissions model
Native connectors for the tools you already run, signed webhooks for anything event-driven, and the REST API that both of them sit on.
Native connectors
Sequencers, CRMs and warmup networks connect over scoped OAuth: no code to write, and revocable from your workspace at any time.
Signed webhooks
Six fleet events post to your endpoint as they happen, signed so you can verify the sender. Nothing sits on a timer.
REST underneath all of it
Every action the console can take is an HTTP endpoint, authenticated with one key you can rotate whenever you want.
No connector yet? It is one REST call away
Every action the console can take is a documented endpoint: buy a domain, generate a mailbox roster, subscribe to fleet events.
# create a mailbox on an existing domain
curl https://api.infrabox.software/v1/mailboxes \
-H "Authorization: Bearer $INFRABOX_KEY" \
-H "Content-Type: application/json" \
-d '{"domain":"sendwith.io","local_part":"mia","warmup":"standard"}'{
"event": "mailbox.provisioned",
"created_at": "2026-08-27T14:02:11Z",
"data": {
"mailbox_id": "mbx_7f2ad91c",
"domain": "sendwith.io",
"address": "[email protected]",
"warmup_status": "scheduled"
}
}Six events cover the whole fleet
Subscribe once and every change arrives as a signed POST. Nothing in your pipeline has to poll.
domain.verifiedDNS verification finishes for a sending domain.
mailbox.provisionedA mailbox is created and cleared to send.
warmup.completedA mailbox reaches the end of its ramp curve.
deliverability.alertPlacement or reputation crosses a threshold you set.
message.bouncedA send returns a hard or soft bounce code.
domain.blocklistedA monitored blocklist starts listing one of your domains.
A connection is three steps and one scope
Access is narrowed at the moment you grant it, and revocable the second you change your mind.
Step 1: Pick the tool
Choose a connector from the directory, or generate an API key if you're building your own.
Step 2: Grant a scope, once
Hand it domains, mailboxes or events only, never the whole workspace, and never a password.
Step 3: It syncs until you revoke it
Sends, replies and health events move in both directions, and access ends the second you pull the key.
Missing a tool? The endpoint for it already exists
Start free, provision a fleet, and wire it into whatever your team runs now or switches to later.
