Send Emails with Lovable

​

Overview

​

What Brew Handles for You

• On-brand design without HTML - Describe your email in plain language. Brew generates production-ready, responsive emails that match your brand’s colors, fonts, logo, and tone of voice. No HTML coding or email design skills needed.
• Compliance built in - Marketing emails (automations and campaigns) automatically include a physical address and unsubscribe link in the footer. Brew’s preflight audit blocks any send that’s missing required compliance elements, keeping you aligned with CAN-SPAM and GDPR.
• Unsubscribe management - Brew handles the entire unsubscribe flow: a branded unsubscribe page, contact status updates, and automatic suppression from future marketing sends. You don’t need to build any of this yourself.
• Bounce and complaint handling - Hard bounces and spam complaints are automatically suppressed, protecting your sender reputation without any code on your end.
• Contact auto-creation - When you trigger an automation or send a transactional email, Brew automatically creates or updates the contact record. No separate contact creation step needed in your app.
• Works across every email client - Gmail, Outlook, Apple Mail, Yahoo, mobile - email HTML is notoriously tricky. Every email Brew generates is responsive and tested across clients.
• Analytics without instrumentation - Opens, clicks, bounces, and deliverability are tracked automatically in Brew’s dashboard. No event tracking code required in your Lovable app.

​

Three Ways to Send Emails with Brew

​

Prerequisites

​

Connect Brew to Lovable

​

Automations

​

Set up in Brew

​

Prompt Lovable

Integrate Brew automation API for triggering email sequences.

API Details:
- Base URL: https://brew.new/api
- Auth: Bearer token using the BREW_API_KEY secret
- Endpoint: POST /automations/{eventId}/trigger
- Content-Type: application/json

Request body format:
{
  "payload": {
    "email": "user@example.com",
    "firstName": "Jane",
    "plan": "premium"
  }
}

Response format:
{
  "success": true,
  "executionId": "exec_abc123",
  "automationId": "kx7777hn1pqfvpq",
  "eventId": "user_signup",
  "status": "running",
  "contact": {
    "email": "user@example.com",
    "action": "created"
  }
}

Create a Supabase Edge Function called "trigger-automation" that:
1. Reads BREW_API_KEY from environment secrets
2. Accepts eventId and payload in the request body
3. Calls POST https://brew.new/api/automations/{eventId}/trigger with Bearer token auth
4. Returns the response to the client

The "email" field is always required in the payload. The eventId is a string you define in Brew when creating the automation (e.g. "user_signup", "order_placed").

Docs: https://docs.brew.new/emails/automations

​

When to use automations

• User signup - Trigger user_signup to start a welcome series
• Onboarding - Trigger onboarding_started to send a multi-step getting started sequence
• Trial ending - Trigger trial_ending to send a reminder sequence nudging users to upgrade
• Re-engagement - Trigger user_inactive to win back users who haven’t logged in recently

​

Transactional Emails

​

Set up in Brew

​

Prompt Lovable

Integrate Brew email API for sending transactional emails.

API Details:
- Base URL: https://brew.new/api
- Auth: Bearer token using the BREW_API_KEY secret
- Endpoint: POST /send/transactional
- Content-Type: application/json

Request body format:
{
  "chatId": "YOUR_TEMPLATE_ID",
  "to": "recipient@example.com",
  "variables": {
    "firstName": "Jane",
    "resetUrl": "https://yourapp.com/reset?token=abc123"
  }
}

Response format:
{
  "success": true,
  "data": {
    "sent": 1,
    "failed": 0,
    "results": [
      { "email": "recipient@example.com", "id": "email_abc123" }
    ]
  },
  "meta": { "requestId": "req_xyz789" }
}

Create a Supabase Edge Function called "send-email" that:
1. Reads BREW_API_KEY from environment secrets
2. Accepts chatId, to, and variables in the request body
3. Calls the Brew API with Bearer token auth
4. Returns the response to the client

The "chatId" is the template ID from Brew. Design your email in Brew first, then publish it to get the chatId.

Docs: https://docs.brew.new/emails/transactional-emails

​

When to use transactional emails

• Password resets - Send a reset link immediately when requested
• Order receipts - Confirm a purchase the moment it’s completed
• Payment failed - Notify the user instantly so they can update their payment method
• Account notifications - Plan upgrades, billing alerts, security events

​

Test Your Integration

​

Troubleshooting

​

Need Help?