Glossary
What is a webhook?
A webhook is an automatic message one system sends to another the moment something happens, such as a new lead, a reply or a booked meeting. Instead of asking every few minutes whether anything changed, the receiving system is told at once. Sales teams use webhooks to connect tools without manual exports.
Published by Sellinger AI. Numbers and settings checked on 24 October 2026 against the fact register. Report an error.
How does a webhook work?
You give the sending system a URL. When the event happens, it sends a small message, usually JSON, to that URL with the details. The receiving system, such as your own server or a workflow tool like n8n, Zapier or Make, reads it and acts: creates a record, posts a notification or starts a step.
What are sales examples?
| Event | What the receiver does |
|---|---|
| A lead replied | Post the reply in a team channel |
| A meeting was booked | Create a deal in the CRM |
| A lead opted out | Add them to the do not contact list elsewhere |
| A form was submitted | Create a lead and start a campaign |
What should you check?
- That the receiving URL verifies where messages come from, for example with a shared secret.
- What happens when the receiver is down: does the sender retry?
- That the same event arriving twice does not create two records.
- That personal data in the payload is handled under your data rules.
How Sellinger handles it
Sellinger offers a REST API with webhooks (from the Full Stack bundle up) and a hosted MCP connector with 43 tools for Claude and ChatGPT. The API documentation covers authentication, and errors and limits the limits. Zapier, Make or n8n for lead handling compares the workflow tools.
Common questions
What is the difference between a webhook and an API?
Do I need a developer for webhooks?
Are webhooks secure?
Sources and method
General integration practice; examples are illustrative. Sellinger API from the fact register, checked 24 October 2026.
Related: Sales API, GTM engineer, API documentation, Zapier, Make or n8n.
