Learning Center

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.

Most email platforms make you stitch the product together yourself. One tool sends transactional email, another handles broadcasts, another manages lifecycle messages, and your app code still owns the logic that decides what should happen. Dreamlit is built to be all-in-one and end-to-end. It helps you create the workflow logic, audience rules, timing, templates, delivery, and previews in one place, with AI that can use the full context of your app instead of only writing email copy.

​

Start with the problem you have

​

I need emails to work in production

Start with Supabase email if you are using Supabase Auth, Supabase database tables, or a vibe-coded app built on top of Supabase.

​

I need product emails without writing infrastructure

Start with database-driven email. It explains how Dreamlit uses live app data inside an end-to-end email platform, instead of making you wire API calls, cron jobs, templates, and delivery yourself.

​

I am choosing between tools

Start with comparisons. The right answer changes depending on whether you need a low-level sending API, a campaign tool, or one end-to-end AI platform for product email.

​

I want a tool or planner

Start with Tools. The section is small today, but it includes the Lovable Cloud to Supabase Exporter and a workflow planner.

​

The Dreamlit point of view

Dreamlit’s core bet is that app email works better when the whole loop is connected:

• Auth emails that are branded and production-ready
• Transactional emails like receipts, account alerts, and order updates
• Broadcasts to the right audience
• Recurring emails like digests, reports, and usage warnings
• Lifecycle emails that wait, check current state, and send the right follow-up

Because Dreamlit owns the workflow end to end, AI can do more than draft subject lines. It can reason about who should receive the message, what data matters, when to wait, what to check next, and how the final email should look before you publish.