#yamith_webhooks
dawn tideBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1338541055557238915
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
cosmic gullBOT
velvet snow
Hi there 👋 I see the first Event was created about a minute before the other two, does that imply the two later Event IDs you shared are the ones that you think are duplicates?
viral fox
The first is when I update the sub, but it does not take effect yet because it is changed at the end of the period, and the other two are when the subscription change is already made at the end of the period, this with the test clock
velvet snow
Sorry, can you clarify which ones you think are duplicates then?
Looking at the previous_attributes hash in each Event, I'm seeing that each one is notifying you of a different change being made to the Subscription:
https://docs.stripe.com/api/events/object#event_object-data-previous_attributes
viral fox
The request data of the webhook does not let me access previous_attributes, there is one that is previous_attributes metadata foo
velvet snow
Can you elaborate on what that means? All of these Event objects should contain a data.previous_attributes hash.
viral fox
I understand that all Event objects should contain data.previous_attributes, but when I try to access it in Bubble.io's webhook workflow, it doesn’t appear as an available field. The only thing I can see is previous_attributes.metadata.foo, but not previous_attributes itself.
velvet snow
I'd suggest speaking to the Bubble's support team then. To understand how to use their abstraction to interact with our objects the way you need to.