Connect your revenue (Stripe and Measure)
Bring billing into Airhop with Stripe and Measure so health, triggers, and the agent see who is paying.
Connecting your revenue folds billing into the accounts and health picture, alongside product events and call sentiment. Once it is connected, the agent knows who is paying, who is overdue, whose usage is climbing, and whose renewal is close, and it can act on those signals through playbooks.
Airhop reads two billing systems directly, and normalizes both into the same shape so the rest of the product does not care which one you run:
- Stripe, connected with Stripe Connect (one click, read only).
- Measure (getmeasure.com), connected with an API key.
This is a customer-success capability, not a support one. You will only be prompted to connect revenue inside the Accounts and Playbooks surfaces, never during the basic support setup.
Connect Stripe
- Open Connectors and find the Revenue section.
- Click Connect with Stripe. You are taken to Stripe's consent screen.
- Approve the connection. Airhop requests read only access, so it can never change anything in your Stripe account.
That is it. Airhop pulls your current customers, subscriptions, and invoices in the background, and from then on Stripe pushes changes to Airhop in real time.
Connect Measure
- In Connectors, under Revenue, open the Measure form.
- Paste your Measure API key (and the webhook signing secret, if you use one).
- Save. Airhop backfills your customers and listens for Measure webhooks.
Choose a primary source
If you connect both Stripe and Measure, pick a primary revenue source in the Revenue section. The primary source owns the revenue numbers (MRR, ARR, renewal date); the other still contributes payment events.
A good rule of thumb: choose Measure if you meter usage and recognize revenue there, and Stripe if Stripe is your system of record.
What flows in
For each billing customer, Airhop maps it to an account (by domain, or the stored customer id) and keeps a normalized snapshot:
| Field | Meaning |
|---|---|
| MRR and ARR | Monthly and annual recurring revenue. |
| Plan | The current plan or tier. |
| Billing status | active, past_due, canceled, or trialing. |
| Usage | Percent of the plan entitlement consumed. |
| Payment health | ok, failed, or card_expiring. |
| Renewal date | The next billing or renewal date, which also powers renewal_approaching. |
| Invoices | A rolling window of recent invoices and their status. |
You can see all of this on the account's Revenue panel.
How it feeds health
Billing is one of the strongest churn signals there is, so it is wired into health directly: a failed payment or an overdue or failed invoice caps an account's health no matter how active its users look. A paying account that just bounced a payment will not read as healthy.
Billing triggers
Connecting revenue unlocks three new playbook triggers:
| Trigger | Fires when |
|---|---|
payment_failed | A payment fails for the account. |
invoice_overdue | An invoice goes overdue. |
usage_over_plan | Usage exceeds the plan entitlement (an expansion signal). |
When one fires, Airhop flags the account for your CSM and can reach out to the account's contacts through a playbook. As with every customer-facing play, you choose whether the agent sends automatically or drafts the message for your approval first.
Staying current
You do not need to configure anything for freshness:
- Stripe Connect delivers events to Airhop in real time through a single platform webhook, for every connected account.
- Measure pushes events to a per-connector webhook.
- A nightly reconcile re-pulls everything as a backstop, in case an event was missed.
What Airhop never does
Airhop's billing access is read only. It never creates charges, changes subscriptions, issues refunds, or writes anything back to Stripe or Measure. It reads your revenue so it can act on customer success, nothing more.