Webhook
A webhook is an HTTP callback triggered automatically when a system event occurs, such as a failed payment, closed ticket, or completed deployment. Instead of polling an API on a schedule, the receiving service gets a real-time POST request containing event metadata and identifiers. In support and operations systems, webhooks are used to trigger downstream actions like creating Linear issues, enriching Zendesk tickets, or starting investigation workflows the moment a customer-facing event happens.
Why it matters for B2B support
Webhooks are a core integration primitive in modern SaaS architectures because they push event data across systems with low latency and low overhead. Teams usually pair them with signature verification, retry logic, idempotency keys, and dead-letter handling so duplicate or delayed events do not create bad state in downstream automation.
How Altor helps
Altor can trigger on webhook events and start investigation immediately, turning a 45 min → 2 min diagnostic step into an automated workflow before an agent opens the ticket.
FAQ
How is a webhook different from polling?
Polling asks an API for updates on a fixed interval. A webhook sends the event as soon as it happens.
What breaks webhook integrations most often?
Missing signature validation, poor retry handling, and non-idempotent consumers. Those issues create duplicates or missed events during outages.
Related terms
See Altor investigate a real ticket
We connect to your systems and diagnose a real ticket in 2 minutes during US hours.
Book a Demo