Agent skill · software engineering · jeremylongshore
clari-webhooks-events
Detect Clari changes through supported paginated audit reads and asynchronous activity exports instead of assuming webhooks. Use when building an administrative or sales-activity feed. Trigger with: "monitor Clari changes", "stream Clari audit events", "replace Clari webhooks".
Why this skill is useful
Adds executable scripts for monitoring Clari forecast changes and sending alerts via Slack, which are not available in public documentation.
What it needs
Requires curl, python3 installed locally. Requires clari, slack account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clari Audit and Activity Change Feed Overview The published Revenue contract does not define a general webhook subscription surface. Preserve this public route by implementing provider-supported polling: direct paginated audit reads for administrative changes or asynchronous activity exports for emails, meetings, and files. Prerequisites Chosen feed type, organization scope, and authorized fields Monotonic time window or pagination checkpoint with overlap policy Deduplication store and downstream event schema Instructions Step 1: Choose the supported source Use GET /audit/events for paginated audit changes or POST /export/activity plus the export-job lifecycle for activity data. Step 2: Freeze the window Record inclusive and exclusive boundaries, page limit, overlap allowance, timezone, and the first checkpoint before requesting data. Step 3: Read or queue Page audit events in stable order, or queue one activity export and persist its job ID before polling. Step 4: Normalize event identity Derive a deterministic key from provider identifiers, event type, actor, timestamp, and source window; retain the source job or page lineage. Step 5: Deduplicate and advance Publish only validated unseen events, then advance the checkpoint atomically after the downstream sink acknowledges the batch. Step 6: Detect gaps and replay Monitor lag, empty windows, page discontinuity, aborted jobs, and reconciliation counts; replay from the last safe checkpoint within retention. Authentication Use the Revenue apikey header and an identity authorized for the selected audit or activity data. Do not log actor identities, email content, meeting details, filenames, or the token in event-processing telemetry. Tool Discipline Use Read and Grep to inspect configuration, provider contracts, fixtures, logs, schemas, and existing tests before proposing a change. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clari-webhooks-events