Map the revenue events
Separate charge succeeded, failed, refunded, disputed, and subscription events before writing anything into CRM.
Stripe + HubSpot workflow rescue
For teams that need Stripe charge events, HubSpot CRM records, and Slack revenue summaries connected with idempotency, retry handling, and a short runbook before production credentials are shared.
Operating plan
Separate charge succeeded, failed, refunded, disputed, and subscription events before writing anything into CRM.
Define the idempotency key, object matching, field mapping, and retry path so one payment does not create duplicate contacts or deals.
Leave test events, expected HubSpot writes, Slack summary examples, and the credential-rotation notes needed for production.
Related paths
Ready to start