Skip to content

Give your Lovable app real email.

Lovable's agent reads and sends test mail through the hosted MCP. The app it builds sends with its own key and hears about new mail through a signed webhook.

Connect Lovable in three steps.

Send and receive email from the apps you build in Lovable.

  1. Add Drin to Lovable's chat

    In Lovable, open Connectors → Add custom → MCP server, paste this address, keep OAuth and sign in with Drin. Now the agent can read and send test mail.

    https://mcp.drin.run/mcp
  2. Give the app a key

    In Drin, open Agents & keys and create one for the app. Store it as a secret in the project and ask the agent to send and read mail with the Drin API.

  3. Get a webhook when mail lands

    In Drin, open Webhooks, add your app's https address and pick the new-mail event (inbound_received). Each email arrives as a signed POST.

These steps follow Lovable's own docs (docs.lovable.dev). If Lovable changes how it works, tell us and we'll fix this page.

Mail calls your app.

Your Lovable app gets a signed POST for each new email, with the clean text in the body. Check the Drin-Signature header with the secret Drin showed you once, when you made the webhook.

curl -X POST https://api.drin.run/v1/webhooks \
  -H "Authorization: Bearer $DRIN_KEY" \
  -H 'content-type: application/json' \
  -d '{ "url": "https://app.acme.com/api/drin",
        "eventTypes": ["inbound_received"] }'

# → { "id": "…", "signingSecret": "whsec_…", … }   the secret is shown once
# Below full access, or from an agent's key, it needs webhooks:write, answers 202
# and delivers nothing until a person approves.

What Lovable can and can't do.

What it can do

  • Your app sends. Sign-in links, receipts and replies from the app Lovable builds, with a key stored as a project secret. An app's key doesn't wait for a person.
  • Your app hears replies. Each new email arrives as a signed POST with the sender, subject and clean text. No mail parsing.
  • Test for free. The free sandbox sends test emails to verified recipients, through the same API.

What it can't do

  • Mail doesn't wake Lovable's chat agent. The webhook goes to the app it built.
  • The chat's sign-in doesn't carry over. The app needs its own key, stored as a project secret.
  • It can't see inboxes you didn't pick. To its key, they answer 404 on reads and 403 on writes.
  • It can't mail a new address by itself. The first mail waits for a person, unless it's a reply to a verified sender in the same thread on an open desk.

Before you connect it.

Where does the app's key go?
Create one in Drin under Agents & keys and store it as a secret in the Lovable project, on the server side. The key is shown once.
How does my app know a webhook is from Drin?
Each POST has a Drin-Signature: t=…,v1=… header: an HMAC-SHA256 of the timestamp and the raw body with your webhook's secret. verifyWebhook in @drin00/sdk checks it and rejects anything older than 5 minutes.
Is the chat's sign-in the same as the app's key?
No. Lovable's chat signs in with Drin; the app gets its own key. Revoke one and the other keeps working.
Do inboxes or apps cost extra?
No. There is no fee per inbox or per connected app.

The same inbox works in other apps.

Each app gets its own key. Pause one, and the others keep working.

Give Lovable an address tonight.

Start free. Add your own domain whenever you like.