Email for Lovable.
Lovable writes the app; Drin carries its mail. Describe the email you want in the prompt, add one secret, and the generated code sends through a clean REST API — no backend of your own.
Free sandbox to integrate · Production from $3/month
One block, then ask.
Lovable doesn't speak MCP — it doesn't need to. The REST API is one endpoint with a bearer key; Lovable generates correct calls from a clear prompt, and the key stays in project secrets.
Full setup guide →"Add transactional email to this app using the Drin REST API: POST https://api.drin.run/v1/emails with Authorization: Bearer read from the DRIN_API_KEY secret. Send a welcome email when a user signs up." # then: project settings → secrets → DRIN_API_KEY.
Paste one of these first.
Three real tasks, end to end — copy a prompt and watch it run the tools.
When a user signs up, send them a welcome email via the Drin API (POST https://api.drin.run/v1/emails, bearer key from the DRIN_API_KEY secret), from hello@mydomain.com.
Add a contact page whose form POSTs to my Drin form endpoint https://api.drin.run/f/— plain HTML form, no client library, success and error states included.
Add an /api/inbound route that accepts Drin inbound_received webhook events, verifies the Drin-Signature header, and stores data.from, data.subject and data.threadId in the database — then fetch the message text from GET https://api.drin.run/v1/emails/{data.messageId}/body (bearer key from the DRIN_API_KEY secret) and store that too.Asked about Lovable.
Why REST instead of MCP here?+
MCP connects an agent to tools at run time; Lovable instead writes application code. Generated apps call the REST API directly — fewer moving parts, and the code keeps working after the prompt session ends.
Where does my API key go?+
Project settings → secrets, as DRIN_API_KEY. Never paste it into the prompt or the generated client code — the prompt above tells Lovable to read it from the secret.
Can my published Lovable app receive email?+
Yes — give it a webhook route subscribed to inbound_received; each message that lands in a Drin inbox posts a signed JSON event, with the parsed body one API call away. For simple contact pages, Drin forms skip the backend entirely.
Will mail from a generated app actually land?+
Sending rides your verified domain with DKIM, SPF and DMARC, warmup and suppressions — same engine as every other Drin send. How deliverability works →