Automation and integration
Webhook
A webhook is a message one system sends to a URL in another system the moment something happens, such as a paid invoice or a new order, so the receiver can act without polling.
How it works in practice
Without webhooks, an integration has to ask a system every few minutes whether anything changed. With a webhook, the source system calls you: Stripe posts a payment event, Shopify posts a new order, a form tool posts a submission. The receiver reads the payload and starts a workflow.
Webhooks need care to be reliable. Senders retry on failure, so the same event can arrive twice and the receiver should be idempotent. Payloads should be verified with the sender’s signature so nobody can fake one. And because a missed webhook is silent, a periodic check that compares both systems catches what slipped through.
A worked example
A subscription business receives Stripe webhooks for failed payments. Each event updates the customer in HubSpot and starts a reminder sequence. A nightly job compares Stripe and HubSpot and fixes any account where a webhook was missed.
Examples in this glossary describe typical builds for companies of 1 to 1,000 people. They are not named client results.















