Get a native alert for every row that matters.
After your application receives a Supabase database webhook, send the useful row changes to LogsNinja for native alerts and charts that update automatically once configured.
What you'll never miss
| Supabase alone | With LogsNinja | |
|---|---|---|
| A new row in a key table | Sits in the table editor until someone happens to look. | A native alert the moment the row is inserted. |
| A canceled subscription row | You find out at month-end, from the numbers. | An alert the moment the row changes. |
| A new auth signup | No easy way to notice it in real time. | An alert, plus a point on your growth chart. |
Works with Supabase Database Webhooks
Point the Supabase Database Webhook at an endpoint in your application. That handler receives the row, keeps only the useful fields and sends the resulting event to LogsNinja.
| Supabase payload field | LogsNinja field |
|---|---|
type |
title (INSERT, UPDATE or DELETE) |
table |
metadata.table |
record |
content |
schema |
metadata.schema |
Need the exact code? Read the step-by-step guide. From Webhook to Push Notification in One HTTP Call
Track your database automatically
Create the database charts you need once. Every matching row event your application sends then updates them automatically.
Example values shown for illustration.
Who it's for
A good fit if
You already use Supabase and want to know about a specific row change – a signup, a cancellation, a critical update – without polling the table yourself.
Not a fit if
You want to alert on every row change across every table. Pick the tables and events that matter – LogsNinja is not a database audit log.
Frequently asked questions
Do I need to write a Postgres function?
No. Database Webhooks are configured from the Supabase dashboard by picking a table and an event – no SQL trigger to write by hand.
Can I send only some columns, not the full row?
Yes. Forward only the fields you need for the alert or the chart from inside your webhook handler, not the raw record.
Does this work for Supabase Auth events too?
For signup events, use a public profile table populated from auth.users, then attach the Database Webhook to that table. Supabase manages the auth schema, so avoid attaching webhooks directly to its internal tables.
Never miss a row that matters again.
Connect your webhook and see the next change as a native alert.