#AlexElie
clever drum
fair notch
That's part of the flow
You can unsubscribe from those events if you don't want them
What exactly is the problem you're having with these?
outer storm
no i need them. I need to log when a customer update his plan but also when he creates a subscription
so i guess ill only use update for both
fair notch
Using created makes sense at the beginning, but up to you to determine what the best fit is for your needs
outer storm
when i receive the updated hook is there any way i can know the customer was on which plan before updating?
fair notch
What do you mean?
for these events around creation, or later changes?
(I wouldn't expect any plan/price changes at creation time via Checkout)
For later changes, eg via the Customer Portal, you can inspect the previous_attributes on the event
outer storm
later, lets say the user update his subscription. when i receive the hook, the subscription object tells me which plan the customer is currently on. Any way to know which plna and was on before updating...
Ok nice ill check the previous attribute!
eternal widget
Yes previous_attribute is a very nice way to check things like previous plan