Email · One key, and a webhook that tells you what happened

Connect your own Resend account

A developer-first mail API. The connection needs a single key, and the provider reports delivery and inbound mail back over a signed webhook — which is the only email path where the console can show you what happened after acceptance.

Add a Resend connectionAll integrations
Scope. This integration sends Email. Delivery events come back through the provider’s webhook and are normalized into the same three statuses as SMS, so a delivery reads the same way whichever channel carried it. Routing and automatic failover, per-number pacing and segment accounting are SMS-channel features rather than Email ones: a Email send goes out on the single connection you configure. Opt-out suppression is applied to marketing sends on every channel. Whaleal Platform is a message orchestration layer: it calls Resend’s public API using your account. We do not resell message volume, do not mark up your Resend bill, and do not own your account.

What you need from Resend

Gather these in the Resend portal first. The connection form asks for exactly these fields and nothing more.

FieldWhat it is
apiKeyAPI Key. From the Resend dashboard. A sending-scoped key is enough.
webhookSecretoptionalWebhook signing secret. Only needed if you want inbound replies and delivery events to reach the console. Find it under Webhooks → that endpoint → signing secret.

Credentials are sealed with AES-256-GCM and the console only ever shows a masked value afterwards. Plaintext is never written to logs and never sent back to the browser.

What we configure on the connection

  • Sender address (From). The address your mail goes out as. It must sit on a domain verified in your Resend account.
  • Default send pacing: 10 messages per second. This is a conservative starting point, applied per connection, and you can change it at any time. Your real ceiling is set by Resend — check your account quota and raise the value to match.

Why teams pick Resend

  • A single API key to connect
  • Signed webhooks, so inbound mail is verified rather than trusted
  • Delivery events normalized into the same statuses as SMS
  • Domain verification stays in your own Resend account

Worth knowing

  • You provide the From address as part of the connection, not per send — every send on this connection goes out as that address.
  • Without the webhook signing secret the console rejects inbound events, so replies and delivery updates never appear.

What stays on your side

These are yours to hold — and that is the point of bringing your own account: the relationship, the rates and the compliance stay in your name, not ours.

  • Account approval and billing terms
  • Domain verification, plus the SPF and DKIM records for the domain you send from
  • Sender reputation, and any blocklist remediation that follows from it
  • The quotas and rate limits Resend grants your account

Next

Whaleal Platform currently offers self-service connections to 6 SMS providers, 4 email providers and 3 WhatsApp providers. Underlying the SMS channel is an SMS adapter library of 33 adapters; the ones outside this list are unlocked on request rather than self-service.

Add the connectionHow Whaleal Platform works