How Chargebee customers, subscriptions, invoices and payments can give every HubSpot company a live revenue picture, and how HubSpot deals can become Chargebee quotes and subscriptions.
Chargebee runs subscription billing: plans and add-ons, recurring invoices, payment collection and dunning. HubSpot holds the customer relationship and the pipeline. This assessment shows how to connect the two so revenue and relationship data sit on the same record.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. Self-serve: the API is documented publicly, and keys are created in Chargebee's settings.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Chargebee's documented REST API and webhooks let HubSpot show what every customer pays, what they owe, and when they renew.
Campaign Creators assessment
Chargebee publishes its own HubSpot apps. Chargebee for HubSpot syncs customers, subscriptions and orders into contacts, companies and deals, and the HubSpot Quote-to-Cash app adds product sync and subscription creation from deals. They are the natural starting point. A custom build on the Chargebee REST API v2 and its webhooks extends them with subscription and invoice records, company-level MRR and ARR rollups, dunning status for customer success, usage, multiple sites and business entities, and deal-to-quote write-back shaped around the client's sales process.
Ratings are CC judgments from Chargebee's public API documentation. Plan features, limits and the scope of Chargebee's own apps are confirmed for the client's account during discovery.
Chargebee emits documented events for customers, subscriptions, invoices, credit notes, payments, quotes and dunning, so HubSpot can follow billing within minutes.
If Chargebee's HubSpot app stays on, each field and deal stage gets one writer. The custom build adds to the app rather than writing over it.
Finance signs off how MRR, ARR, churn and renewal dates are calculated, and which currency they report in, before any rollup is built.
Seven Chargebee capabilities matter to a HubSpot build. Five carry the integration, one enriches it, and one is the starting point the build extends.
The billing account: contact details, billing address, currency, payment terms and auto-collection.
Each subscription with its status, plan and add-on items, MRR, billing period, term dates and contract term.
mrr, current_term_end, next_billing_atWhat each customer was billed, what they paid, what is overdue and where dunning stands.
status, amount_due, due_datedunning_status: in_progress, exhausted, stopped, successChargebee posts an event for every change. The integration keeps HubSpot current from these events and re-reads the resource for its latest state.
subscription_created, subscription_cancelled, subscription_renewedinvoice_generated, payment_failed, dunning_updatedA HubSpot deal with line items becomes a Chargebee quote for a new subscription, and an accepted quote converts into the subscription.
Consumption recorded against metered item prices. Usage trends show expansion and risk signals on the HubSpot record.
Chargebee's own apps sync customers, subscriptions and orders to contacts, companies and deals, sync products, and create subscriptions from deals. The custom build extends what they cover.
Chargebee webhooks reach a CC-hosted integration layer, which verifies each event by reading it back from the API, keeps the latest version of each resource, computes revenue rollups and writes HubSpot records. HubSpot deals call back into Chargebee to create quotes and customers.
Prices, invoices, payments and MRR are calculated by Chargebee. HubSpot stores them as reported and never recalculates a bill.
Companies, contacts, owners and the sales pipeline live in HubSpot. Chargebee customers link to them, not the other way round.
Where Chargebee's own app already writes a field or deal stage, the custom build leaves it alone. The split is written into the SOW.
Each phase ends on a gate the client signs off before the next begins, so the fixed scope holds even if the account setup differs from the public docs.
List the Chargebee sites and business entities, the plan, and which Chargebee HubSpot apps are installed and what they write. Issue test-site API keys.
Finance agrees how MRR, ARR, renewal date and churn are defined and which currency reports use. Agree which system and which app writes each field.
Create the Subscription and Invoice custom objects, company rollups, product properties, renewal pipeline and dunning ticket pipeline in a HubSpot sandbox.
Build the webhook endpoint, event re-read, version checks, revenue engine and HubSpot writer against the Chargebee test site.
Build deal-to-quote and quote-to-subscription flows, and customer creation from HubSpot, with validation against the synced catalog.
Load customers, active subscriptions, open invoices and an agreed history window through the list APIs, then compute rollups once.
Switch to the live site with workflows paused, run two weeks in parallel, then switch on dunning and renewal automations.
Attribute names follow Chargebee's API reference. Custom fields and the exact HubSpot objects for subscriptions and invoices are confirmed during discovery. Chargebee amounts are in the currency's minor unit and are converted before writing.
| Chargebee field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers → companies & contacts | ||||
| customer.id + site | cb_customer_id, cb_site | Company | CB → HS | Unique per site; both stored. |
| customer email | Contact | ↔ Both | Match key for the billing contact. | |
| customer first and last name | firstname, lastname | Contact | ↔ Both | Fill blanks only; HubSpot edits stay in HubSpot. |
| customer company | name | Company | ↔ Both | Company created in HubSpot, then linked. |
| billing address | address, city, state, zip, country | Company | CB → HS | Country names normalized to HubSpot values. |
| preferred currency | cb_currency | Company | CB → HS | Drives currency on related deals. |
| auto collection, net term days | cb_auto_collection, cb_net_term_days | Company | CB → HS | Confirm field names in discovery. |
| Subscriptions → Subscription object & rollups | ||||
| subscription.id | cb_subscription_id | Subscription (custom object) | CB → HS | Unique key. |
| status | cb_status | Subscription (custom object) | CB → HS | future, in_trial, active, non_renewing, paused, cancelled, transferred. |
| mrr | cb_mrr | Subscription (custom object) | CB → HS | Converted from minor units. |
| subscription_items | Line items | Subscription (custom object) | CB → HS | Plan, add-ons and charges with quantity. |
| current_term_end | cb_renewal_date | Subscription (custom object) | CB → HS | Feeds the renewal pipeline. |
| trial_end | cb_trial_end | Subscription (custom object) | CB → HS | Trial conversion workflows. |
| cancelled_at, cancel_reason_code | cb_cancelled_at, cb_cancel_reason | Subscription (custom object) | CB → HS | Churn reporting. |
| sum(mrr) of active subscriptions | cb_company_mrr | Company | CB → HS | Computed in the integration layer. |
| cb_company_mrr × 12 | cb_company_arr | Company | CB → HS | Per the signed revenue definitions. |
| Invoices, payments & dunning | ||||
| invoice.id | cb_invoice_id | Invoice (custom object) | CB → HS | Unique key. |
| status | cb_invoice_status | Invoice (custom object) | CB → HS | paid, posted, payment_due, not_paid, voided, pending. |
| total, amount_due | cb_invoice_total, cb_amount_due | Invoice (custom object) | CB → HS | Converted from minor units. |
| due_date | cb_due_date | Invoice (custom object) | CB → HS | |
| dunning_status | cb_dunning_status | Company | CB → HS | Latest across open invoices. |
| payment_failed event | Task or Ticket | Ticket | CB → HS | Routed to the account owner or customer success. |
| credit_note_created event | Custom event: Credit note issued | Company | CB → HS | Amount and reason as event properties. |
| Catalog, quotes & write-back | ||||
| item_price (id, price, period) | Product (hs_sku = item price ID) | Product | CB → HS | Chargebee owns the catalog. |
| HubSpot deal line items | create_subscription_quote_for_items | Deal | HS → CB | Quote created for the linked customer. |
| HubSpot company and contact | Chargebee customer (create) | Company | HS → CB | Only when a deal reaches the agreed stage. |
| quote_created / quote_updated events | cb_quote_id, cb_quote_status | Deal | CB → HS | |
| Converted quote → subscription_created | Deal stage: Closed won | Deal | CB → HS | Subscription associated to the deal. |
| Usage | ||||
| usages per item price | cb_usage_current_term | Subscription (custom object) | CB → HS | Rolled up per term; metered items only. |
Chargebee uses API keys per site; HubSpot uses one app token. Values Chargebee does not publish are marked for confirmation.
| Topic | Chargebee | HubSpot |
|---|---|---|
| Authentication | HTTP Basic with the API key as the username and an empty password. Test and live sites have separate keys. Read-only keys for inbound; a full-access key only where write-back is in scope. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Base URL & sites | https://{site}.chargebee.com/api/v2. Each site has its own keys, catalog and customers; business entities can sit within a site. | One API domain for all portals. |
| Webhook security | Basic authentication on the webhook URL; HMAC signing is not offered. CC verifies each event by retrieving it through the Events API before acting on it. | HubSpot signs its own webhooks with a v3 signature. |
| Delivery & ordering | Retried up to 7 times with increasing intervals; delivery can be out of order and repeated. De-duplicate on event ID and compare resource_version. | Writes are immediate; batch endpoints handle volume. |
| Rate limits | Published per plan: 150 to 3,500 requests per minute on live sites, 150 on test sites. Exceeding them returns HTTP 429. Confirm the client's limit. | Per-10-second burst and daily limits by subscription tier. |
| Data formats | Amounts in the currency's minor unit; timestamps as UTC seconds. | Currency amounts as decimals; dates in UTC. |
| Plans & licensing | Chargebee for HubSpot lists Rise or Scale as required; Quote-to-Cash quotes are a paid feature. Confirm plan features in discovery. | Custom objects need an Enterprise hub; Quote-to-Cash needs Sales Hub Professional or higher. |
Severity reflects impact on the SOW, not technical difficulty alone.
Chargebee's app can create deals and move stages. If both it and the custom build write deals, they collide. The SOW names one owner for each deal pipeline and field.
Each subscription reports MRR in its own currency. Finance picks a reporting currency and rate source before company rollups are built.
One deal per subscription, per renewal, or per expansion changes every report. Agree the pipeline design before backfill.
Chargebee webhooks use basic authentication, not signatures. The integration re-reads every event from the API, so a forged call changes nothing.
IDs are unique per site, not across sites. Every key is stored with its site, and catalogs are kept apart.
Amounts arrive in cents or the currency's minor unit, and tiered prices have several price points. The writer converts amounts and stores tier detail where the client needs it.
MRR, ARR, active plans and next renewal sit on the company record, ready for lists, views and reports.
A failed payment or exhausted dunning opens a task or ticket for the owner, with the invoice attached, before the customer churns.
Renewal deals are created ahead of the term end, so account managers see every renewal in one pipeline.
Sales builds the deal in HubSpot and sends a Chargebee quote; acceptance creates the subscription and closes the deal.
Customers near a usage threshold enter an upsell list for their owner.
Cancellation reasons and dates sit beside marketing source and owner, so leaders see why customers leave.
Chargebee's own HubSpot app and the custom build share one HubSpot data model, so the work can be delivered in stages that each stand on their own.
All custom properties use the cb_ prefix in a Chargebee property group. Rollups are calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| cb_customer_id | Chargebee Customer ID | Company | Single-line text | customer.id; unique with cb_site |
| cb_site | Chargebee Site | Company | Dropdown | Site the customer belongs to |
| cb_company_mrr | MRR | Company | Number (currency) | Sum of active subscription mrr |
| cb_company_arr | ARR | Company | Number (currency) | MRR × 12, per signed definition |
| cb_active_subscriptions | Active Subscriptions | Company | Number | Count of active and non_renewing |
| cb_next_renewal_date | Next Renewal | Company | Date | Earliest current_term_end |
| cb_dunning_status | Dunning Status | Company | Dropdown | Latest invoice dunning_status |
| cb_amount_due | Amount Due | Company | Number (currency) | Sum of open invoice amount_due |
| cb_subscription_id | Chargebee Subscription ID | Subscription | Single-line text | subscription.id; unique |
| cb_status | Subscription Status | Subscription | Dropdown | subscription.status |
| cb_invoice_id | Chargebee Invoice ID | Invoice | Single-line text | invoice.id; unique |
| cb_quote_id | Chargebee Quote ID | Deal | Single-line text | Quote created from the deal |
Choose the modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation. Each item marked for confirmation is verified against the client's Chargebee sites during discovery.
Yes. Chargebee publishes its own HubSpot apps: Chargebee for HubSpot syncs customers, subscriptions and orders into contacts, companies and deals, and the HubSpot Quote-to-Cash app adds product sync and subscription creation from deals. Campaign Creators extends them with a custom build on the Chargebee REST API v2 and webhooks for subscription and invoice records, company MRR and ARR rollups, dunning status, usage, multiple sites and deal-to-quote write-back.
Chargebee customers sync to HubSpot companies and contacts; subscriptions and invoices sync to custom objects with status, MRR, renewal date, amount due and dunning status; and plans, add-ons and charges become HubSpot products. HubSpot deals with line items create Chargebee quotes, and an accepted quote converts into a subscription and closes the deal as won.
Chargebee owns billing: prices, invoices, payments and MRR are calculated in Chargebee, and HubSpot stores them as reported. HubSpot owns the relationship: companies, contacts, owners and the sales pipeline. Where Chargebee's own HubSpot app already writes a field or deal stage, the custom build leaves it alone, so each field has one writer.
Seven phases, each closed by a client sign-off: discovery and access, revenue definitions and field ownership, the HubSpot data model, the inbound webhook build, the quote write-back build, a backfill of customers, subscriptions and open invoices, and a two-week parallel run before dunning and renewal automations are switched on.
Timeline and cost depend on what is in scope, such as the number of Chargebee sites and business entities, which Chargebee HubSpot apps stay on, multi-currency reporting and quote write-back. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.