Term · Web & development
Webhook
A webhook is an automatic notification that one system sends to another when something happens — a payment is completed, an order is created, a form is submitted, a message arrives. Instead of your system repeatedly asking "has anything changed?", the other system tells it immediately.
[ 01 ]
Explained
How it works
You give a service a URL on your server. When the event occurs, the service sends an HTTP request to that URL with details of the event. Your server processes it: marks an order as paid, creates a lead in the CRM, sends a notification.
Common uses
- Payment providers notifying that a payment succeeded or failed. See payment gateway integration.
- Messengers delivering incoming messages to a bot.
- CRMs and forms notifying other systems about new leads.
- Delivery services updating shipment status.
Using webhooks reliably
- Verify authenticity: check signatures or secrets so that forged requests cannot trigger actions.
- Handle duplicates: the same event may arrive more than once; process each only once.
- Respond quickly: acknowledge receipt, then process in the background.
- Handle failures: providers retry failed deliveries; log everything and alert on persistent errors.
- Do not trust the payload blindly: for critical actions, confirm the status through the provider's API.
[ 02 ]
FAQ
Frequently asked questions
What is the difference between a webhook and an API?
An API is something you call when you need data; a webhook calls you when an event happens. Integrations often use both.
Can no-code tools receive webhooks?
Yes. Tools such as n8n, Make and Zapier can receive webhooks and trigger workflows.