Triggers API

The Platform Triggers API lets an application subscribe to content events in Glean and receive them at its own endpoint as signed webhooks.

Use Cases

Browse Presets

List the event definitions your deployment serves, and the inputs each one accepts.

Create a Trigger

Instantiate a preset against your webhook URL and receive its signing secret.

Preview Matching Events

See which recent events a preset would have matched, before you create anything.

Manage Triggers

List, update, and delete the triggers you own.

API Endpoints

Method	Endpoint	Purpose
POST	/api/triggers	Create trigger
GET	/api/triggers	List triggers
GET	/api/triggers/{trigger_id}	Get trigger
PATCH	/api/triggers/{trigger_id}	Update trigger
DELETE	/api/triggers/{trigger_id}	Delete trigger
POST	/api/triggers/{trigger_id}/events/search	Search events for a trigger
GET	/api/trigger-presets	List trigger presets
GET	/api/trigger-presets/{preset_id}	Get trigger preset
GET	/api/trigger-presets/{preset_id}/input-values	Search trigger preset input values
POST	/api/trigger-presets/{preset_id}/events/search	Search events for a trigger preset

A trigger is created from a preset — a curated event definition such as "a review is requested from me" or "30 minutes before an event starts" — so you describe what you care about rather than assembling a query.

Built-in datasources have a fixed set of presets. Datasources you index through the Indexing API get presets from their schema. See Custom datasources.

Events are delivered as Standard Webhooks, signed with HMAC-SHA256, and are scoped to what the subscribing user is permitted to see.

These endpoints are experimental — send X-Glean-Include-Experimental: true on each request, or they are not exposed.

For error responses, see Platform API Errors for the shared ProblemDetail code reference and remediation guidance.