Webhook

A webhook is a notification between systems. Instead of one system repeatedly asking another whether anything is new, the source system sends a message as soon as something happens: a form is submitted, a payment succeeds, a call ends, a document is signed.

How it works

You give the source system a URL, called the webhook endpoint. When the chosen event occurs, the source sends a web request to that URL with details of the event, usually as JSON. The receiving system reads it and starts whatever should happen next.

Webhooks and APIs work together. The webhook says "this happened"; the receiving system then often calls an API to fetch more detail or take action.

Doing it reliably

Webhooks are fast but need care:

• Verify the sender. Check the signature or shared secret that proves the message came from the source.
• Expect duplicates. Many senders retry when they do not get a quick confirmation, so the same event can arrive twice. Process each event only once.
• Log everything. Keep a record of received events so failures can be found and replayed.
• Alert on silence. If messages stop arriving, someone should know.

How it works in a business

Webhooks make instant response possible. A form submission can trigger a text and a callback within seconds, which is what good speed to lead depends on.

How it relates to Worcia

Webhooks connect events across Worcia's builds, especially in Maestro, its workflow automation, and Cadenza, its lead follow-up system. See 40 workflow automation examples.