Sure.
So, usually “web hooks” are set up in external applications so that “when this thing happens” you get a trigger in your app. It is a lot simpler than polling every x minutes to ask is something has happened yet.
For example, in Stripe you set up a Webhook on Payment Success - “tell me when a payment has been made”.
In Bubble we do that via a Backend API workflow being external. So we give Stripe the URL of our API workflow and then it gets triggered. Workflow runs by something outside of Bubble. Can be VERY powerful.
In the case of Stripe, it does a POST to our URL. POST is like a “here do this”.
However, there are webhooks that want to do a GET to our URL. This really “should” not be a problem but Bubble only allows POST. So it has always been impossible to do natively.
We CAN have a GET on a DATA URL - but that is not really the same use case. We want to do some processing.
It was possible to turn the GET into a POST in AWS or Integromat.
Things like Instagram want to do a GET on your endpoint. No idea why.
Also, you might want to offer a GET service to external users. So they can query things that are beyond just a “get row from table”.
So … it is awesome because it really always should have been there.
And it allows us to offer really quite a full REST API implementation to customers. Which is pretty hardcore for no-code.