What Chargebee + PingBell does together
Chargebee’s webhooks fire on subscription lifecycle events (subscription_created, _activated, _changed, _cancelled, _reactivated) and invoice events (invoice_generated, _paid). Point them at a PingBell source and each one becomes a counter update, a team push, and a graph point — invoice-paid events for a collected-revenue counter, lifecycle events for a new-subscriptions counter.
Use cases
- Mid-market SaaS on Chargebee tracking live MRR across an office
- Subscription boxes and DTC subscription businesses
- Membership businesses using Chargebee’s billing
- Multi-site Chargebee operators aggregating across product lines
- Dunning-focused ops teams alerting on payment-failed events
Setup
- In Chargebee, go to Settings → API Keys → Webhooks → Add Webhook.
- Paste your PingBell source’s webhook URL (from the Sources page).
- Subscribe to subscription and invoice events.
- Save. Chargebee sends a test webhook.
- In PingBell, drop a counter block on a board and pick the source — revenue or count, live.
Why PingBell for Chargebee users
PingBell is the broadcast layer for your Chargebee revenue: live MRR on every team screen, push alerts on every new subscription, office-TV display. Pairs naturally with whatever SaaS analytics tool you already use — different jobs, both worth doing.
FAQ
Does it support Chargebee’s hosted checkout?
Yes. Checkout-completed events fire the subscription-created webhook and flow through normally.
How do I track different subscription events separately?
Create a source per event — new subscriptions on one counter, cancellations on another — by pointing each Chargebee webhook at its own PingBell source.
Does it work with Chargebee’s multi-currency?
Keep one currency per counter — run a source per currency, or have your automation convert to a base currency before it rings the bell.