What is a webhook?
A webhook is event-driven integration: when something happens, the source system pushes a message rather than waiting to be asked.
It is what makes integrations react in real time, instead of on a delayed polling schedule.
Short answer
A webhook is an automated message a system sends to another the instant an event happens - a real-time notification with data, delivered to a URL the receiving system listens on. Webhooks let systems react immediately to events like a new lead or a closed deal, powering real-time integrations without one system constantly polling the other for changes.
Key takeaways
- An automated message sent the instant an event happens.
- Pushes data to a URL the receiving system listens on.
- Enables real-time reactions across systems.
- More immediate than polling for changes.
Why it matters
Webhooks make integrations instant. Instead of one system repeatedly asking another "anything new?", the source pushes an event the moment it occurs, so a new lead or closed deal triggers action in another system immediately. This real-time responsiveness is what many modern integrations depend on.
How Ardovo handles it
Ardovo supports webhooks so events like new leads and closed deals push to connected systems in real time, and Rook can trigger workflows on incoming webhook events. Integrations react instantly rather than on a delay, keeping connected tools responsive to what happens in the CRM.
Frequently asked questions
How does a webhook work?
When a defined event happens in the source system - a new lead, a closed deal - it automatically sends a message containing the event data to a URL the receiving system listens on. The receiver acts on it immediately. It is a push model, so the source notifies rather than waiting to be asked.
What is the difference between a webhook and polling?
Polling has one system repeatedly ask another for changes on a schedule, introducing delay and wasted requests. A webhook has the source push an event the instant it happens. Webhooks are real-time and efficient; polling is periodic and slower. Webhooks are preferred for immediate reactions across systems.
What are webhooks used for?
Real-time integrations: triggering an action in one system the moment an event happens in another - notifying a tool when a lead is created, kicking off a workflow when a deal closes, updating an external system instantly on a change. Webhooks power any integration that needs to react immediately to events.