---
title: "Webhook: explained simply for businesses"
description: "What is a webhook? An automatic message a program sends as soon as something happens, such as a new enquiry. Explained simply, with an everyday example."
url: https://osai.solutions/en/ai-glossary/webhook
lang: en
dateModified: 2026-11-13
---

# Webhook

*Also called: Web hook, Callback URL*

**In short:** A webhook is an automatic message a program sends to a fixed web address when something happens, such as a submitted form or an incoming payment. The receiving program then starts a workflow.

## What is a webhook?

Programs learn in two ways that something has happened: they keep asking whether there is anything new, or the other program reports by itself. That report is a **webhook**.

Think of a doorbell. Without one, you would check the door every five minutes. With one, you keep working until it rings. A webhook is the doorbell between two programs.

## How does it work?

A webhook is set up once and then runs by itself:

- **Create the address:** The receiving program, such as [n8n](https://osai.solutions/en/ai-glossary/n8n), creates its own web address, the webhook URL.
- **Enter the address:** You add this address in the sending program, such as your website form or payment service.
- **The bell rings:** When someone submits the form, the details go there right away.
- **Workflow starts:** n8n takes the data and starts the [workflow](https://osai.solutions/en/ai-glossary/workflow), such as adding the enquiry to the [CRM](https://osai.solutions/en/ai-glossary/crm) and preparing a confirmation.

## Why does it matter for your business?

Because speed matters with enquiries. A webhook reports a new enquiry the moment it arrives, not at the next check. A workflow can then sort it, add it to the customer database and send you a message.

Webhooks also save the programs work: data only flows when there is something new, instead of endless asking. Many programs have a setting called “webhook” or “notification URL”.

## How does OsAI use it?

OsAI builds workflows with n8n, Make.com and Zapier plus AI steps. A webhook can be the starting point: a form, a calendar or a payment service reports in, and the workflow begins. A tool like n8n handles the fixed steps, the AI only the understanding of text. That keeps the workflow easy to follow.

The free [AI ROI calculator](https://osai.solutions/en/ai-roi-calculator) gives a rough idea of whether such a workflow pays off. Examples are in a guide [on n8n in a business](https://osai.solutions/de/blog/n8n-automatisierung-mittelstand) (in German).

## Frequently asked questions

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

With an [API](https://osai.solutions/en/ai-glossary/api), a program actively asks for data. A webhook arrives by itself as soon as something happens. Often both work together: the webhook reports “new order”, then the workflow fetches the details through the API.

### Is a webhook secure?

As secure as you keep the address. Anyone who knows the webhook URL can send it data and start a workflow. So treat it like a key and have the sender checked. n8n offers, among others, a password or header login and a list of allowed IP addresses.

### How do I set up a webhook in n8n?

You add the webhook node as the first step in n8n and copy the address it shows. n8n shows two addresses: one for testing and one for live use, which only works once the workflow is published. You enter the live one in the sending program.

## Sources

- [n8n: Dokumentation des Webhook-Knotens (abgerufen 13.11.2026)](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook)

Last updated: 2026-11-13
