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.

Database-driven email means your app’s database decides when an email should send. It is one part of Dreamlit’s broader model: an end-to-end AI email platform for auth, transactional, broadcast, recurring, lifecycle, and internal notification workflows.

​
Why does this matter?

Most important app emails are conditional. They are not just “send this template now.” A welcome flow might need to:
  1. Send an email when a user signs up
  2. Wait 3 days
  3. Check whether the user activated
  4. Send a reminder only if they still need help
That logic belongs close to the data that proves what happened. Your database already knows the signup time, activation state, plan, usage, and payment status.

​
The old way

Traditional email setup usually spreads responsibility across several places:
  • app code calls an email API
  • cron jobs wake up and query for reminders
  • marketing tools sync user data on a schedule
  • templates live in another system
  • test sends use mock data instead of real rows
This can work, but the workflow becomes hard to see. The more conditional the email gets, the more places you need to check before you trust it.

​
The database-driven way

With a database-driven workflow, the database event or query is the starting point. This is useful for:
  • auth emails like confirmation, password reset, and magic link emails
  • transactional emails like receipts, order updates, and account alerts
  • lifecycle emails like onboarding, trial reminders, and reactivation nudges
  • recurring emails like weekly digests and monthly reports
  • internal alerts like high-value signups or failed payments

​
Where this fits in Dreamlit

Dreamlit connects to Supabase or Postgres, understands your schema, and builds workflows from plain English. The workflow can trigger on database events, wait, query current state, and send email or Slack messages. Database-driven workflows are not the whole product. Dreamlit also gives you one place to manage Supabase Auth emails, broadcasts, recurring emails, branded templates, delivery, previews, and workflow iteration. That means you can write prompts like:
  • “Welcome new users, wait 3 days, then remind anyone who has not activated.”
  • “Send a usage-limit warning every morning to customers above 80 percent of their plan.”
  • “Send a receipt when a payment row is created.”
  • “Announce a product update to active customers on the Pro plan.”
You can preview the workflow with live database rows before publishing.

​
When should you use this approach?

Use database-driven email when the message depends on app state. If the email needs to know what a user did, did not do, bought, reached, missed, or became eligible for, the database should probably be involved. Use Dreamlit when you want that data-aware workflow to live alongside templates, delivery, previews, AI editing, broadcasts, recurring schedules, and auth email setup.

​
Learn next

Supabase email

Learn the most common Supabase email paths and limits.

Database-triggered email

Read the glossary definition.