Supabase is becoming the default backend for a huge number of SaaS products. Auth, database, storage, realtime, all in one open-source platform. But when it comes to email, Supabase only handles the basics: auth confirmation emails, password resets, and magic links.

For everything else (onboarding sequences, product updates, dunning, lifecycle email), you need an external tool. The question is how to connect your Supabase events to your email platform cleanly.

How Supabase + Email Works

Supabase gives you several integration points for email:

Auth hooks: Trigger emails on signup, login, password reset
Database webhooks: Fire webhooks when rows are inserted, updated, or deleted
Edge Functions: Serverless functions that can call email APIs
Realtime: Subscribe to database changes (useful for real-time notifications)

The most common pattern: use Supabase database webhooks or Edge Functions to forward user actions to your email tool's API.

The 6 Best Options

1. Sequenzy

Best for: SaaS founders wanting lifecycle email triggered by Supabase events

Sequenzy's event tracking API works well with Supabase Edge Functions or database webhooks. When a user takes an action that updates your Supabase database, fire an event to Sequenzy and trigger the appropriate email sequence.

The advantage: you get full lifecycle automation (onboarding, trial conversion, dunning, re-engagement) on top of your Supabase backend without complex middleware.

Pricing: From $29/month Integration: Event API via Edge Functions or webhooks Pros: Full lifecycle automation, AI sequences, transactional + marketing Cons: Requires Edge Function setup, no native Supabase connector

2. Resend

Best for: Developers wanting the cleanest Supabase integration

Resend and Supabase are a natural pairing. Both target the same developer audience, and Supabase actually lists Resend as a recommended email provider. You can use Resend as your custom SMTP provider in Supabase for auth emails, and use the Resend API for everything else.

The React Email support means you can build templates as React components, which fits the modern development workflow that Supabase developers already use.

Pricing: Free for 100 emails/day, from $20/month Integration: SMTP for auth + API for marketing, Edge Function compatible Pros: Natural Supabase pairing, React Email, great DX, recommended by Supabase Cons: Marketing features still maturing, limited automation

3. Loops

Best for: Early-stage Supabase apps wanting simple event-driven email

Loops and Supabase share a similar developer audience. Connect them through Supabase Edge Functions that call the Loops API when users take actions. The event-driven model matches naturally.

Pricing: Free for 1,000 contacts, from $49/month Integration: API via Edge Functions Pros: Simple, modern, good free tier, event-driven Cons: Limited automation, basic segmentation

4. Postmark

Best for: Developers prioritizing transactional email delivery with Supabase

Postmark can serve as your Supabase custom SMTP provider for auth emails (giving you better deliverability than Supabase's default) and handle transactional email via API. For marketing, you'd need a separate tool.

Pricing: From $15/month Integration: SMTP for auth + API for transactional Pros: Best transactional deliverability, can replace Supabase default SMTP Cons: No marketing automation, separate tool needed for campaigns

5. Customer.io

Best for: Technical teams building complex behavioral email on Supabase

Customer.io's event API accepts events from Supabase Edge Functions. Build complex workflows triggered by any database change or user action. The most powerful option but also the most complex and expensive.

Pricing: From $100/month Integration: API via Edge Functions Pros: Most powerful automation, flexible event handling Cons: Expensive, complex, overkill for simple needs

6. Brevo

Best for: Budget-conscious Supabase projects

Brevo offers both transactional (SMTP/API) and marketing email at an affordable price. Use it as your Supabase SMTP provider for auth emails and the API for marketing sequences. The free tier (300 emails/day) works for development and early stages.

Pricing: Free for 300 emails/day, from $25/month Integration: SMTP for auth + API for marketing Pros: Affordable, both transactional and marketing, generous free tier Cons: Dated interface, less developer-focused than alternatives

Integration Patterns

Pattern 1: Supabase Edge Function to Email API

User action -> Supabase database change -> Database webhook -> Edge Function -> Email tool API

Best for: Real-time event tracking. Edge Functions process the event and forward it to your email tool immediately.

Pattern 2: Custom SMTP for Auth Emails

Replace Supabase's default email provider with your email tool's SMTP. This gives you better deliverability and consistent branding on auth emails.

Pattern 3: Scheduled Sync

Use a Supabase cron job (pg_cron) to periodically sync user data to your email tool. Good for non-real-time data like usage statistics or weekly reports.

FAQ

Can I use Supabase's built-in email for marketing? No. Supabase's email is only for auth-related messages. You need a separate tool for marketing, onboarding, and lifecycle email.

Should I replace Supabase's default SMTP? If email deliverability matters to you (it should), yes. Supabase's default email uses a shared service. A dedicated SMTP provider like Resend or Postmark gives you better inbox placement.

How do I send emails when a Supabase database row changes? Use Supabase database webhooks to trigger an Edge Function that calls your email tool's API. This pattern works for any database change (new user, updated status, new row in any table).

Is there a native Supabase email marketing integration? Not yet. Supabase focuses on backend infrastructure. Email marketing requires connecting to a third-party tool via API, webhooks, or Edge Functions.