Resend

Available

Send customer email through Resend with your own verified domain, and have replies come back into your Botvee Inbox.

What you need

Your own Resend account with a verified sending domain — Botvee does not send through ours
An API key from the Resend dashboard
An AI Agent created in Botvee

Step 1 — Connect the account

1
Open Dashboard → Integrations → Resend
2
Click Add email account and choose Resend
3
Enter the from address
it must be on your verified Resend domain
4
Enter the from name customers will see
5
Paste your Resend API key
6
Click Connect & verify

Botvee checks the key immediately, so a wrong or revoked key is caught here rather than on your first customer email.

Tip

Send yourself a test email from the account row before going further. It proves the domain, key and from address all agree.

Step 2 — Receive replies in your Inbox

Sending works on its own. Receiving needs three things: an inbound route in Botvee, Resend pointed at your account's webhook URL, and that webhook's signing secret saved in Botvee.

1
In the same dialog, under Receive into your Inbox, enter the address customers email and pick the AI Agent that should answer it
2
Save the inbound route
3
Copy the inbound webhook URL shown on your Resend account row
it is unique to that account
4
In your Resend dashboard, set that URL as the inbound endpoint
5
Copy the signing secret Resend shows (whsec_…) and paste it back into Botvee with “Add signing secret”
6
Send a real email to the address and watch it appear in Dashboard → Inbox

Note

The webhook URL is per account, not one shared URL. Your Resend account signs deliveries with your own secret, so Botvee needs to know which account a delivery claims to be from before it can check the signature.

Customer emails you

Resend inbound

Signature verified

Inbox conversation

Your team replies

What Botvee does with a received email

Saves it as an Inbox conversation, so your team can see and answer it
Threads follow-ups onto the same conversation instead of creating new ones
Replying from the Inbox emails the customer on the same thread
Duplicate deliveries and Resend retries are ignored, so a customer never gets answered twice

Safety built in

Every inbound delivery is checked against your account's own signing secret — an unsigned, forged or replayed request is rejected
Deliveries older than five minutes are refused, so a captured request cannot be replayed later
Bounces, vacation responders and mailing-list traffic are stored but never auto-answered, so two robots cannot loop
Auto-replies are capped per thread
Your API key and signing secret are encrypted at rest and never shown again after saving

Notes

An address can belong to only one Botvee workspace
Sending from an unverified domain will be rejected by Resend, not by Botvee
Without a signing secret, inbound on that account is refused rather than trusted — sending still works