# Webhook

> A webhook is a notification mechanism in which a system automatically sends an HTTP request to a predefined URL when a specific event occurs, so that another system learns about the event immediately. For events such as a new order, a completed payment or a submitted form, you do not need to keep polling the other system. The information comes to you and your flow starts at once.

URL: https://corrplus.net/glossary/webhook/
Updated: 2026-11-10
Corrplus Team

**Definition:** A webhook is a notification mechanism in which a system automatically sends an HTTP request to a predefined URL when a specific event occurs, so that another system learns about the event immediately.

## How does a webhook work?

You first create a URL on the receiving system. You register that URL in the settings of the sending system and choose which events to listen to. When an event occurs, the sender makes an HTTP POST request to the URL. The request body carries the event details, usually as JSON.

The receiver verifies the request and returns a success response quickly. Doing the real work in the background is good practice. The same event can arrive more than once, so the processing should be safe to repeat.

## When should you use a webhook?

When you need to react to an event as it happens. Typical cases are starting fulfilment when a payment is confirmed, creating a CRM record when a form is submitted, or messaging a customer when a shipment status changes.

In tools such as [n8n](/glossary/n8n/) and Make, the webhook is the most common trigger. After the event arrives, [API integration](/glossary/api-integration/) takes over to fetch details or write to another system. Starting an [AI agent](/glossary/ai-agent/) from an incoming event works the same way.

## What to watch for

Supported events, payload formats and retry behaviour differ between providers. Check the current documentation before you build on them. This applies to payment providers, carriers, marketplaces and messaging channels alike.

Webhook payloads often contain personal data such as names, phone numbers and addresses. Review how long your automation tool keeps execution logs, under GDPR or, for data from Türkiye, KVKK, Türkiye's data protection law. Self-hosting the tool makes it easier to decide where that data sits. See [n8n and Make automation](/services/workflow-automation/n8n-make-automation/) for setup options.

## Frequently asked questions

### What is the difference between a webhook and an API?

With an API, you start the request and receive the response. A webhook works the other way round: when an event occurs, the other system sends a request to you. That is why webhooks are sometimes called reverse APIs. Most integrations use both.

### Are webhooks secure?

They are if set up properly. The URL should use HTTPS, the signature or shared secret of each incoming request should be verified, and the sender should be checked. Without verification, anyone who knows the URL can send fake events.

### What happens if a webhook delivery is missed?

If your system is down at that moment, the event can be lost. Many services retry failed deliveries for a while, but behaviour differs by provider. For critical flows, log events and reconcile periodically through the API.
