What is Webhook?
Webhook: An HTTP request one system sends to another when an event happens, like a new order or payment, so the receiver can react in real time without polling.
A webhook is a callback over HTTP. You give a service (Stripe, Shopify, a CRM, a phone provider) a URL, and when a specified event happens, it sends a POST request to that URL with the event data. Your system receives it and acts: create a record, start a workflow, notify someone. It replaces polling, where you would repeatedly ask "anything new?"
Production webhook handling needs care. Verify the signature so you know the request came from the real sender. Respond quickly and process the work in a background queue, because senders time out and retry. Expect duplicates and out-of-order delivery, so make handlers idempotent. Log every event, and have a way to replay missed ones if your endpoint was down.
Why it matters when you build or buy AI
Most AI automations are started by webhooks, and most automation bugs live in webhook handling: double-processed orders, missed events during downtime, or unverified endpoints anyone can call. When you buy an automation, ask how it handles retries, duplicates, and outages. If the answer is "it just works," it has not been tested.
Example
Shopify sends an orders/create webhook. The handler verifies the HMAC signature, stores the event ID, queues the job, and returns 200 within a second. A duplicate delivery is ignored because the ID was already processed.
Related terms
More in Engineering
Book 20 minutes, or send a brief
A former CTO replies. You leave with a written plan and a fixed estimate.
Prefer LinkedIn? Connect with Harish.