WEBHOOK NOTIFICATIONS

Turn any webhook into a native alert and a live metric.

Your application keeps receiving and verifying Stripe, GitHub or Supabase webhooks. Add one LogsNinja API call to send the useful fields to native alerts and charts that update automatically once configured.

Send my first webhook

What changes once webhooks are connected

A failed deployment
Buried in CI logs until someone happens to check them.
A native alert the moment the workflow fails.
A new order
You find out next time you open the dashboard.
An alert, plus a bump on your revenue chart.
A risky database change
No visibility until something downstream breaks.
An alert the instant the row changes.

Works with the webhook you already have

No new endpoint to deploy. Inside the handler that already receives the webhook, three steps turn it into a signal.

Verify the signature
Map the fields
Send the event
FROM WEBHOOK TO SIGNAL

One HTTP call turns a payload into an alert.

Verify the sender's signature first, then map the fields you care about to a LogsNinja event.

$ curl -X POST https://api.logsninja.com/v1/events \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
    "project": "YOUR_PROJECT_ID",
    "stream":  "webhooks",
    "title":   "Deployment succeeded",
    "emoji":    "🚀",
    "metadata": {"source": "github", "repo": "api"},
    "notify":   true
  }'

✓ Event received
✓ Push sent to 2 devices
# chart updated

A GitHub payload, mapped

The same idea applies to any provider – pull the fields you care about out of the payload you already receive.

GitHub payload field LogsNinja field
workflow_run.conclusion title (e.g. "Deployment succeeded")
repository.full_name metadata.repo
sender.login metadata.actor
success or failure emoji (🚀 or 🚨)
Webhooks
Deployment succeededwebhooks ·
Workflow failedwebhooks ·
ONE WEBHOOK, TWO OUTCOMES

Every webhook becomes an alert and a chart.

No separate integration for notifications and reporting. Send the event once, and it feeds both at the same time.

Popular webhook sources

Stripe

Payments, invoices and subscription changes.

GitHub

Deployments, pull requests and workflow failures.

Supabase

Database changes and auth events.

Your own backend

Any internal event you already emit as a webhook.

Who it's for

A good fit if

You already receive webhooks from a provider or your own backend and want an alert plus a chart, without building either from scratch.

Not a fit if

You need to receive and route webhooks in the first place. LogsNinja turns a webhook you already receive into an alert and a chart – it's not a webhook relay or queue.

Frequently asked questions

Do I need to change my existing webhook endpoint?

No. Keep the endpoint you already have and add one HTTP call to LogsNinja inside it, after you verify the sender's signature.

Which webhook providers does this work with?

Any of them. LogsNinja doesn't parse a specific provider's payload – you map the fields you care about to a LogsNinja event, so it works the same way for Stripe, GitHub, Supabase or an internal system.

Can the same webhook also build a dashboard?

Yes. The event you send for the alert is the same one that feeds a chart or metric – no separate integration for each.

What if the webhook fires more often than I want to be notified?

Set notify to false for the events you only want on a chart, and true for the ones that deserve an alert – both read the same payload.

Turn your next webhook into an alert.

Send your first event and see it become a native notification in seconds.

Send my first webhook