Settings

Your profile, how Chronicle looks and which alerts reach you.

Connections3 available to add
4 / 7

Tools Chronicle reads revenue from and sends alerts to. The billing provider is the one every number depends on.

  • Billing provider4 min ago
  • Data warehouseToday, 02:00
  • Team chat12 min ago
  • Calendar1 hour ago

Revenue data

Where MRR, accounts and seats come from.

  • Billing providerConnected

    Subscriptions, invoices and failed payments. Every MRR figure starts here.

    Last sync 4 min ago

  • Data warehouseConnected

    A nightly copy of accounts, users and MRR movement for your own queries.

    Last sync Today, 02:00

Where alerts go

Where the team hears about payments and renewals.

  • Team chatConnected

    Failed payments and churn posted to the revenue channel as they happen.

    Last sync 12 min ago

  • CalendarConnected

    Renewal calls and QBRs on the Calendar page, both ways.

    Last sync 1 hour ago

Customer context

Context that sits beside each account and user.

  • CRMNot connected

    Account health and seat usage on each deal record, so sales sees risk early.

  • Product analyticsNot connected

    Weekly active seats per account, for the usage heatmap and health score.

  • Support deskNot connected

    Open tickets beside each user, and a note when a payment fails.

Webhooks

Chronicle posts these events to your endpoints, signed with your workspace secret.

  • https://hooks.example.com/chronicle/revenuepayment_failed, churn · 200 OK, 9 min ago
    Delivering
  • https://ops.example.com/webhooks/seatsseat_limit_exceeded · 200 OK, 2 hours ago
    Delivering