Connect Resend email

For: Company admins and integration owners
Owner: Integration operations
Outcome: Test, monitor, recover, rotate, and disconnect Resend email safely.
Last verified: 2026-08-30
Next review: 2026-11-28
Status: supported

Use Resend for approved company email sending and delivery events. This guide uses the current supported Sakhaa setup surface and keeps provider-owned approval and availability separate.

Prepare the connection

Automated domain management is available for Resend. Other providers use their own domain tools.

Create a restricted Resend API key for the Sakhaa connection.
Verify the sending domain and required DNS records before using it as the default.
Configure webhook verification and run the provider test before the first campaign.

Connect and prove health

Open /app/email/settings in the correct workspace.
Save the provider api key and webhook secret only in the protected setup surface.
Use the provider test action before making the provider the default send path.
Confirm this healthy result: The provider test passes and webhook health does not report a missing secret.

Use synthetic data and an approved test identity. Do not use customer traffic only to prove a connection.

Monitor and recover

Monitor: Review provider status, default sender, domain state, webhook health, and recent failures.
Recover: Keep the current default provider active while the failed provider is repaired and retested.
Rotate: Save the replacement credential, test it, then revoke the old credential in the provider.
Disconnect: Switch the default path first. Confirm that queued and reply-tracking work will not be lost.
Limits: Automated domain management is available for Resend. Other providers use their own domain tools.
Fallback: Keep the current default provider active and use the provider failure queue until the replacement passes its test.

Support boundary

Sakhaa supports the CRM configuration and product behavior. The provider controls account approval, billing, quotas, and external service availability.

Record the provider, workspace, approximate time, safe error code, expected result, and actual result.
Do not include passwords, access tokens, API secrets, message content, or unnecessary customer data.