Send alerts to Slack, Discord or your server
Add a webhook per app to post new users, purchases, low balances, Sentry errors and more to Slack, Discord or a signed JSON endpoint.
Webhooks send an app’s alerts to a Slack or Discord channel, or to your own server as signed JSON. Each app has its own webhooks, and each webhook picks its own events. Your push settings don’t change.
What it’s good for
- A
#signupsor#revenuechannel where the whole team sees new users and purchases as they happen. - An
#alertschannel for low balances, AI limit alerts, a project that stops answering, new Sentry errors and failed builds. - Your own backend or automation tool, to react to events: add a user to your CRM, post to another tool, start a workflow.
Get a Slack webhook URL
- Go to api.slack.com/apps and click Create New App → From scratch. Name it, for example “Cockpitify”, and pick your workspace.
- Open Incoming Webhooks and turn on Activate Incoming Webhooks.
- Click Add New Webhook to Workspace, pick the channel and click Allow.
- Copy the Webhook URL. It starts with
https://hooks.slack.com/services/.
Get a Discord webhook URL
- In Discord, hover the channel and click Edit Channel (the gear).
- Open Integrations → Webhooks → New Webhook.
- Optionally rename it and give it an avatar, then click Copy Webhook URL.
Your own server
Any public https:// address that accepts a POST with a JSON body works. Private and local addresses are refused, and redirects aren’t followed. See JSON format below.
Add a webhook
- Open the app’s webhooks:
- Phone: tap the app’s name at the top, then App settings → Webhooks.
- Web: open App → App settings → Webhooks.
- Tap Add webhook.
- Paste the Webhook URL. Cockpitify tells you whether events arrive as Slack messages, Discord messages or signed JSON.
- Optionally fill in Name. Empty, the list shows the address’s host.
- Choose whether to Show user names. Off, messages say “A user”.
- Tap Save and send test.
The address is stored encrypted and never shown in full again, because anyone who has it can post to the channel.
All events start off. Check the channel for the test message, then turn on the events you want.
You can also reach the webhooks from the Alerts page with Destinations: webhooks.
Choose the events
Open the webhook. Under Events, each one is Off or Instant; New users can also be Hourly, one summary per hour.
| Event | What it sends |
|---|---|
| New users | Each sign-up, or one summary per hour |
| Premium | New premium, trials, cancellations, refunds |
| Balance and budget | A service runs low or passes its budget |
| Daily AI limit | A user passes the daily AI cost limit |
| Project reachability | No signal for 30 minutes, and recovery |
| Usage drop | Active people or a feature drop sharply, or data stops |
| Event alerts | The app’s own event alerts |
| Stability | A release crashes often (Sentry), Sentry sees a new error, or an EAS build or submission fails (Expo) |
| Daily summary | Yesterday’s numbers, each morning |
What the messages look like
- Slack: a short message with a bold title and one line of detail, for example the new user, the plan they bought or the service that runs low. A Sentry alert adds an Open in Sentry link.
- Discord: an embed with the title, the detail, a colour per event type and the time.
- With Show user names off, people appear as “A user” in Slack, Discord and JSON alike. JSON keeps the user id either way.
JSON format
Your server receives one POST per event:
{
"id": "…",
"type": "signup",
"app": { "id": "…", "name": "Studyloop" },
"at": "2026-10-23T09:12:44.000Z",
"user": { "id": "…", "label": null },
"data": { },
"title": "…",
"text": "…"
}
typeis the event, such assignup,premium_on,premium_cancel,low_balance,ai_limitorsentry_issue. The same value is in theX-Ops-Eventheader.userisnullfor events that aren’t about a user, such as a low balance.labelis the name as it appears in push (for example “Elif K.”), and only when Show user names is on.dataholds the event’s details;titleandtextare the same words as the push notification.- Answer with any
2xxstatus within 5 seconds.
Verify the signature
Every JSON request has an X-Ops-Signature header like t=1791393931,v1=5f2c…. v1 is the HMAC-SHA256, in hex, of the timestamp, a dot and the raw body, signed with the webhook’s Signing secret (copy it from the webhook’s page). In Node.js:
import { createHmac, timingSafeEqual } from 'node:crypto'
function verify(rawBody: string, header: string, secret: string) {
const parts = Object.fromEntries(header.split(',').map((p) => p.split('=')))
const expected = createHmac('sha256', secret).update(`${parts.t}.${rawBody}`).digest('hex')
const fresh = Math.abs(Date.now() / 1000 - Number(parts.t)) < 300
return fresh && timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1 ?? ''))
}
Use the raw request body exactly as received, before parsing it as JSON.
Paused webhooks
After 10 failed deliveries in a row, a webhook pauses itself and says why. Events in between aren’t kept. Fix the address or your server, then tap Resume (sends a test first).
The webhook’s page shows the last delivery and its result. A webhook that keeps failing is also named in a banner on the Alerts page.
Limits and permissions
- Up to 5 webhooks per app.
- On a team, adding or changing webhooks needs edit access to Webhooks.
- Send test message sends a test any time; Remove webhook stops events and deletes the address.