One email provider is active at a time. Authdog's managed provider sends until you connect another and it becomes active.
Prepare the domain
In Resend, verify the domain you will send from and publish the SPF and DKIM records Resend gives you. Add a DMARC policy before you send production mail. Authdog does not verify domain ownership for you. A domain Resend has not verified still fails at send time.
Create an API key scoped to sending. It starts with re_.
Connect Resend
In the Authdog console:
- Select the project and environment.
- Open Notifications > Providers.
- Select the Email channel.
- Choose Resend and select Connect.
- Enter the API key and the From email (for example
[email protected]). - Save. A newly connected provider becomes active.
- Select Test, enter a recipient outside your own domain, and confirm delivery.
The API key is encrypted and is not loaded back into the browser. On a later edit, leave it blank to keep the stored key. Enter a new value only to replace it.
Use Set active if you connected Resend but another provider is still in use. Use managed returns delivery to Authdog.
Set the visible From name and Reply-to under Notifications > Configuration. Those defaults apply to every template, independent of which provider sends.
Test it
- Send the provider test and inspect the message headers for SPF and DKIM.
- Trigger a real template, such as a magic link or an invitation, in the same environment.
- Confirm the send appears under Notifications > Events.
Use a separate Resend key and from-address for production. Provider configuration does not copy between environments.
Related
| Read | To learn how to |
|---|---|
| Email providers | Active provider, tests, and sender-domain checks |
| Notifications | Templates, from name, and the Events tab |
| Marketplace | The listing for this integration |