Connect Supabase business data

Dashloom Cloud reads business metrics from a Supabase read-only view. It does not use deployment counts, project uptime, or repository activity as business KPIs.

1. Create an aggregate view

Create a view with one date column and one or more numeric metric columns. Keep customer-level records and personal data out of this view.

create view public.dashloom_metrics as
select
  date_trunc('day', created_at)::date as metric_date,
  count(*) filter (where event = 'signup') as signups,
  coalesce(sum(amount) filter (where event = 'payment'), 0) as revenue
from public.business_events
group by 1;

2. Restrict access

Use a dedicated read-only credential and expose only the aggregate view. Apply RLS or a dedicated database role appropriate to your Supabase setup. Never give Dashloom a service-role key or write permission.

3. Connect in Dashloom

Open Dashboard → Data sources → Business data → Supabase. Enter the canonical project URL, dedicated credential, schema, view name, date column, and a JSON mapping from view columns to Dashloom metric names.

{"signups":"new_users","revenue":"revenue"}

Dashloom validates the URL and identifiers, performs a one-row read, encrypts the credential, and then allows synchronization. Each sync reads only the selected columns, accepts no custom SQL, follows no redirects, and stops when the view exceeds 5,000 rows.

Agent and evidence behavior

Synchronized values are stored as product-scoped metric evidence. Dashloom Agents can compare these metrics with acquisition, search, and billing evidence, cite the source and date, and recommend measurable follow-up work. The Agent does not receive database credentials or unrestricted table access.