Integrations / Supabase
Supabase
Every scheduled loop, its run history, and whose key it's on.
Why connect it
Most self-built apps keep their background work in pg_cron: sweepers, drains, nightly jobs. Nobody looks at them after they're written. This is where idle loops spin for months and where one failing job stays failing.
What you'll see
- Every pg_cron job with cadence, 7-day runs, failures, and the last error
- Edge function calls in the last 24 hours
- Queue depth on the tables each loop touches — so an empty-queue loop is visible
- Secret fingerprints (never values): the same key in two projects shows as the same fingerprint
What the credential can and cannot do
Where to get it: Approve: Supabase's own screen, scoped to read on Projects, Database, Edge Functions, Analytics. Token: supabase.com → account → Access Tokens.
It grants: The approve flow grants read only. A pasted access token grants full API access to your account; GitDoctor only reads with it.
It cannot: Nothing is written until you apply an action, and every action ships with its undo.
Whatever you connect lives in an encrypted cookie in your browser and nowhere else. Sign out and it's gone; revoke it at the provider and it stops working immediately.
Connect
Approve on Supabase — the recommended path.
Own this deployment? Unlock with the passcode instead.