Lovable Email Setup: 4 Flows Your App Needs Before Launch

A Lovable app needs four email flows: auth emails, transactional app emails, email blasts, and recurring emails. On Lovable Cloud, the built-in Emails feature (paid plans) covers auth and app emails from your own domain, and scheduled Jobs can send recurring ones. Blasts need a separate tool such as Resend. If your app runs on your own Supabase project, you configure auth emails in Supabase and send everything else through an email provider.

Last validated: September 2026 against Lovable's email docs⁠, Lovable Jobs⁠, Supabase's SMTP docs⁠, and Resend's docs⁠.

What email flows does a Lovable app need?

1. Auth emails. Needed for any app that confirms signups, resets passwords, or offers magic-link or one-time-code sign-in:

• Signup confirmation ("Verify your email address")
• Password reset
• Magic link or one-time code sign-in
• Email change confirmation
• Invites and reauthentication, if your app uses them

2. Transactional app emails. Sent when something happens in your app:

• Welcome email after signup
• Comment or reply notifications
• Order confirmations and receipts
• Status updates ("Your export is ready")

3. Email blasts. One-time sends to a group: newsletters, product announcements, feature updates, promotions.

4. Recurring emails. Sent on a schedule: weekly digests, reminders, usage summaries, monthly reports.

Cold outreach to people who haven't signed up is a different job, with different rules, and isn't covered here.

Which email setup should a Lovable app use?

It depends mostly on your backend. This guide covers the two backends Lovable sets up for you: Lovable Cloud (Lovable's built-in backend, which is built on Supabase) and your own Supabase project connected through Lovable's Supabase integration. Lovable also documents moving to self-hosted Supabase or another Postgres backend.

A few things to know before you pick:

• Lovable's auth emails need Lovable Cloud. They always go through Cloud Auth, though TanStack Start projects can send app emails without Cloud. If you later move your backend to your own Supabase project, you'll set up auth emails again in Supabase.
• Resend is Lovable's suggested provider for marketing email and for teams who already send with Resend. Lovable's docs note the connector can't verify domains for you or receive Resend's event webhooks.
• Your own Supabase gives you direct database access, which email tools that query your data at send time need. Lovable documents a way to export Lovable Cloud data⁠ to your own Supabase project, and our open-source Lovable Cloud to Supabase exporter moves tables, users, and storage files in one pass.

How do you set up auth emails in Lovable?

Prompt Lovable for the flow you want ("add magic link sign-in") and it adds the UI and the auth calls. The sender setup depends on your backend.

On Lovable Cloud

Auth works immediately, but emails come from a default Lovable sender, and Lovable's docs warn that emails from new domains often land in spam. To send from your own domain:

1. Open More > Cloud > Emails and click Get started.
2. Pick your domain and a sender subdomain (the default is notify, so emails come from something like notify.yourapp.com).
3. Add the DNS records. Lovable can do it automatically through Entri, or you add the NS and TXT records by hand, plus a _dmarc record if you turn on Show as sent from @yourdomain.com.
4. Wait for the domain to show Verified. Propagation usually takes hours and can take up to 72.

This needs a paid Lovable plan. Each paid workspace includes 50,000 emails a month, then 4 credits per 1,000. There are also hourly caps:

If you expect a launch spike (a Product Hunt day, a waitlist invite), check the auth cap against your busiest hour.

Once set up, you can edit each template with a live preview, send yourself a test, and see sent, delivered, and bounced counts plus an activity log under Analytics and logs.

On your own Supabase project

Auth emails are configured in Supabase, not Lovable. Supabase's built-in sender only delivers to your organization's team members and allows 2 emails per hour, so real users won't get their emails until you change it.

You have two options:

• Custom SMTP: under Authentication > Emails > SMTP Settings, enter your provider's credentials. The rate limit then starts at 30 per hour and you can raise it under Authentication > Rate Limits.
• Send Email Hook: Supabase calls your own function to send each auth email, so you control templates and delivery in code.

With custom SMTP, edit the templates under Authentication > Emails; with a Send Email Hook, your function renders its own. The default templates are plain and carry no branding. On free Supabase projects created since June 3, 2026, you can only edit templates after setting up custom SMTP. Our guides cover both setup options step by step and the template variables.

How do you send transactional emails from a Lovable app?

Ask Lovable for the email and when it should send: "When someone comments on a post, email the post's author."

With Lovable Emails

If you've set up Emails, Lovable writes the sending code in your app's server code. Projects built on TanStack Start can send app emails without Lovable Cloud, and React + Vite projects need Cloud turned on. App emails count toward the same 50,000 monthly emails and have their own hourly cap.

With Resend

1. Sign up at Resend⁠ and verify your domain. Until you do, Resend's resend.dev testing domain only sends to your own account email.
2. Connect Resend in Lovable and add your API key.
3. Ask Lovable for the email and tell it to use Resend.

Resend's free plan covers 3,000 emails a month, up to 100 a day.

Test before real users see it. Code-sent emails are easy to break without noticing. Trigger each flow yourself after every change, send to a test address, and check the rendered email on your phone as well as your desktop.

How do you send email blasts from a Lovable app?

Lovable's Emails feature doesn't support marketing emails, newsletters, or promotions, so you need one of these:

1. Export and import. Ask Lovable for a user export, then upload the CSV to Resend or a marketing platform like Klaviyo⁠ or ActiveCampaign⁠. Fine for one send. For repeat sends, the list goes stale.
2. Sync to Resend. Ask Lovable to push users to Resend Contacts whenever they're created, updated, or deleted, and backfill existing users once. Then send Broadcasts⁠ to a Segment. Resend's marketing free plan covers up to 1,000 contacts. More setup, but the list stays current.
3. Query at send time. Use a tool that reads your database directly, so there's nothing to sync. This needs direct database access, for example through your own Supabase project.

Whichever you pick, blasts need an unsubscribe link and a sender reputation you don't share with your password resets. The deliverability guide covers both.

How do you send recurring emails from a Lovable app?

On Lovable Cloud, ask Lovable to create a scheduled Job: "Every Monday at 9am Eastern, email each user a summary of last week's activity." Jobs run on a schedule, and you can see each run's status (Succeeded, Failed, Running) under More > Cloud > Jobs. Lovable's docs note that frequent or long-running jobs use more credits.

On your own Supabase project, the same prompt creates a Supabase Cron⁠ job that calls an Edge Function, which queries the data and sends the emails through your provider. For event-based sequences (a welcome email, then a follow-up three days later), Resend Automations⁠ can handle the delays and conditions.

Recurring emails are where mistakes are most expensive, because a bad send goes to everyone. Before turning one on:

• Run it once against a test list of your own addresses.
• Log who was sent what, so a rerun doesn't double-send.
• Add a condition for opted-out users.

Which emails should a Lovable app send first?

Auth emails come first because without them, users can't confirm their accounts, reset passwords, or use magic links. After that, prioritize emails that get new signups to use your app:

• A welcome email right after signup, pointing at the one action that makes your app useful.
• A nudge 24 to 48 hours later to users who haven't done that action yet.
• A heads-up before a trial ends or a usage limit is reached.

These are triggered by what users do (or don't do), so they need your app's data. Welcome email examples shows the triggers and copy, and what is a drip campaign covers how to chain them.

Where Dreamlit fits

Dreamlit, the company behind this blog, takes the whole job off your hands. Our experts decide what to send, run the emails that turn signups into paying users, and own the results. It fits products with 500 or more signups a month.

Launching soon? See how Dreamlit works once your signups grow.

References

1. Lovable: Send branded emails from your own domain⁠
2. Lovable: Email authentication⁠
3. Lovable: Jobs⁠
4. Lovable: Resend connector⁠
5. Lovable: Connect to Supabase⁠
6. Supabase: Send emails with custom SMTP⁠
7. Supabase: Auth rate limits⁠
8. Supabase: Email templates⁠
9. Resend: Account quotas and limits⁠
10. Resend: resend.dev testing domain restrictions⁠
11. Resend: Broadcasts⁠
12. Supabase: Cron⁠

---

Frequently asked questions

Does Lovable send emails?

Yes. Lovable Cloud sends auth emails (signup confirmations, password resets, magic links) from a default Lovable sender. On paid plans, the Emails feature sends auth emails and app emails, such as order confirmations, from your own domain.

Is Lovable's email feature free?

No. Sending from your own domain is on paid plans only, and free plans use the default Lovable Cloud Auth sender. Each paid workspace includes 50,000 emails a month, and extra emails cost 4 credits per 1,000.

Can Lovable send newsletters or email blasts?

Not through Lovable's Emails feature, which only supports transactional email. For newsletters and announcements, connect Resend and use its Broadcasts, or export your users to a marketing email tool.

Can Lovable send recurring emails like weekly digests?

Yes. Ask Lovable to create a scheduled Job on Lovable Cloud (for example, every Monday at 9am) that sends the email. If your app uses your own Supabase project, the same idea runs on Supabase Cron and an Edge Function.

Why do my Lovable app's auth emails only reach my own team?

If your app uses your own Supabase project, Supabase's built-in sender only delivers to your organization's team members and allows 2 emails per hour. Configure custom SMTP or a Send Email Hook in Supabase before launch.

Do I need DNS records to send email from my own domain?

Yes. Lovable's Emails setup adds the required records for a sender subdomain automatically through Entri, or gives you records to add by hand. Resend also requires you to verify your domain before sending to real recipients.