Salesforce PubSub API Source Connector — 1.0.0 (archived)
|
This is archived documentation for version 1.0.0. |
Type |
Source |
Class |
|
Target System |
Messaging & Streaming (Salesforce Pub/Sub API) |
Maintainer |
Axual |
License |
Proprietary (client-only) |
Project |
Proprietary. Source code is not publicly accessible. |
Download |
Contact Axual Support to obtain the connector library. |
|
This page documents version 1.0.0. Newer versions should be compatible unless there are breaking changes, but field names or default values may differ. If you notice discrepancies, please contact Axual Support. |
Description
The Salesforce PubSub API Source Connector streams events from Salesforce to Kafka topics in real time. It uses the modern gRPC-based Salesforce Pub/Sub API, providing efficient, high-performance ingestion of Change Data Capture (CDC) events, Platform Events, and Real-Time Event Monitoring data. It is a robust alternative to older Streaming API (CometD) based connectors, offering better scalability and a unified eventing interface.
Features
-
Stream real-time events from Salesforce to Kafka
-
Supports multiple Salesforce event types:
-
Change Data Capture (CDC)
-
Platform Events
-
Real-Time Event Monitoring
-
-
Built on Salesforce Pub/Sub API (gRPC) for high throughput and low latency
-
Converts Salesforce Avro schemas to Kafka Connect schemas, enabling structured converters
-
Supports at-least-once delivery semantics
-
Secure authentication using OAuth 2.0 Client Credentials with Connected App client ID and client secret
-
One task per Salesforce topic —
tasks.maxmust be ≥ the number of topics insalesforce.topics
Configuration
Configuration options are grouped as follows:
-
Authentication — Salesforce OAuth 2.0 credentials and Pub/Sub API endpoint
-
Topic Routing and Replay — Salesforce topics to subscribe to, Kafka topic naming, and replay position
-
Performance Tuning — Internal buffers, batch sizes, and polling timeouts
-
Connection Reliability (gRPC) — gRPC keep-alive settings
-
Advanced Configuration — Schema caching and connection validation
Authentication
Required settings to authenticate against Salesforce and connect to the Pub/Sub API using OAuth 2.0 Client Credentials.
| Key | Type | Mandatory | Default | Description |
|---|---|---|---|---|
|
String |
Yes |
— |
Salesforce OAuth Client ID (Connected App Consumer Key). |
|
Password |
Yes |
— |
Salesforce OAuth Client Secret (Connected App Consumer Secret). |
|
String |
Yes |
— |
Salesforce Instance URL, e.g. |
|
String |
Yes |
— |
Salesforce Organisation ID (Tenant ID). Typically starts with |
|
String |
No |
api.pubsub.salesforce.com:7443 |
Salesforce Pub/Sub API gRPC endpoint in |
Topic Routing and Replay
| Key | Type | Mandatory | Default | Description |
|---|---|---|---|---|
|
List |
Yes |
— |
Comma-separated list of Salesforce topics to subscribe to.
Example: |
|
String |
Yes |
— |
Prefix for destination Kafka topic names.
Salesforce topic path slashes are replaced with dots and this prefix is prepended.
Example: prefix |
|
String |
No |
EARLIEST |
Starting position for new subscriptions (when no stored offset exists).
|
Performance Tuning
| Key | Type | Mandatory | Default | Description |
|---|---|---|---|---|
|
Integer |
No |
100 |
Maximum records returned per |
|
Integer |
No |
1000 |
Maximum events buffered in memory before pausing the gRPC consumer. |
|
Long |
No |
1000 |
Maximum time in milliseconds to wait for events during a |
Connection Reliability (gRPC)
| Key | Type | Mandatory | Default | Description |
|---|---|---|---|---|
|
Integer |
No |
30 |
Interval in seconds between keep-alive pings sent to the server. |
|
Integer |
No |
10 |
Time in seconds to wait for a keep-alive ping response before treating the connection as dead. |
|
Integer |
No |
5 |
Time in seconds to wait for graceful channel shutdown before forcing termination. |
Known limitations
-
One connector task is assigned per Salesforce topic —
tasks.maxmust be ≥ the number of topics insalesforce.topics. -
Only OAuth 2.0 Client Credentials is supported in this version. JWT Bearer authentication was added in 1.1.0.
-
The Salesforce Pub/Sub API must be enabled in your Salesforce organisation.
-
Event replay is subject to Salesforce retention windows — typically 3 days for Platform Events and CDC events.
-
Real-Time Event Monitoring requires a separate Salesforce license and must be enabled in your org.