Helpdesk Concepts

Webhook

定義

A webhook is an automated HTTP callback that sends real-time data from one system to another when a specific event happens — for example, a help desk posting ticket details to an external URL the moment a ticket is created or updated.

別名: HTTP callbackreverse APIevent notification

How it works

Unlike a normal API call where your app repeatedly asks "is there anything new?", a webhook flips the direction: you register a URL, and the source system pushes a payload (usually JSON) to that URL as soon as an event occurs. The receiving endpoint parses the payload and acts on it.

In a help desk, common triggers include ticket created, status changed, or comment added. The webhook fires an event to a CRM, Slack channel, billing system, or automation platform so downstream tools stay in sync without polling.

Why it matters

Webhooks are the backbone of real-time integrations in support. They let a help desk react instantly to events instead of on a schedule, keeping connected systems current and enabling automations to run the moment something changes.

For AI-driven support, webhooks are often how an AI layer gets notified that a new ticket needs handling — the event fires, the agent picks it up, reads the context, and acts.

よくある質問

What is the difference between a webhook and an API?

An API is pulled — your app requests data when it wants it. A webhook is pushed — the source system sends data to you automatically when an event happens, in real time, without you asking.

Are webhooks secure?

They can be. Most providers sign payloads with a secret so the receiver can verify the request really came from the source, and endpoints should be served over HTTPS.

Route and act with triggers

Webhook

How it works

Why it matters

よくある質問

関連用語