Supabase SMTP with Brevo for Auth emails
Swap Supabase's built-in email sender for Brevo SMTP for confirmations, magic links, invites and password resets. Send everything else from Edge Functions through the Brevo API.

Why use Brevo as your Supabase SMTP
What you can build with Supabase and Brevo
- Auth emails: Supabase Auth → Brevo SMTP → your users' inboxes
- Delivery events: Brevo webhooks → your Edge Function → Supabase
Deliver every Supabase Auth email
Confirmations, magic links, one-time passwords, invites and password resets go out through Brevo SMTP to any address. As Supabase recommends, keep promotional content out of these emails.
Send email from Edge Functions
Edge Functions cannot open outgoing connections on ports 25 and 587, so send with the Brevo API instead: a POST to /v3/smtp/email with your key in the api-key header. Store the key with supabase secrets set and read it with Deno.env.get. A 201 response returns a messageId.
Get delivery events back in Supabase
Brevo transactional webhooks report 15 email events, including delivered, opened, clicked and hard bounced. Point one at an Edge Function, turn off verify_jwt for it and verify the calls yourself. An account can have up to 40 webhooks.
Send from a database trigger
With the pg_net extension, a Postgres trigger can call your Edge Function, which then calls the Brevo API. pg_net is in beta, sends JSON bodies only and starts requests after the transaction commits.



