ConnectWiz + Resend
Live integrationCampaigns through your own Resend — consent checked, replies come home
The developer-grade sender, without writing the sending code. Your list, your sender reputation, your negotiated terms — ConnectWiz adds the audience brain and the inbox that catches replies.
Email marketing
What it does — precisely
Your key, tested live
The Resend API key is encrypted at rest and probed with a real connection test at setup — a dead key fails at connect, not at send time.
Audiences with a spine
Campaign audiences require an explicit marketing opt-in and exclude opt-outs automatically — built from the same CRM tags and segments everything else uses.
Replies come home
Answers to campaigns land in the shared inbox as routed conversations — a newsletter reply is a sales conversation, and blast tools drop exactly those.
No markup on traffic
Resend bills you directly on your own plan; ConnectWiz adds no per-mail toll on top.
Under the hood
The audience contract
Opt-in is structural
An audience can only contain contacts with an explicit marketing opt-in and no opt-out on record — the filter isn’t a checkbox you might forget; it’s the query itself.
Preview equals send — verbatim
The audience filter is one shared definition used by both the preview and the send. A filter the preview accepted is a filter the send accepts — the operator never composes against one contract and submits against another.
Filters with real reach
Tags with any/all matching, contact type, custom-field conditions (equals, contains, greater/less, not-empty) on your own field definitions, and last-interaction windows — segmentation from the CRM you already maintain.
Broadcasts, the native way
Sends create Resend Broadcasts against your audiences — the primitive Resend built for exactly this — with send-now or a scheduled time, status readable back.
Tracking a moving API
Resend is mid-rename from Audiences to Segments; this integration pins the stable endpoints and owns that mapping in exactly one place — when Resend moves, one file moves with it, not your campaigns.
Setup
How it connects
Add your API key
Paste your Resend key; it’s encrypted and verified with a live test.
Build the audience
Tags, types and opt-in state — with the recipient count visible before you commit.
Send and converse
The campaign goes out through your account; replies arrive back as conversations.
Better together
What it composes with
The CRM
Audiences build from the same contacts, tags and segments your support and sales work maintains — not a second list to keep in sync by hand.
The inbox
Replies land as routed conversations in the shared inbox — a newsletter answer becomes a sales thread, not a lost mailbox item.
İYS (Türkiye)
Where enabled, the consent registry integration keeps Turkish traffic registry-clean — grants push out, registry opt-outs pull back daily.
Security & guarantees
The boring guarantees
Keys encrypted, verified live
Connecting lists your Resend audiences with the key — proof of both authentication and permission in one call. The key is encrypted at rest and never rendered back to the screen.
Consent with evidence
Every opt-in carries its evidence — the text shown, a version digest, time, source, IP — so "they agreed" is a record, not a recollection.
Secrets stay out of errors
Provider errors are surfaced with their real reason but scrubbed of credentials — an exception never becomes a leak.
The honest fine print
Boundaries, stated
Engagement stays in your ESP
Delivery is tracked here; open and click analytics live in your Resend dashboard where they’re native — we link out instead of duplicating them badly.
No list scraping
Audiences build only from contacts your own workspace holds with explicit opt-in — the integration will not import, buy or infer recipients from anywhere else. A smaller honest list outperforms a bigger borrowed one, and it’s also the only legal kind.
Connected honestly beats connected loudly.
Every integration here is described by what it really does — direction, ownership and limits included.