Webhook Security in Bubble 

Thanks Matt, I've purchased already the Canva template and proceeding with the bootcamp, but cannot say how much I've appreciated such RU-vid videos, truly valuable. Thanks a lot!

Thank is so helpful , thanks Matt

Hey Matt, nice video! Thanks! One comment: using "first item is not empty" is more WU and speed efficient than "count is 1"

Other than that, Mrs. Lincoln.... this video is amazing! TY for layout the hookdeck bubble horror show.

My wife was in the next room and thought I was watching a video about peyronie's disease 🤣 I was like "He's saying 'Hook DEHck', ya perv!" In all seriousness, this video was insanely helpful.

Great vid. I think right now it's even easier in hookdeck to just pick Stripe auth and then add bearer token auth for the destination. Your explanations are great though

I heard so many good things about you as a Bubble instructor. Now what is the difference between "Think it, build it" course and the "Air Dev No-code Bootcamp" ?

Hookdeck check if the Stripe hook is ok, how do you check Hookdeck hook is ok ???

Hey, super interested in your bubble course but I see you took quite a break here on RU-vid. Is the course information up to date?

When will you have the promotion code? (e_e) waiting for my Christmas bonus to buy and be part of your Bubble course.

Hi, Matt. I'm new to bubble and I'm having a hard time with conditions related whether the user is logged in or not. How do make my app notice the user is logged in and restrict them from activities if they aren't then prompt them to log in. Basically saying: If this user is logged in, allow them to do this and that but if they're not make them log in and once they are they can do stuff.

Mate HELP !!!!!!! Can you please for the love of sanity, please make A tutorial on how to make a blocking function that all messaging apps have from the ground up, showing how to set up the database and the logic and the workflow for the button. As no one and I mean no one has done this so far. Be the 1st to do this !!!!!!!

WTAF? Bubble has made a completely arbitrary unnecessary unhelpful design decision to not parse the payload properly that prevents a simple hash validation just to create the need out of thin air for a MIDDLEMAN called hookdeck - another point of EVERY TYPE of FAILURE - (owned by somone's brother-in-law, no doubt) so that webhooks ( a well-established industry standard web construct) work for PAYMENTS (a mission critical financial task) with STRIPE (one of the cornerstones of the modern online economy). WTAF. Who is to blame for this abortion? Is this some kind of a no-code no-sense blooper reel? Is this workaround hoop jumping crap all about the Bubble-folks wanting people to only use the Stripe plugin? Is that what's really going on here? Does using the Stripe plugin cost Bubble workunits (for the payment itself), but the API method in the video does not? At this point, this state of the art makes Bubble an impossible choice for any use that intends to scale larger than a local dog walking chain. While it's a safe bet that Bubble can infinite scale because Amazon can. And it's a safe bet that Stripe can infinite scale. The smart money on HOOKDECK being able to is ... NFW. NFW. There has to be more to this story. No one in their right mind would go through all the trouble of creating the most capable and beautiful no code client builder then ... punish people who want to use webhooks.