Minimo × Lovable + Supabase
Add lifecycle email & WhatsApp to your Lovable app — powered directly by your Supabase data, without writing glue code.
- Design and edit auth & transactional emails without redeploys
- Trigger flows from Supabase row changes, not hard-coded cron jobs
- Track activations and upgrades with goals tied to your database
We'll help you wire your first flow in 30 minutes.
Built for Lovable builders using Supabase as their backend.
The reality of email in Lovable apps today
Most Lovable apps follow the same pattern: Supabase as the backend, Lovable for the UI and logic, and Resend (or another ESP) to actually send emails. It works — but you quickly end up with edge functions, cron jobs, scattered templates and no single place to see what's going on.
Auth & system emails stuck in defaults
Signups, magic links and password resets often use Lovable/Resend defaults. Tweaking branding and content is possible, but rarely feels fully on-brand.
Lifecycle flows = hand-written logic
Trial day 1, 3, 7, report ready, subscription renewed — all become manual edge functions, crons or Make/n8n workflows scattered around your stack.
Design & template gap
Your app UI looks great, but email HTML is stuck in 2005. Keeping templates consistent with your brand tokens across Lovable and the inbox is manual work.
No DB-native goals & insights
You can fire events and send emails, but you can't easily answer: "How many trial users reached activation?", "Which sequence drove upgrades?" directly against your Supabase data.
Minimo doesn't replace Lovable or Supabase. It gives you the missing activation & messaging layer on top of both.
Turn your Lovable + Supabase stack into a DB-native lifecycle engine
Minimo connects directly to your Supabase database and treats it as your CRM. Instead of wiring email logic into every edge function, you send a template UID once from your code and let Minimo handle templates, flows, WhatsApp and goals — all driven by your existing tables and events.
DB-native
Point Minimo at your Supabase project. We introspect your schema, listen to row changes and map your core entities (users, subscriptions, events) without copying your entire database.
Template UIDs for developers, visual editor for humans
In Lovable/Supabase code you send template_uid: "auth_signup_welcome" once. Designers and founders can tweak copy, layout and branding forever in Minimo's email builder — no redeploys.
Flows on real product usage
Trigger emails and WhatsApp from DB events: new user, trial day 6, report completed, subscription renewed, usage drop, you name it.
Goals & insights tied to your tables
Define "Activated", "Converted", "At risk" as conditions on your Supabase rows. See how many users each flow brings to each goal.
Keep your provider or use ours
Prefer Resend? Bring your API key and let Minimo orchestrate on top. Want an all-in-one stack? Use Minimo's own SMTP (SES) and unified deliverability logs.
How Minimo fits into a Lovable + Supabase app
Connect Supabase
Connect your Supabase project to Minimo. We read your schema (respecting RLS) and help you map key tables: users, subscriptions, events, and any custom usage tables.
Create UID templates & flows
In Minimo, create branded email templates with stable UIDs like auth_signup_welcome, trial_day_6, report_ready. Build flows that react to Supabase row changes: when a new user is created, when trial is about to end, when an extraction completes.
Call Minimo from your Lovable/Supabase code
In your Lovable app (Supabase Edge Functions or server routes), call Minimo with: template_uid, to email, data (template variables), optional contact metadata (Supabase user id, fields). Minimo sends the email, updates the contact and logs everything against your DB-driven goals.
Your Lovable code stays clean. Lifecycle logic and template management move into Minimo.
Example: trial onboarding flow for a Lovable + Supabase app
Here's a simplified example of how you'd wire a trial onboarding email using Supabase Edge Functions and Minimo. The same pattern applies to "report ready", "subscription renewed", "credits running low", etc.
// supabase/functions/trial-onboarding.ts
import { serve } from "https://deno.land/std/http/server.ts";
const MINIMO_API_KEY = Deno.env.get("MINIMO_API_KEY")!;
const MINIMO_API_URL = "https://api.minimo.so/v1/email/send";
serve(async (req) => {
const { type, table, record } = await req.json();
// Trigger when a new trial user is created
if (type === "INSERT" && table === "users" && record.plan === "trial") {
const { email, id, first_name, trial_ends_at } = record;
await fetch(MINIMO_API_URL, {
method: "POST",
headers: {
"Content-Type": "application/json",
Authorization: `Bearer ${MINIMO_API_KEY}`,
},
body: JSON.stringify({
to: email,
template_uid: "trial_welcome",
data: {
first_name,
trial_end_date: trial_ends_at,
},
contact: {
external_id: id,
email,
fields: {
plan: "trial",
app_source: "lovable",
},
},
}),
});
}
return new Response("ok");
});What happens
- In Minimo you create an email template with UID trial_welcome and variables first_name, trial_end_date.
- Supabase trigger calls this Edge Function on INSERT into users.
- Minimo sends the email, upserts the contact, attributes it to your "Trial → Activated" goal.
What you get on top of Lovable + Resend
Branded auth & system emails
Replace default Lovable auth emails with Minimo templates. Keep Supabase Auth + Resend under the hood if you want — we handle the templates, UIDs and design.
Lifecycle flows without cron
Define onboarding sequences, trial reminders and time to upgrade flows in Minimo's builder, powered by Supabase row changes, instead of hard-coded cron jobs.
DB-native segmentation
Target users based on any column or event in your Supabase tables: plan, usage thresholds, feature flags, last seen, whatever you store in your DB.
Goals & conversion tracking
"Activated", "Converted to paid", "At risk" are defined as conditions on your own rows. Minimo shows how each flow performs against those goals.
Multi-channel: email & WhatsApp
Use the same DB-driven flows to send WhatsApp messages (and later SMS), not just email. Ideal for reminders, OTPs or high-attention nudges.
Unified logs & deliverability
For each contact you see: events, emails/WhatsApp sent, status, failures. Whether you use Minimo SMTP or bring your own Resend account.
For developers
- Use Supabase Edge Functions or Next.js route handlers — Minimo is just an HTTP call away.
- You only hard-code UIDs, not HTML.
- Keep your Lovable app clean; map business events to Minimo flows instead of embedding all logic in one place.
- Bring your own Resend key if you already like their DX.
For founders & growth
- Update copy and branding in a visual builder, no more ping-pong with devs for every tweak.
- See which flows actually drive activation and upgrades.
- Try new lifecycle ideas in hours, not in the next sprint.
"I already use Resend in my Lovable app — why add Minimo?"
Resend is your SMTP, Minimo is your lifecycle brain.
Resend is great at delivering emails. Minimo is focused on what to send when, based on your DB, with templates, flows and goals on top.
You centralise templates instead of scattering HTML in edge functions.
You keep template_uid in code and move design, copy and branding into Minimo — so your team can iterate without redeploys.
You get DB-native goals, not just logs.
Resend tells you if an email was delivered. Minimo tells you if that email (and the flow around it) helped users reach "Activated" or "Paid" in your own tables.
If you're happy with Resend, you can keep it. Minimo plugs into your existing provider instead of forcing a migration.
Early access for Lovable builders
We're onboarding a small group of Lovable + Supabase teams as design partners. We'll help you wire your first auth emails and one activation flow end-to-end, and use your feedback to shape the product.
- 1:1 onboarding call to connect Supabase and set up templates
- Implementation support for your first flow (auth or onboarding)
- Priority support channel for bugs & feature requests
- Discounted pricing for early partners
Frequently asked questions
Do I need to stop using Resend?
No. You can keep Resend as your underlying provider and let Minimo orchestrate templates, flows and goals on top. Or you can switch to Minimo's own SMTP if you prefer a single vendor.
Does Minimo replace Lovable flows?
No. Lovable remains your app builder and frontend logic layer. Minimo focuses on lifecycle messaging and activation based on your Supabase data. Think of it as a specialised layer for email & WhatsApp, not a general automation tool.
What do I need to integrate Minimo in a Lovable app?
A Supabase project, a Minimo API key and one Edge Function (or server route) calling POST /v1/email/send. We provide a full recipe and starter repo so you can copy/paste the initial setup.
Where is my data stored?
Your primary data stays in Supabase. Minimo stores only the minimum needed to manage contacts, templates and logs. We're an EU company and can sign DPAs for teams that need them.
Can I send WhatsApp/SMS as well as email?
Yes. Minimo supports WhatsApp out of the box and can tie those messages to the same flows and goals as your emails. SMS support is on the roadmap; WhatsApp is the first-class channel alongside email.
What happens if the Minimo API is down?
We aim for high availability, and we expose clear status and retry mechanisms. You can also design your edge functions to fall back gracefully or re-send queued events once Minimo is back.
