Agent skill · forcedotcom
integration-eventing-cdc-configure
Use to enable Salesforce Change Data Capture (CDC) on a standard or custom object, configure a custom event channel, set a filter expression, or add enrichment fields. TRIGGER broadly on any of: 'enable CDC', 'enable Change Data Capture', 'turn on CDC', 'subscribe X to change events', 'only emit events for', 'filter change events', 'enrich change events', 'create a custom event channel'; or any mention of CDC, change events, PlatformEventChannel, PlatformEventChannelMember, EnrichedField, ChangeEvents channel, enrichment fields, change event filter; or when the user wants a downstream system to receive Salesforce data changes; or when the user touches .platformEventChannelMember-meta.xml / .platformEventChannel-meta.xml files. SKIP when publishing platform events, Pub/Sub API or REST/SOAP (use integration-connectivity-generate), or ManagedEventSubscription (out of scope for CDC). Always use this skill for CDC channel-membership metadata.
What it needs
About 8k tokens when loaded.
What this skill does
Managing Change Data Capture Enablement Generate the metadata that subscribes Salesforce objects to Change Data Capture: PlatformEventChannelMember files for the default ChangeEvents channel or a custom channel, and PlatformEventChannel files for new custom channels. Covers enrichment fields, filter expressions, and the canonical naming and value formats that the Metadata API actually accepts (which differ from values that appear in many internal test fixtures and code-search hits). Scope In scope: Generating PlatformEventChannelMember and PlatformEventChannel metadata for CDC. Subscribing standard objects, custom objects, or both. Configuring enrichment fields. Configuring filter expressions. Defining custom data channels. Out of scope: Publishing custom platform events (PE) — that's a different metadata type (PlatformEvent). Pub/Sub API or external Kafka/Bayeux configuration. Pricing/limits guidance — refer the user to the CDC Developer Guide. Programmatic event-bus subscribers in Apex. --- Clarifying Questions Before generating, confirm with the user if not already clear: Which entity (or entities) need CDC enablement? Standard, custom, or both? Default channel (ChangeEvents) or a custom channel? If custom, what's the channel label? Any enrichment fields needed? (Lookup IDs that the consumer needs even when they didn't change.) Any filter expression needed? (A SOQL-WHERE-clause body that gates which change events emit.) --- Required Inputs Gather or infer before proceeding: Source entity API name(s) — e.g. Account, Lead, Orderc. The skill internally translates this to the ChangeEvent entity name (see Workflow step 2). Channel — either ChangeEvents (default) or the developer name of a custom channel ending in chn. Enrichment fields (optional) — list of field API names on the source object whose values should be included in every change event. Filter expression (optional) — a predicate over fields on the change event payload (e.g. Statusc != null). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/integration-eventing-cdc-configure--f2cb40