What it does
Use when a user mentions "stripe subscription sync", "subscription state workflow", "billing event integration", or asks for related help. When Stripe sends a subscription_created / updated / cancelled / payment_failed event, sync the state to the user profile + account lifecycle stage, so segmentation, retention, and reporting always reflect actual billing reality.
You get
Attribute
AI-Derived Attribute produced by this recipe.
Workflow
Workflow produced by this recipe.
Dashboard
Dashboard produced by this recipe.
How it works
Build Billing State Attributes
create_attributeCreate attributes on the User object:
Build Stripe Sync Workflow
Create WorkflowCreate a workflow firing on Stripe webhook events. Step sequence: (1) parse the Stripe event payload (subscription_created/updated/canceled/payment_failed/invoice_paid); (2) match to user via stripe_customer_id (create user if doesn
Build Billing Data Integrity Dashboard
Build DashboardCompose a billing-data integrity dashboard: % of users with subscription_status synced (against Stripe ground-truth — should be 100%), webhook delivery failure count (signal of integration issues), users with billing-attribute drift (Stripe shows active but profile shows cancelled = sync bug), and MRR computed-from-profile-attributes vs. MRR-from-Stripe-API (should match within 1%). This is the recipe that makes every other recipe
Ready to run this recipe?
Tell Blu what you need. It builds the segment, content, journey, and dashboard in minutes.
Sign up free