Skip to content
Tech Bits
All articles

What is a webhook?

A webhook lets a service tell your app when something happens. You give it a receiving URL, and it sends an HTTP request there when the chosen event occurs.

Alex submits your Webflow form. You want their details in a spreadsheet, without checking for new signups all day.

You’ve configured a webhook for new form submissions. Webflow sends the submission details to your automation’s endpoint. That notification is what starts the work.

Your automation reads the fields, decides which spreadsheet columns they belong in, and asks the Sheets API to add a row. Receiving the webhook and updating the sheet are separate steps; the notification alone does not do both.

The automation should also check that the notification came from the expected service, using that provider’s documented verification method.

A newly created message immediately rings a notification bell.

The service sends a notification after a form is submitted.

After an event, the form service sends a notification. Receiving it does not mean the follow-up work is complete.

A webhook is a request sent after an event, not a continuously open connection. Deliveries can be repeated, so your automation should recognise an event it has already handled.

Sources

Reviewed