Your database fires the message.
Connect Supabase or Postgres. The moment a row changes, Minimo sends the email, WhatsApp, or SMS. No syncs. No code.
Latency
Minutes vs milliseconds.
Reverse ETL was built for analytics warehouses. Activation needs real-time.
Polls your DB.
Snapshots the warehouse on a cron. Acts on yesterday's state.
Listens to your DB.
Supabase Realtime + Postgres logical replication. Fires the moment a row changes.
How it works
First flow live in 10 minutes.
Connect
Read-only role + connection string. Supabase one-click.
Map
Minimo reads your schema. Confirm what's a user, what's a plan.
Trigger
Pick a DB event. Pick a channel. Done.
Triggers
Anything in your DB can fire a flow.
No event tracking SDK to install. Your existing columns are the events.
trial_ends_at − 3 daysplan changed to 'pro'subscription_status = 'past_due'last_active_at > 30 dayscredits < 100signed_up_at > 24h AND activated_at IS NULLAI Schema Analyzer
AI reads your schema. Suggests the flows.
Point Minimo at your DB. The AI maps your tables, infers what your users look like, and proposes three automations using your real column names — ready to review.
Dynamic Custom Fields
Custom fields that never go stale.
Define a custom field as a SQL query against your DB. Minimo evaluates it the moment a message fires — never cached, never drifting from your real data.
SELECT MAX(amount) FROM orders WHERE user_id = $1What this is NOT
Honest about scope.
Not a CDP.
No identity resolution, no audience builder, no warehouse sync. If you need Segment, keep Segment.
Not a data warehouse.
We don't store your user data. We read it real-time. Marketing data (opens, clicks, replies) lives in Minimo.
Not raw analytics capture.
Keep Hotjar or PostHog for session capture. Minimo aggregates their signals with your DB so you can ask the AI: "how many pro users visited /pricing?" — and get the answer.
Connect your database in 2 minutes.
14 days · all features · no credit card
