platform-events

Define and manage Salesforce Platform Events for event-driven architecture.

2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/bhanu91221/claude-sfdx-iq --skill platform-events
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-events
Source: https://github.com/bhanu91221/claude-sfdx-iq/tree/main/skills/platform-events
Command: npx skills add https://github.com/bhanu91221/claude-sfdx-iq --skill platform-events

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform events provide a scalable way to decouple Salesforce applications by defining custom event objects with __e suffix and enabling event-driven communication across Apex, Flows, REST, and external subscribers.

Core Features & Use Cases

  • Event Definition & Metadata: Define reliable event schemas with fields and publish behavior.
  • Publish & Subscribe: Publish events from Apex, Flow, REST, and subscribe via Trigger, Flow, or external subscribers using CometD or Pub/Sub APIs.
  • Replay & Reliability: Use replay IDs to resume processing and implement idempotent processing patterns.
  • Error Handling: Patterns for dead-lettering and graceful failure without blocking transactions.
  • Use Case: Build an order processing workflow that publishes an Order_Placed__e event and reacts to it asynchronously.

Quick Start

Instantiate the first Order_Placed__e event in your Salesforce org using the provided Apex snippet.

Frequently Asked Questions about platform-events

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish and consume Salesforce Platform Events in Apex?

To publish Salesforce Platform Events in Apex, instantiate the custom event object with the __e suffix and use EventBus.publish. Consume events by writing an Apex trigger on the platform event object or subscribing via external CometD and Pub/Sub APIs.

What is event-driven architecture in Salesforce and when do I need it?

Event-driven architecture in Salesforce decouples applications by communicating through custom event objects. You need it when building scalable workflows that require asynchronous processing, such as publishing an Order_Placed__e event to notify multiple independent subscribers.

How do I use replay IDs to resume Salesforce Platform Event processing?

Replay IDs track processed Salesforce Platform Events so subscribers can resume processing from a specific point after a failure. Implement idempotent processing patterns alongside replay IDs to ensure messages are not duplicated upon re-delivery.

Can I subscribe to Salesforce Platform Events using Flow or REST?

Yes, you can subscribe to Salesforce Platform Events using Flow or external REST subscribers. Publish events directly from Flow or REST, and react to them asynchronously by configuring Flow triggers or connecting external CometD and Pub/Sub API clients.

What are the limitations and error handling strategies for high-volume Platform Events?

High-volume Salesforce Platform Events require careful error handling to avoid blocking transactions. Use dead-lettering patterns for graceful failure management and enforce best practices for event metadata and publish behavior to handle scale efficiently.