Agent skill · software engineering · jeremylongshore
procore-webhooks-events
Operate Procore hooks, triggers, deliveries, deduplication, and reconciliation as a best-effort notification system. Use when creating webhook subscriptions, upgrading payload formats, or recovering delayed, duplicate, or discarded deliveries. Trigger with: "set up Procore webhooks", "handle duplicate Procore events", "reconcile Procore webhook gaps".
Why this skill is useful
Provides specific API call patterns and error handling for Procore webhooks that the AI wouldn't reliably generate on its own.
What it needs
Requires procore account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Procore Webhook and Reconciliation Boundary Overview Use webhooks for freshness and REST reconciliation for completeness. A delivery tells the receiver that a committed Procore change occurred; it is not the resource itself and may be duplicated, delayed, or discarded after prolonged endpoint failure. Prerequisites Company or project scope, namespace, resource names, and event reasons Public HTTPS receiver that acknowledges quickly and queues work durably Webhooks API permission, OAuth principal, deduplication store, and reconciliation cursor Instructions Step 1: Choose payload format Use the current recommended payload format for new integrations and record the schema contract. Treat string identifier changes and renamed event fields as a versioned migration. Step 2: Create the hook Create one company- or project-scoped hook with an HTTPS destination, required namespace, minimal destination headers, and no secrets in logs. Step 3: Add bounded triggers Subscribe only to documented resources and reasons the application processes. Verify hook and trigger state through the documented API. Step 4: Acknowledge and queue Validate structure, record the event identifier, enqueue a follow-up read, and return a success response within the provider timeout. Process business work asynchronously. Step 5: Deduplicate and hydrate Use event ID or ULID according to the chosen payload. Fetch the current resource from REST and make downstream processing idempotent. Step 6: Reconcile gaps Monitor deliveries and run periodic REST scans from a durable cursor. Explicitly repair the gap after endpoint failure or discarded notifications. Authentication Webhook configuration calls use an OAuth 2.0 Bearer token with Webhooks API permission. Destination authentication uses only minimal reviewed headers; never log those headers or confuse them with Procore OAuth credentials. Tool Discipline Use Read and Grep to inspect handler code, delivery evidence, and endpoint contracts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-webhooks-events--f0a195