Agent skill · software engineering · jeremylongshore
glean-webhooks-events
Implement event-driven Glean indexing triggered by source system webhooks
Why this skill is useful
Provides specific implementation patterns for integrating Glean with various source systems via webhooks that the AI wouldn't reliably generate on its own.
What it needs
Requires express installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Glean Webhooks & Events Overview Glean uses an event-driven indexing model where source system webhooks trigger incremental updates to the Glean Indexing API. Instead of emitting its own webhooks, Glean receives document changes from platforms like GitHub, Confluence, and Notion. You can also monitor internal Glean events such as document indexing completion, permission changes, connector sync status, and search anomalies through the admin API. Webhook Registration Signature Verification Event Handler Event Types Event Payload Fields Use Case ------- --------------- ---------- document.indexed datasource, docid, indextimems Confirm content is searchable permission.changed datasource, objectid, newacl Re-sync access controls connector.synced connectorname, docsprocessed, errors Monitor connector health search.anomaly querypattern, anomalytype, severity Detect unusual search behavior document.deleted datasource, docid, deletedby Audit content removal Retry & Idempotency Error Handling Issue Cause Fix ------- ------- ----- Index rejected Document exceeds size limit Chunk large documents before indexing Permission denied Stale OAuth token for connector Refresh connector credentials in admin Duplicate documents Source sends create + update rapidly Deduplicate by docid before indexing Connector timeout Source API rate limited Implement exponential backoff in connector Prerequisites A secret-manager webhook secret, an approved event origin allowlist, a replay-window policy, and an opaque event ledger. A sandbox receiver with fictional events and a tested disable/rollback control for the consumer. Data-owner approval for every event type that can alter an index, permission mapping, or retention state. Instructions 1. Authenticate the source before parsing, validate timestamp and event ID, and reject unknown origins, stale deliveries, and malformed payloads. 2. Store only a bounded, redacted event envelope and use event ID plus target revision as the idempotency key. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/glean-webhooks-events