Find Chargebee renewals missing a HubSpot deal
Match upcoming Chargebee subscription terms to explicit HubSpot renewal deals, with a per-subscription coverage check and a runnable SQL fixture.
Use Combined to turn billing term dates into a concrete renewal preparation queue. Match Chargebee customers to HubSpot companies, then link each subscription to the deal that actually covers its renewal. Your agent can distinguish ready renewals, missing sales coverage and scheduled cancellations.
Start with the business decision
Ask: “Which subscriptions ending in the next 30 days lack an open renewal deal due to close by the term end?” An account-level pipeline total can hide this gap. A customer may have two subscriptions and only one tracked renewal.
The result should suggest a next decision: review an uncovered renewal, inspect an overdue close date, or discuss an already scheduled cancellation. It should not automatically create deals or assume that every term boundary requires sales involvement. First agree which customer segment follows a sales-assisted renewal process.
Connect the records the question needs
Connect HubSpot and Chargebee. Inspect HubSpot companies, deals, owners and pipeline definitions. Chargebee's customer and subscription references supply the customer relationship, subscription state and current term boundary.
Use a term end for this coverage check, rather than assuming the next billing timestamp is the same milestone. Chargebee documents them separately. Subscription date reference. On the CRM side, use your configured renewal type or pipeline and the internal stage IDs described in the HubSpot deals reference.
Make the identity map explicit
Use two maps: Chargebee customer to HubSpot company, and Chargebee subscription to its intended HubSpot renewal deal. A deal custom property, a maintained mapping dataset or another explicit relationship can provide the second link. Confirm that both IDs are exposed in the synced data.
Check that the mapped deal belongs to the same company as the subscription's customer. Do not let a generic expansion deal cover every subscription under an account. Where one deal legitimately covers several subscriptions, list those relationships intentionally. Ambiguous or duplicate links belong in the output as mapping issues, not as successful coverage.
Define the metric and reporting window
The example includes active and non-renewing terms ending from September 10 inclusive to October 10 exclusive, 2026 UTC. For an active term, coverage requires an explicitly linked deal that is a renewal, remains open, belongs to the correct company and has an expected close at or before the term end.
A non-renewing subscription receives a cancellation-review action even if sales has a deal. An expansion deal and a closed deal do not establish open renewal coverage. “Ready” in the example only means those coverage checks passed; the account owner must still inspect a close date already in the past, a stale stage or a missing stakeholder.
Run the worked example
Atlas subscription s1 maps to an open renewal deal and is ready under the stated rule. Its second subscription maps to an expansion deal, so it needs renewal coverage. Birch's term is non-renewing and goes to cancellation review. A subscription ending exactly on October 10 is outside the 30-day queue.
Download the runnable SQL fixture and its expected result. The fixture uses synthetic records and normalized teaching tables. Run it in DuckDB; discover your own Combined datasets before adapting the calculation.
| Subscription | Company | Term end | Covering deals | Next action |
|---|---|---|---|---|
| s1 | Atlas | Sep 15 | 1 | Ready |
| s2 | Atlas | Sep 25 | 0 | Needs renewal deal |
| s3 | Birch | Sep 20 | 0 | Cancellation review |
Give your agent an exact assignment
Use my HubSpot and Chargebee sources in Combined.
Discover the actual schemas and validate customer/company and
subscription/renewal-deal maps, including company consistency.
Find active and non-renewing term ends in [2026-09-10, 2026-10-10), UTC.
A covering deal must be explicitly linked, open, classified as renewal,
and expected to close no later than that subscription's term end.
Classify non-renewing terms for cancellation review, uncovered active
terms as needing a renewal deal, and covered active terms as ready.
Flag past expected close dates and stale CRM activity separately.
Return subscription, company, term end, deal IDs, owner if available,
mapping exceptions, source freshness and query receipt. Read only.Return supporting records and the next decision for each account. Display a bounded list while calculating over the complete dataset.
Check coverage before acting on the answer
Subscription edits can move a term boundary or schedule cancellation. A CRM change can close the only covering deal. Display both successful-sync timestamps and recheck the source before making a customer-facing commitment. If the selected connector does not expose the custom subscription/deal link, add or sync the maintained mapping first. A company-name match is not a substitute.
Combined gives your agent a managed data layer across these sources, so the next question does not require another export. Start with 5 million MAR without a card, connect your apps, and use the Claude Code walkthrough or MCP setup reference.
Sources and further reading
Explore the documentation behind this guide. Product details checked on September 10, 2026.