Agent skill · marketing growth · jeremylongshore
salesforce-webhooks-events
Select and govern Salesforce change delivery across Pub/Sub API, Change Data Capture, Platform Events, event relay, Streaming API, Outbound Messages, or polling. Use when building event-driven integrations. Trigger with "design Salesforce events".
Why this skill is useful
Provides specific implementation patterns and code examples for integrating Salesforce events that the AI wouldn't reliably generate on its own.
What it needs
Requires express, jsforce installed locally. Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce Event and Change-Delivery Decision Overview Choose the supported delivery contract from business semantics, entitlement, transport, ordering, replay, schema, security, and recovery evidence. Prerequisites Business event or record-change definition, producer, consumers, latency, ordering, volume, and recovery objective Current org edition, event entitlements, permissions, channels, schema, delivery allocation, and support contract Consumer idempotency, checkpoint or replay state, dead-letter path, reconciliation, and backfill owner Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract Pub/Sub API uses gRPC over HTTP/2 and Avro for platform events, Change Data Capture, and real-time event monitoring. CDC publishes near-real-time record changes and can emit gap or overflow events; other Salesforce delivery mechanisms have different contracts. Authentication Use the documented OAuth and permission model for the selected producer and consumer. Protect tokens, event payloads, replay or checkpoint state, schemas, org identifiers, and personal data. Instructions 1. Define business semantics, source of truth, producer authority, consumers, payload minimum, ordering key, latency, and loss tolerance. 2. Discover the org edition, enabled event products, Pub/Sub or alternative availability, channels, permissions, schemas, and allocations. 3. Compare Pub/Sub API, CDC, custom Platform Events, event relay, Streaming API, Outbound Messages, and bounded polling against requirements. 4. Design idempotency, schema compatibility, checkpoint or replay handling, flow control, reconnect, dead letter, and poison-event isolation. 5. Model duplicate, delayed, out-of-order, gap, overflow, schema-change, permission-loss, quota, and consumer-outage cases. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-webhooks-events