A simple explanation of Webhooks.
I think of Webhooks as postcards between computers.
Small communications which are addressed, have a stamp to get them delivered and contain relatively short pieces of information (payload).
The address is a URL. Web sites have URL's that when loaded into a browser they display the content which is usually text, images or videos. But URL's do not need to content visible element and do not need to be visited using a browser like Chrome or Internet Explorer. Instead the page can contain code that reads the very long URL and extracts the information contained within it.
We can use Webhooks to send data to a page.
When the data get to the destination URL it can be used to fill in information at the destination system. Think of this as filling in a form.
Alternatively, the receiving URL can have code on it that is triggered by the Webhook to do something in return. That might be to initiated a computer programme within itself or to return information back to a URL (or both).
So I guess you are thinking that this is the playground of developers. It certainly is. However, there are some tools available that normal humans can use to simplify the use of these very helpful Webhooks.
One such tool is Zapier.
Zapier provides an array of tools for using Webhooks to interact with applications.
There is a good article that you can read here that described Webhooks and their use in some detail.
If you want some help with Webhooks or anything Zapier just let us know.