Operations & Internal Tools
Connect Supabase and Resend
Each email sent once from your own domain, with the delivery record stored.
- Data flows
- 4 automated, two-way where safe
- Built with
- Supabase Postgres, Resend API, Supabase Auth SMTP
- Timeline
- Live in 2 to 8 weeks from scope
- Owned by
- You, with accounts, credentials and code in your name.
Connecting Supabase to Resend lets your app send reminders, alerts and sign-in emails from your own domain, and store what happened to each one. SBD runs this in production: a Supabase-backed operations tool sends a daily reminder digest through Resend, and another platform uses Resend as custom SMTP for Supabase Auth.
What runs between Supabase and Resend
Each line is one automated workflow, with the same checks, logs and alerts on all of them.
-
Daily reminder digest per person
WhenThe daily scheduled job runs
ThenGather every reminder due today and send one Resend digest per person, recording each send first
-
Invites and alerts from app events
WhenA row is inserted that needs an email, such as an invite
ThenA database webhook or server action calls Resend with an idempotency key
-
Sign-in links from your own domain
WhenA user asks for a sign-in link
ThenSupabase Auth sends it through Resend as custom SMTP, from your domain
-
Bounces and complaints stored back
WhenResend reports delivered, bounced or complained
ThenVerify the webhook signature and store the event against the send in Supabase
Where the simple setup breaks down
A one-step Zap connects Supabase and Resend in an afternoon. This is what goes wrong once volume grows.
A retried job sends the email twice
Scheduled jobs get retried. Resend accepts an Idempotency-Key header, keeps it for 24 hours, and returns the original response for a repeat. Our reminder job also records every send under a unique key before sending, so a rerun after a failure cannot produce a second copy.
The built-in Supabase email is not for production
Supabase Auth’s default email service only delivers to members of the project team and is limited to 2 messages an hour. Supabase says it is not meant for production and that real users need custom SMTP. Resend is one of the providers it lists.
One read stops at 1,000 rows
The Supabase Data API returns at most 1,000 rows per request by default. A reminder job that reads its table once quietly skips everyone after row 1,000. Our job reads a page at a time and stops the run if any page fails, rather than reminding part of the list.
The rate limit is per team, not per key
Resend allows 10 requests a second per team by default, shared across every API key. A nightly run that sends one email per record can hit 429s. Sending one digest per person, as our reminder job does, keeps volume low and the inbox readable.
The problem, from both sides
In the team
- Reminders depend on someone remembering to send them
- Sign-in emails never reach real users
- People get the same reminder twice after a retry
- Nobody knows an email bounced
- A dozen separate emails a day instead of one list
Under the hood
- Default Supabase Auth email limited to the team, 2 an hour
- 1,000-row default cap on Data API reads
- 10 requests a second per Resend team
- Idempotency keys kept for 24 hours
- Webhook signatures need the raw body
Used for
- Daily reminder digest per person
- Invites and alerts from app events
- Sign-in links from your own domain
- Bounces and complaints stored back
- Supabase transactional email
- Resend custom SMTP for Supabase Auth
- Scheduled email from Postgres
- Idempotent reminder emails
- Email delivery tracking in Supabase
- Website form notifications
Built with
- SPSupabase Postgres
- RAResend API
- SASupabase Auth SMTP
- SCSupabase Cron
- SDSupabase Database Webhooks
- VCVercel Cron
Which fields map to which
Agreed in the blueprint and written into the runbook. Two-way rows carry loop protection, so a write from the sync never sets it off again.
- Reminders due today, by assignee one-way→ One digest email per person Assignee and date
- Sent reminders ledger one-way→ Idempotency key on the send Entity, reminder kind and due date
- Auth sign-in and invite events one-way→ Email through Resend SMTP User ID
- Delivery events table one-way→ Delivered, bounced and complained webhooks Resend email ID
Standards on every build
Validation, retries, reconciliation, audit logs and alerts come as standard, with credentials and accounts in your name. Read the integration standards
Where we have done this
- 9 modules in one tool
Internal operations tool replacing SmartSuite
The Supabase-backed operations tool sends a daily reminder digest through Resend, one email per person, with each send recorded so a retry never duplicates it.
Read the story → - 11 product areas in one platform
AI outbound sales platform
Resend carries the platform’s own mail on a Supabase stack, including sign-in links through custom SMTP, invites, alerts and scheduled reports.
Read the story →
What people ask about this pair
Where should the scheduled job run?
Either works. Supabase Cron is built on pg_cron, can call an Edge Function over HTTP, and records each run in cron.job_run_details. Our reminder job runs on Vercel Cron next to the app. What matters is that the job is safe to run twice and alerts when it fails.
Do we need our own domain?
Yes. Resend sends from a domain you own and have verified. Setting it up is part of the build, and it is what lets reminders and sign-in links arrive from your name rather than a provider address.
How do we know an email arrived?
Resend sends webhooks for events such as email.delivered, email.bounced, email.complained and email.delivery_delayed. We verify the svix signature headers against the raw request body, then store the event against the send, so a bounce becomes a visible fix rather than a silent gap.
Does SBD use Resend itself?
Yes. The forms on this site deliver submissions to our inbox through Resend, and it is listed on our trust page as a subprocessor.
Related pairs
-

Retool and Supabase
Screens in Retool, data in a Postgres database you own and can expose safely.
-
n8n and QuickBooks
Bookkeeping workflows you can read, own and rerun, posting to the QuickBooks file your accountant trusts.
-

HubSpot and Slack
Fewer, fuller notifications, sent to the person who has to act on them.
- Solution
Operations
The workflows we automate for this kind of team.
App email sent once from your domain, with delivery events stored
Scheduled digests, event emails and sign-in links from your Supabase app through Resend, with idempotent sends and delivery events stored back, live in 2 to 8 weeks.
Start with a discovery call










