Instantly + SalesCrew
Mirror your Instantly sender and domain registry into SalesCrew, so the accounts you warmed there sit beside the pipeline they feed. Sending through Instantly is a roadmap item.
- Registry sync, read into SalesCrew
- Send provider on the roadmap
- Native pool sends today
The short answer
- What ships today is a registry mirror: SalesCrew reads your Instantly senders and domains so your pool is visible and usable as configuration on the SalesCrew side.
- Sending through Instantly as a provider is on the roadmap. Today SalesCrew sends from its own mailbox pool over SMTP, with per-account daily caps, cooldown stamps and suppression re-checked at send time.
- SalesCrew does not do inbox warmup. If warmup is the reason you pay for Instantly, keep paying for it. The two tools are complementary rather than a swap.
Mechanism
Read this before you plan a migration, because half of it is not shipped.
| What | Mechanism | Direction | Objects | Status |
|---|---|---|---|---|
| Sender and domain registry | Mirror sync from Instantly into SalesCrew | Inbound | Sender pool, sending domains | Available |
| Sending campaigns through Instantly | Send-provider dispatcher with an Instantly provider | Outbound | Campaigns, cadence steps | On the roadmap |
| Sending today | SalesCrew's own mailbox pool over SMTP | Outbound | Campaigns, cadence steps | Available |
| Replies | Read from your connected mailboxes over IMAP, not from Instantly | Inbound | Threads, drafts | Available |
| Suppression | Enforced by SalesCrew at audience freeze and again at send | Internal | Suppression entries | Available |
| Inbox warmup | Not a SalesCrew feature at all | , | , | Not planned |
Mechanisms read from the SalesCrew integration table, September 2026. Instantly's own site is the authority on its pricing and its warmup behaviour.
Setup
Sync the registry, then decide which tool actually sends.
- 1
Add the Instantly key
Settings, integrations, Instantly. The key goes into your instance's Supabase Vault and is not displayed again. The MCP twin is integration_set_key.
- 2
Run the sync
instantly_sync mirrors the sender accounts and sending domains into SalesCrew's registry, so the pool is visible where you build audiences.
- 3
Connect the reply mailboxes
Replies reach SalesCrew over IMAP from the mailboxes themselves. Without this step you will see sends but not answers.
- 4
Import the suppression list
Before any audience is frozen. Suppression is checked at freeze and again at send, so it has to exist first.
- 5
Choose the sending path
Today that is SalesCrew's native mailbox pool. Keep Instantly for warmup, and watch the changelog for the Instantly send provider.
- 6
Turn cadences on in review
The Campaign agent is a roadmap item; today cadences run on their schedule and any agent-written step waits in the approval queue.
Questions
- Can I send my SalesCrew cadences through Instantly?
- Not yet. The send-provider dispatcher with an Instantly provider is on the roadmap. Until it appears in the changelog, cadences send from SalesCrew's own mailbox pool.
- Does SalesCrew warm up mailboxes?
- No, and it is not planned. Warmup is a real service with a real cost and pretending otherwise would set you up to burn domains. Use Instantly or your provider of choice for that.
- Why mirror the registry at all?
- So the accounts and domains you already manage are visible where audiences and caps are set, instead of living in a second tool nobody opens while planning a campaign.
- What does SalesCrew add that Instantly does not?
- A pipeline, a shared inbox, a data bank, marketing spend in the same database, and an MCP server so an agent can operate all of it. Instantly is a sending and warmup tool; SalesCrew is the CRM behind it.
- Is the sync two-way?
- No. It reads from Instantly into SalesCrew. Nothing is written back.
Keep the warmup, move the pipeline
Mirror your registry, connect the reply mailboxes, and see the replies as deals rather than rows.