Built in · always on

Resend and Conduyt

Resend is the email delivery layer built into Conduyt. It is platform-native and always on, with per-tenant sending domains and per-user senders rather than one shared account-wide address.

Start a free trial → All integrations

Integration type

Platform-native

Setup time

~10 min

API key

Not needed

Extra cost

// how it connects

Conduyt

deal · contact · template

Resend

built-in delivery layer

Inbox

replies route back

from your domainas the individual repSPF · DKIM · DMARC enforcedbounces auto-handled

How it works

What makes it different

Nothing to install

Email sending in Conduyt runs on Resend as part of the platform. There is no app to connect and no key to rotate.

Your domain, not ours

Per-tenant sending domains mean email leaves from your domain instead of a shared platform domain.

Reps send as themselves

Per-user senders mean replies land with the right person and deliverability tracks to real identities.

Before you start

What you need in place first

✓

DNS access for the sending domainYou need to be able to add SPF, DKIM and DMARC records wherever your DNS lives. Sends are held until those verify rather than falling back to a shared domain, so DNS access is a hard prerequisite and not a later step.

✓

The domain you want replies to land onMail leaves from your domain rather than a platform domain, so decide which domain your prospects should recognise before you authenticate anything. Changing it later means authenticating again.

✓

One address per repSenders are per user, so have the person to address mapping ready before you start. A shared alias will work, but it gives up the reply routing and the per-identity reputation that make this worth doing.

✓

Nothing to buyThere is no second subscription, no API key to store and no add-on line item. Sending is part of the $299 per month plan, which includes unlimited users with no per-seat fees.

Data flow

What moves, and which way

Direction	What moves	Notes
Conduyt to Resend	The rendered message: sender identity, recipient, subject and body, built from a Conduyt template, a sequence step, or a one-off send from the contact record.	Outbound only. Inbound parsing and reply threading are handled by Conduyt email sync, not by this layer.
Resend to Conduyt	Delivery lifecycle events. Resend publishes email.sent, email.delivered, email.bounced, email.complained, email.opened and email.clicked among its webhook event types.	Vendor source: Resend webhook event types.
Resend to Conduyt	Suppression state. Resend documents that an address is added to your suppression list automatically after a hard bounce or a spam complaint.	Same source. It is why bounce handling does not need a hand-maintained list on the Conduyt side.
Your DNS to the receiving server	SPF, DKIM and DMARC lookups at delivery time, made by the recipient's mail provider rather than by either product.	Nothing leaves Conduyt on this leg. It is the reason authentication has to finish before the first campaign, not during it.

Setup

3 steps, about ten minutes

Add your sending domain

Settings, then Email, then Sending domains. Paste the domain you want reps sending from.

~1 min

Complete DNS authentication

Add the SPF, DKIM and DMARC records we generate. Verification is usually near-instant once DNS propagates.

~5 min plus propagation

Assign per-user senders

Map each rep to their own address so outbound and replies both resolve to them.

~2 min

Because this is platform-native rather than a connected app, there is no separate Resend subscription to manage and no API key to rotate.

Honest limits

What it does not do

You cannot connect your own Resend accountSending runs on Conduyt's platform integration. If you need to keep an existing Resend workspace billing separately, this is not that.

No separate Resend dashboardDelivery, bounce and complaint data surface inside Conduyt reporting rather than a second console to log into.

It does not warm your domainA brand-new domain still needs a ramp. Pair it with Warmy for inbox warmup.

Outbound onlyInbound parsing and reply threading are handled by Conduyt's email sync, not by this layer.

Specifications

The details

Sending domains

Per-tenant, unlimited

Senders

Per-user addresses

DNS records

SPF, DKIM, DMARC

Bounce & complaint handling

Automatic, surfaced in reporting

Templates

Conduyt-native editor

Included in plan

Yes, no add-on

FAQ

Common questions

Do I need my own Resend account?

No. Sending is platform-native, so there is no separate signup, no subscription to manage, and no API key to store or rotate.

Can I use a different email provider?

Outbound sending runs on the built-in layer. If you need a specific provider for compliance reasons, talk to us before migrating. We would rather tell you no up front than after you switch.

Does this help or hurt deliverability?

It helps, for two structural reasons: mail leaves from your own authenticated domain, and each rep sends from their own address instead of one shared alias that accumulates reputation damage.

What happens before DNS is verified?

Sends are held rather than sent from a fallback domain. That is deliberate. Sending unauthenticated mail to warm up a pipeline is how domains get burned.