Rules & patterns

Rules determine which events reach you through which channel. No rule: no notification (events are still stored in your history, though).

Quick-start presets

The rules page offers ready-made one-click rules, including:

• 🔔 Subscription cancelled — customer.subscription.deleted
• ⏳ Cancellation scheduled — customer.subscription.updated
• ⚠️ Payment failed — invoice.payment_failed
• 📡 All events — *

Custom patterns

The pattern matches the Stripe event type. * is a wildcard:

• customer.subscription.deleted — exactly this event
• customer.subscription.* — everything subscription-related
• invoice.* — everything invoice-related
• * — literally everything

Noise filter (“skip routine updates”)

Some events fire very often without anything important happening — e.g. customer.subscription.updated on every minor change. With the noise filter enabled, Churnbell only notifies you about such events when something genuinely relevant happened (such as a scheduled cancellation).

The filter also bundles duplicate notifications: for a failed payment Stripe sends e.g. three events, for a received payment up to five – you only get one notification each. Repeated dunning attempts are only reported on the first and the final failure. Details: Bundling & routine events.

💡 Recommendation to start with: the presets “Subscription cancelled”, “Cancellation scheduled” and “Payment failed” — these are exactly the alarms that cost you revenue.