How Webhooks work in Bubble
Vložit
- čas přidán 16. 07. 2024
- 🎓 This is a free lesson from my zero-to-hero Bubble course 👉 thinkitbuildit.co
IN THIS VIDEO
You'll learn what Webhooks are, how they work, and how to set them up in Bubble.
Make sure to also check out the next video on Webhook security - • Webhook Security in Bu...
⌚ TABLE OF CONTENTS
00:00 What are web hooks
07:20 What we’ll be building
09:12 A note on the native Bubble Stripe plugin
10:29 Overview of our Stripe integration
21:32 Setting up our first webhook
29:45 Connecting our webhook to our app
42:46 Real-ish life example
50:36 Closing remarks
Genuine review from a paid student: Matt is one of the best educators in Bubble sphere - to Matt, your courses (Airdev and personal) accelerated my career as a PM to the point where I can quickly create an MVP for my team without having to go through lengthy brief meetings. This cuts down the prototyping time 10x
Just wanna show appreciation. Thanks so much
Thanks so much - super appreciate this and glad to have been of service! :D
I'm glad that you back dear Matt! Please keep going, you're doing really well! :)
Most awaited video
Thanks Matt!
Welcome back😅
Am currently struggling to get an API call on stable diffusion image to image. 😢😢😢
Do you have any tutorial on that?
you are great
Boss how can I reach you to talk ? Please reply
I have a question regarding the Private Field. Big fan of your teaching, by the way - beginner student of your Thinkit-Buildit course.
If the Query String Check Box is ticked which means that info is placed into the URL that's being sent. So if they Private Check Box is ALSO checked (both Private & Query String check boxes are ticked) HOW does it keep the information for that field PRIVATE? It's within the URL that's being sent back.
Is the private information somehow encoded so it's disguised in the URL? If this was discussed in the video, my apology, maybe let me know the time code where you cover this.
Hey Jon!
It’s a great question.
Private simply means that the input for that parameter isn’t exposed within the bubble editor and in the client-side code.
All api calls are made from the backend (Bubble handles this for you) so private just means the value is static and inserted on the backend itself. This article explains it well manual.bubble.io/help-guides/infrastructure/security/api-security/api-connector-security#parameters
That's what is confusing. IF the Query String is NOT exposed in the ULR, then HOW is the parameter being read? Sounds like invisible ink of some sort (ha) @@mneary
@@thinkjon it is exposed in the URL. Think of what you setup in the API connector as simply the setup instructions for an HTTP request which is made from Bubble's server. That request includes your parameter, it's just not exposed in your app's client side code (nor the editor interface).
When we tick the PRIVATE checkbox, the parameter will be exposed in the URL, but NOT in the client side web browser INSPECT code. Is this correct? So anyone who understands this can simply find it in the URL. This is not private, so WHY do they call it private? @@mneary
Promo`SM 🙋
very good, and also could be much more shorter for explanation.