Workflow triggers

Connect billing events to HubSpot automations.

Tier requirement

Building workflows requires HubSpot Professional or higher (HubSpot's gating). The property updates themselves land on any tier — Starter portals still get the synced data, cards and dashboard.

How triggers work

Billing events land in HubSpot as property updates on Contacts and Deals (see What Stripe Sync writes to HubSpot), so any workflow that can trigger on a contact or deal property change can react to billing:

• subscription started / renewed
• payment failed
• subscription past due
• dispute opened
• subscription canceled
• subscription paused or scheduled to cancel

Building one (example: dunning sequence)

1. In HubSpot, create a workflow triggered by a contact or deal property — e.g. Stripe Delinquent is true, or Stripe Last Payment Failure Date is known.
2. Add an email step for the customer.
3. Add a task for the account owner as a second touch.
4. Activate. Test with a test contact first.

Other typical uses: save-play tasks for churn-risk accounts (cancel at period end flag), CS handoffs on upgrade, flagging disputed accounts, trial-ending-this-week outreach.

Which fields to trigger on

The most useful trigger properties (full list in What Stripe Sync writes to HubSpot):

Property	Fires when
Stripe Subscription Status	Any lifecycle change (active, past_due, canceled…)
Stripe Delinquent (Contact)	Latest payment failed or subscription past due
Stripe Last Payment Failure Date (Contact)	A payment fails
Stripe Has Active Dispute	A dispute opens or closes
Stripe Cancel at Period End	A cancellation is scheduled
Stripe Trial End (Deal)	A trial is running — combine with a date rule

TIP

Properties update in real time as Stripe events arrive — usually seconds after the event. If a property looks stale for over an hour, see Troubleshooting.