#cubosgavin_webhooks
mild zealotBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1247094729666068553
đ Have more to share? Add details, code, screenshots, videos, etc. below.
stuck basalt
Yes you are right, it's due to the webhook enpoint type being "Connect". The connect webhook endpoint will only listen to events generated from your connected account, not your account. And that's why this event wasn't delivered to this endpoint.
marsh cove
Presumably it's totally normal to have a second non-connect webhook then? Can both have the very same URL?
stuck basalt
Yes you can create another webhook endpoint, but I won't suggest you reuse the URL.
marsh cove
Why not? I have everything already set up on my end.
dusk wigeon
You will likely want to listen to different events and perform different actions depending on if the events come from your Platform or Connect endpoints, e.g. you will want to check what account does the Connect event come from, while in Platform endpoint this is not needed.
marsh cove
That makes sense, thank you! You've helped me a lot.
dusk wigeon
Happy to help.