The biggest problem with webhooks is testing them. In a typical scenario you'll be developing your code on your machine, which is usually on a NATted wifi network or on a corporate VPN. How, then, does the third party's server trigger the webhook? They can't open a connection to you.
I find ngrok invaluable for working around this problem. Several other similar services are available of course, but IME none of them are as easy to use.
The biggest problem with webhooks is testing them. In a typical scenario you'll be developing your code on your machine, which is usually on a NATted wifi network or on a corporate VPN. How, then, does the third party's server trigger the webhook? They can't open a connection to you.
I find ngrok invaluable for working around this problem. Several other similar services are available of course, but IME none of them are as easy to use.
Hey, check out webhookrelay.com, built it many years ago especially for webhook testing and getting them to internal services:)