Webhook
A webhook is an automatic message a system sends the moment something happens, for example a new booking. Another system catches that message and responds to it right away, without having to wait or ask.
The difference from a regular API request is the direction. With an API, you actively ask for data. With a webhook, the system pushes the information to you the moment something changes. That makes integrations faster and more efficient, because you don't have to keep checking whether there's anything new.
Webhooks are the glue under a lot of workflow automation. Something happens, and a chain of actions starts right away.
In practice.
In the automations I build, workflows often start with a webhook. As soon as a sign-up or payment comes in, the rest of the process gets going on its own.
Frequently asked questions.
What is a webhook?
An automatic message a system sends the moment something happens, like a new booking. Another system catches it and responds right away, without having to wait or keep checking.
What's the difference between a webhook and an API?
With an API, you actively ask for data. With a webhook, the system pushes the information to you the moment something changes. So a webhook is faster for events you want to process right away.
Related terms.
Want to see how this works in practice? Have a look at Automation and integrations.
Curious what this could do for you?
Walk me through one process. In half an hour I will show you where this kind of work gets stuck in your business, and what it would save to hand it off.