Once Stripe revenue data syncs onto your HubSpot Subscriptions, invoices, and Companies, your workflow tool gets a whole new set of triggers. These five are the ones teams reach for first. Each one names the exact synced property to trigger on, the action to take, and why it matters.
1. Churn-risk alert when a subscription goes past_due #
A subscription slipping to past_due is the earliest, cleanest churn signal you
have — and it usually goes unnoticed until renewal.
| Trigger | hs_status changes to past_due on a Subscription |
| Action | Create a task for the account owner + notify the CSM channel |
| Why | A failed renewal payment is a save opportunity, not a lost cause — but only if someone acts this week |
Enroll on the Subscription object so the alert fires per subscription, not per company. A multi-product account can have one line lapse while the rest stay healthy.
2. Expansion play when MRR increases #
When stripe_mrr goes up, the customer just voted with their wallet. That’s the
best possible moment to deepen the relationship.
| Trigger | stripe_mrr increases on a Subscription (or Company rollup) |
| Action | Notify the AE, add the account to an “Expanding” list, raise the health score |
| Why | Expanding customers are your warmest upsell and best reference pipeline — catch them while momentum is high |
3. Onboarding sequence on the first paid invoice #
The first successful payment is the real start of the customer relationship — more meaningful than a closed deal.
| Trigger | First invoice reaches hs_invoice_status = paid for the company |
| Action | Enroll the primary contact in the onboarding email sequence + create a kickoff task |
| Why | Onboarding that starts at first payment, not contract signature, lines up with when value delivery actually begins |
Use a “first paid invoice” property or a re-enrollment guard so the sequence fires once, not on every paid invoice thereafter.
4. Dunning hand-off to the CSM on a failed payment #
Automated dunning emails handle the routine retries. The human hand-off is for the accounts you can’t afford to lose.
| Trigger | hs_last_payment_amount payment fails / hs_status becomes past_due on a high-value subscription |
| Action | Branch on stripe_mrr — above your threshold, route to a CSM with a personal outreach task |
| Why | Mass dunning emails feel like spam to your biggest accounts; a personal note from their CSM recovers revenue and goodwill |
5. Renewal task before the billing term ends #
Renewals shouldn’t surprise anyone. hs_recurring_billing_end_date holds the
scheduled cancellation date, so it’s set only on subscriptions slated to cancel at
period end — this workflow enrolls those, not normal auto-renewals.
| Trigger | hs_recurring_billing_end_date is N days away (date-based enrollment) |
| Action | Create a renewal task for the owner; for annual terms, kick off a QBR sequence |
| Why | A renewal worked 60 days out is a conversation; one worked the day it lapses is a fire drill |
Pair this with
hs_recurring_billing_frequencyto set lead time per cadence — a longer runway for annual subscriptions, a shorter one for monthly.
Putting it together #
Each workflow above turns a synced property into an action your team would otherwise have to remember to take manually. Because the sync keeps those properties current in real time — and reconciles them nightly — the automations fire on facts, not stale snapshots.
For the full list of properties available to trigger on, see What syncs to what, and for build-ready report and workflow recipes see Example reports & workflows.