Webhooks

Webhooks let external systems send events into The AI Platform. A webhook is an endpoint you create in a workspace: it has its own URL, a signing secret, and a target that decides what happens when an event arrives.

What a webhook can do

Each endpoint has one target:

  • Channel post — the event is delivered into a chat channel as a message authored by the webhook. Point CI/CD, error trackers, or product-analytics integrations at a channel and the team sees each event inline. Payloads with a blocks array render as rich messages; anything else renders as a formatted payload preview.
  • Workflow trigger — the event starts a workflow, passing the request payload as its input.

The target also decides how requests are authenticated: channel posts use one generic shared-secret scheme, while workflow triggers verify a provider's event signature.

How delivery works

  1. An external system sends an HTTP POST to the endpoint URL with a signature header.
  2. The platform verifies the signature against the endpoint's secret using the endpoint's configured verifier scheme. Unverified requests are rejected before any target runs.
  3. The raw request body is archived, and the target runs — a channel message is posted, or a workflow is triggered.

Verification is always on: an endpoint cannot receive events without a valid signature, so a leaked URL alone is not enough to post into your workspace.

Get started

  • Setup — create an endpoint, choose its target and verifier, and send your first signed request.
  • Channel posts — deliver events into a channel as messages.
  • Workflow triggers — start a workflow from an event.
  • Configuration — verifier schemes, response modes, secret rotation, and delivery limits.
  • Rich messages — render events as rich messages using a blocks payload.