Webhook
A Webhook is an HTTP callback — one system sends an HTTP POST to a URL hosted by another system the moment a specific event happens — enabling real-time integration without polling.
What is Webhook?
Webhooks are the lightweight alternative to API polling. Instead of System A asking System B every minute 'did anything happen?', System B sends an HTTP POST to System A whenever something does happen. The pattern is ubiquitous in modern SaaS — every major GTM tool supports outbound webhooks for key events. On the receiving end, you handle the webhook by writing an endpoint that processes the payload. Webhooks are faster (sub-second instead of minutes of delay), more efficient (no wasted requests), and simpler to debug (every event has a single moment of truth).
Why it matters
- Real-time integration without polling overhead.
- Payloads are typically richer than what poll-style APIs return.
- Make event-driven architecture practical for non-event-native products.
Use cases
- Form-to-CRM. Form submission webhook into CRM creates the lead instantly.
- Calendar-to-CRM. Calendar booking webhook updates opportunity stage and notifies team.
- Workflow chaining. One tool's webhook becomes another tool's workflow trigger.
How turgo helps
turgo emits webhooks for every major event (agent action, signal, deal change) and consumes webhooks from any tool that emits them — making it the event hub for the GTM stack.
See turgo in action →
