Workflow actions

Connect billing events to HubSpot automations, and Stripe actions to workflow steps.

Triggers (Stripe → HubSpot workflows)

Billing events land in HubSpot as timeline events and property updates, so any workflow that can trigger on a contact/deal property change or timeline event can react to billing:

• subscription started / renewed
• payment failed
• subscription past due
• dispute opened
• subscription canceled

Typical uses: dunning email sequences, save-play tasks for churn-risk accounts, CS handoffs on upgrade, flagging disputed accounts.

Actions (HubSpot workflows → Stripe)

Stripe Sync ships custom workflow actions you can drop into any HubSpot workflow. Each acts on the subscription linked to the enrollment's Contact/Deal:

Action	Effect
Cancel subscription	Cancels at period end (same as the card action).
Pause subscription	Pauses collection at period end.
Refund latest invoice	Refunds the most recent invoice's payment.

Actions respect the same audit logging as the sidebar cards. HubSpot's workflow engine calls Stripe Sync server-to-server — the acting user is the workflow, noted in the audit entry.

Building one (example: dunning sequence)

1. In HubSpot, create a workflow triggered by subscription past due (a contact property Stripe Sync keeps current).
2. Add an email step for the customer.
3. Optionally add Pause subscription after N days of no payment, or leave the sequence purely communicative.
4. Activate. Test with a test contact first — actions hit your live Stripe account.

TIP

Workflow actions are real Stripe mutations. Prefer notification-first sequences, and only automate money-moving actions (refunds) where a human reviews the trigger list.