#troop4christ_webhooks
worn ventureBOT
đ 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/1364376394129473566
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
chrome lark
Oh, I'm so sorry. Let me just read your notes there.
What I would do here is add a vaue to the Metadata on the Subscrtiption when your app does the cancellation; that way you'll know when it was you - and therefore when you don't need to send an email, right?
AKA: your hack is what I would use.
You could also set the portal to collect a cancellation_reason which would mean that would only be present when cancelled through the customer portal.
hollow merlin
Really?
So there's nothing that Stripe sets on the customer.subscription.update event, that would differentiate that event, if set programatically through the API, vs when a user cancels their subscription through the Portal?
chrome lark
Correct.
Many users don't need to differentiate those two; if you do, you can use one of the options mentioned above - i.e., keep doing what you're doing now, or start asking for a cancellation reason via the portal to get the opposite effect (i.e., identify the portal ones, vs identify the "our app did this" ones).
worn ventureBOT