Skip to main content

Documentation Index

Fetch the complete documentation index at: https://notikaai.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Supabase is a great place to build your app. Email is where many teams discover the gap between a working prototype and a production-ready product. In development, the default Supabase email sender can be enough to test signups and password resets. In production, you need reliable delivery, branded templates, correct redirect URLs, and workflows that can respond to live app data.

​
The common Supabase email paths

​
Supabase Auth emails

These are emails Supabase sends for authentication events:
  • email confirmation
  • password reset
  • magic link
  • invite
  • email change
  • reauthentication
Supabase’s built-in sender is not meant to be your production sender. For production apps, you need to configure a real email path.

Set up Supabase Auth emails

Follow the Dreamlit setup guide for branded Supabase Auth emails.

​
App-triggered transactional emails

These emails come from product events, like a new order, payment, comment, invite, or status update. You can send them from app code with an email API. That works, but the workflow logic now lives inside your app. If the email needs waits, follow-up checks, or recurring queries, the code can get messy quickly.

​
Scheduled and lifecycle emails

These emails usually need queries:
  • trial ending reminders
  • usage limit warnings
  • abandoned onboarding nudges
  • weekly digests
  • renewal reminders
Many teams solve this with cron jobs. Dreamlit solves it with workflows that query your Supabase database, wait, check current state, and send only when the data still matches.

​
What Dreamlit handles

Dreamlit handles the end-to-end email layer for Supabase apps:
  • connects to your Supabase database
  • creates Supabase Auth email workflows
  • generates branded templates
  • watches database events
  • runs queries for recurring or conditional workflows
  • supports broadcasts and product updates from the same workflow system
  • previews sends with live rows before publishing
Your app still owns the product experience:
  • signup and login screens
  • calls to Supabase Auth APIs
  • redirect URL configuration
  • callback routes and deep links
  • user consent and email preferences
That split matters. If an email arrives but the link does not sign the user in, Dreamlit delivery is working. The next place to check is your Supabase redirect settings and app callback handler.

​
What should you build first?

For most Supabase apps, start with:
  1. Auth emails: confirmation, magic link, and password reset
  2. Activation email: welcome users and guide the first important action
  3. Follow-up check: wait a few days, query the database, and remind users who did not activate
  4. Critical transactional emails: receipts, account changes, and important alerts
  5. Recurring digest or warning: send a useful report or usage limit warning from live rows
If you are not sure what your app needs, use the Email Workflow Planner.