Cockpitify Docs Search the docs⌘K Product Sign in Try the live demo

See and manage every alert for an app

Updated · Every plan · Phone · Web

The Alerts page lists every rule that can notify you about an app, whether it is on, when it last fired, and where each alert goes.

The Alerts page shows everything that can send an alert for one app, each as one plain sentence: what sets it off, whether it is on, when it last fired and how often in the last 7 days. From here you open the rule to change it, and choose where each kind of alert goes.

Open it

  • Phone: tap the app’s name at the top, then Alerts under App.
  • Web: in the sidebar, open App → Alerts.

At the top you see how many rules are on and how many times they fired in 7 days.

The groups

GroupWhat’s in it
MoneyA service’s balance or budget, a user’s AI cost passing your daily limit, a failed payment, RevenueCat’s fee nearing its free limit, someone subscribing, cancelling or lapsing, and money metrics that move the wrong way
UsersSomeone signs up, usage drops, usage goes silent, and user metrics that move the wrong way
StabilityA new Sentry issue or a regression, a release under your crash-free line, and a failed EAS build or submission
CustomYour own event alerts on events your app sends
ReportsThe daily summary and the weekly insights

Each row reads like the rule itself, for example “A user’s AI cost today is over $5” or “Usage drops by 30% or more”. The second line gives the details: the thresholds, the filter, or what makes it fire.

What the state means

  • On: the rule can fire.
  • Off: the rule exists but is switched off, or has no threshold yet.
  • Always on: the alert fires without a rule (sign-ups, subscription changes, failed payments, the daily summary and weekly insights). Whether you get it is your own choice; see Choose which notifications you get.

A row that says Needs and a connection name, such as “Needs RevenueCat”, can’t fire until that connection is set up. Tap the line to set it up. See Check your connections.

Rows marked “Not set yet”, such as “A weekly number moves the wrong way” or “A product event happens”, are kinds of rule you haven’t created yet.

Change a rule

Tap a row (on the web, click it or Edit). It opens the place the rule is set:

RuleOpens
Balance or budgetThe service, with its thresholds. See Add a service
AI cost limitThe daily limit. See Daily AI limit
Metric moves the wrong wayMetric threshold alerts
Usage drops or goes silentUsage alerts (phone: Usage tracking; web: App → Data)
Sentry issue, release healthSentry. See Instant Sentry alerts and Release health
EAS buildThe Expo service’s build alerts
RevenueCat feeThe RevenueCat connection
Event alertThe event alert editor
Automatic alertsYour notification settings

Event alerts have a switch on the row, so you can turn one off without opening it. To add one, tap New event alert at the top. An app can have up to 20 event alerts.

Choose where an alert goes

Under each row, Goes to lists where that kind of alert is sent, such as “Team push · #revenue”. Tap it to open Where it goes:

  • Team push: phones and browsers of the people who can see that part of the app. Each person’s own notification settings still apply.
  • Webhooks: tick the app’s Slack, Discord or JSON webhooks that should get this kind. See Send alerts to Slack, Discord or your server.
  • E-mail owners: the workspace owner and admins, at most 50 e-mails a day for the app. It only shows as available when e-mail is set up on the server.

Tap Save. The choice applies to every alert of that kind for this app.

Until you save here, each webhook follows its own event list. Once you save, this choice wins for that kind, and the webhook’s page says so. Use webhook lists goes back to the webhooks’ own lists.

Send a test and check deliveries

On Where it goes, tap Send a test. The push part goes to your own devices only; webhooks and e-mail get it as set. A message tells you what each destination did, for example “Push · sent, #revenue · failed”.

Recent lists the last fires of that kind with the result at each destination: sent, failed or skipped. Fires are kept for 30 days.

If a destination kept failing in the last 7 days, a banner at the top of the Alerts page names it, for example “#alerts failed 4 times”, with the last error. Other destinations still work. For a webhook, open it and fix the address.

Was this page helpful?YesNo
Ask a question
Questions? Ask me.I’m Murat, the indie developer behind Cockpitify.

I read every message and reply by email, usually within a day.