The Problem
A SaaS company's finance and customer success teams were manually monitoring Stripe for payment events, then updating HubSpot contacts, creating deals, and triggering onboarding emails by hand. This dual-system management consumed 2–3 hours daily and frequently caused 1–2 day delays before new customers received their welcome and onboarding sequence.
- Manual process: Stripe → export CSV → cross-reference HubSpot → update records
- New customers waited up to 48 hours to receive onboarding emails
- Cancelled subscriptions not flagged in HubSpot for weeks — no churn response triggered
- Failed payments not tracked — customers quietly churning undetected
The Solution
I built a complete Stripe webhook processor in Make.com that listens for 8 different Stripe event types and executes tailored HubSpot actions instantly for each one.
The architecture uses a single Make.com webhook as the entry point. A Router module branches the flow based on the event type field in the Stripe payload. Each of the 8 branches handles a specific scenario.
"Every payment event that happens in Stripe now reflects in HubSpot within 15 seconds —
automatically, without any human intervention."
The 8 Event Types Handled
- payment_intent.succeeded → Update deal stage to Closed Won + trigger onboarding
- customer.subscription.created → Set lifecycle stage to Customer + enroll in welcome sequence
- customer.subscription.updated → Update plan tier property in HubSpot
- customer.subscription.deleted → Tag as Churned + notify CS team + enroll in win-back
- invoice.payment_failed → Add dunning tag + create CS task + send alert
- invoice.payment_succeeded → Log MRR value to custom HubSpot property
- customer.updated → Sync email/name changes from Stripe to HubSpot
- charge.refunded → Flag contact + create finance task for review
Technical Architecture
The Results
- 12 hours/week recovered from manual CRM maintenance work
- All 8 Stripe event types now covered — 100% payment visibility in HubSpot
- Onboarding delay: from 1-2 days → under 15 seconds after payment confirms
- Churn detection and win-back campaign triggered automatically every cancellation
- Failed payment dunning sequence deployed — recovered 3 previously lost subscriptions in month one