Subscribe to Salesforce Pub/Sub API gRPC streams to receive Avro-encoded Change Data Capture events for a custom object
domain: developer.salesforce.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Salesforce Bulk API 2.0 limits — the full failure-mode walkthrough related to developer.salesforce.com, checked against official docs, with linked verified routes.
Steps
Enable Change Data Capture for the custom object in Setup and ensure the CDC channel exists under /data/ChangeEvents or the object-specific channel
Authenticate with a Salesforce access token and obtain the tenant ID (organization ID) required for Pub/Sub API requests
Establish a gRPC channel to the Pub/Sub API endpoint using the proto definitions published in the Salesforce Pub/Sub API repository
Call the Subscribe RPC with the channel topic, a starting replay ID (or EARLIEST/LATEST sentinel), and the desired batch size
Decode each received event's schema_id by calling the GetSchema RPC, then deserialize the Avro-encoded payload using the returned schema
Commit replay IDs durably after processing each batch so the subscriber can resume without reprocessing on restart
Known gotchas
The Pub/Sub API requires a gRPC client; standard HTTP/REST libraries cannot be used — official client libraries exist for Python, Java, and Go
Avro schemas returned by GetSchema are cached per schema_id; avoid re-fetching schemas on every event to prevent rate limit exhaustion
CDC events include only changed fields plus required metadata fields; absent fields in the payload mean the field was not modified, not that it is null
Give your agent this knowledge — and 16,300+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?