Send branded emails from your own domain

1. 1

   Ask Lovable to set up emails for your domain, or go to the 'Cloud' tab, then 'Emails', and click 'Get started'.

   This initiates the process to connect your custom domain for email sending.

2. 2

   Choose an existing domain or add a new one (e.g., 'yourdomain.com'), then click 'Continue'.

   This tells Lovable which domain you want to use for sending emails.

3. 3

   Configure the sender subdomain (e.g., 'notify.yourdomain.com') and decide if you want emails to appear from your root domain (e.g., 'yourdomain.com'), then click 'Set up domain'.

   This sets up the specific address your emails will come from and how it will display to recipients.

4. 4

   Follow the on-screen prompts to either automatically update your DNS records through Entri, or manually copy and add the provided TXT and NS records to your domain registrar or DNS provider.

   This step verifies that you own the domain and allows Lovable to manage email sending for it. Be careful not to replace your domain's main nameservers if doing it manually.

5. 5

   Wait for the domain status to change to 'Verified' on the 'Emails' page.

   DNS changes take time to update across the internet, and your domain needs to be verified before emails can be sent.

6. 6

   Go to the 'Auth emails' tab and click 'Customize auth emails' to generate standard email templates, or ask Lovable to create specific app email templates (e.g., 'Add order confirmation emails to my app').

   This generates the actual email templates that will be sent, which you can then customize to match your brand.

I want to send password reset emails and order confirmation emails from my domain, 'example.com'. Please guide me through the setup.

DNS

Domain Name System, like a phone book for the internet that translates website names into computer addresses. You need to update entries here to prove you own your domain and allow Lovable to send emails from it.

SPF

Sender Policy Framework, a security record that tells email providers which servers are allowed to send emails from your domain. It helps prevent spammers from faking emails from your address.

DKIM

DomainKeys Identified Mail, a digital signature added to your emails that proves they haven't been tampered with during delivery and truly came from your domain.

DMARC

Domain-based Message Authentication, Reporting, and Conformance, a policy that tells email providers what to do if SPF or DKIM checks fail (e.g., send to spam, reject, or monitor). It further protects your domain from being used by spammers.

Transactional emails

Emails sent automatically in response to a user's action, like a password reset, order confirmation, or shipping notification. These are not marketing emails.

Root domain

The main part of your website address, like 'yourdomain.com'.

Subdomain

An extension of your main domain, like 'blog.yourdomain.com' or 'notify.yourdomain.com'.

DNS records

Specific entries in your DNS that provide instructions, such as where to find your website or which servers can send emails for your domain. Examples include TXT and NS records.

Nameservers

Specialized servers that store all the DNS records for your domain. When you update nameservers, you're telling the internet where to look for your domain's information.

Deliverability

How likely your emails are to successfully reach the recipient's inbox, rather than being blocked or sent to spam.

• Do not replace your domain's main nameservers at your registrar when setting up DNS manually; this will take your entire website and email offline. Only add the NS records as records *within* your DNS zone for the specific subdomain.
• Remember that emails are only available on paid plans and require the built-in Lovable backend (Cloud).
• Be aware that newly configured domains start with no sending reputation, so initial emails might go to spam until your domain builds trust.
• Do not remove or change the required authentication variables, callback links, or the unsubscribe footer in email templates, as this can break functionality.