Salesforce Platform Event Sink Connector for Confluent Cloud

Salesforce platform events are user-defined publish-subscribe events. The full-managed Salesforce Platform Event Sink connector publishes platform events from Apache Kafka® topics to Salesforce.

The Salesforce Platform Event Sink connector can be thought of as the inverse of the Platform Events Source connector. It is designed to read platform event records from a Kafka topic containing data streamed from the platform event source connector. The connector then publishes this data as new platform events to the configured organization.

Important

If you are still on Confluent Cloud Enterprise, please contact your Confluent Account Executive for more information about using this connector.

Features

The Salesforce Platform Event Sink connector supports the following features:

  • At least once delivery: This connector guarantees that records from the Kafka topic are delivered at least once.

  • Supports multiple tasks: The connector supports running one or more tasks. More tasks may improve performance (that is, consumer lag is reduced with multiple tasks running).

  • Automatically creates topics: The following three topics are automatically created when the connector starts:

    The suffix for each topic name is the connector’s logical ID. In the example below, there are the three connector topics and one pre-existing Kafka topic named pageviews.

    Salesforce Platform Event Sink Connector Topics

    Connector Topics

    If the records sent to the topic are not in the correct format, or if important fields are missing in the record, the errors are recorded in the error topic, and the connector continues to run.

  • Supported data formats: The connector supports Avro, JSON Schema (JSON-SR), and Protobuf input message formats. Schema Registry must be enabled to use these Schema Registry-based formats.

See Configuration Properties for configuration property values and definitions. See Cloud connector limitations for additional information.

Data Fields

The UI configuration property Salesforce platform event name (CLI property salesforce.platform.event.name) designates the name of the event. Event names must end with __e. For example, MyPlatformEvent__e.

The connector only publishes data fields that are part of the Platform Event Definition (that is, data fields ending with __e). All other fields are ignored. If there are no fields in the message that have the required __e suffix, the entire message is not sent to Salesforce.

Note

The Platform Event Definition must exist in Salesforce before the connector can publish events to Salesforce. See the Salesforce Developer Guide for more information.

Quick Start

Use this quick start to get up and running with the Confluent Cloud Salesforce Platform Event Sink connector. The quick start provides the basics of selecting the connector and configuring it to stream events

Prerequisites
  • Authorized access to a Confluent Cloud cluster on Amazon Web Services (AWS), Microsoft Azure (Azure), or Google Cloud Platform (GCP).
  • An authorized Salesforce user and credentials for the connector.
  • An authorized Salesforce consumer key and secret for the connector.
  • The Confluent Cloud CLI installed and configured for the cluster. See Install and Configure the Confluent Cloud CLI.
  • Schema Registry must be enabled to use a Schema Registry-based format (for example, Avro, JSON_SR (JSON Schema), or Protobuf).
  • At least one source Kafka topic must exist in your Confluent Cloud cluster before creating the sink connector.

Using the Confluent Cloud Console

Step 1: Launch your Confluent Cloud cluster.

See the Quick Start for Apache Kafka using Confluent Cloud for installation instructions.

Step 2: Add a connector.

Click Connectors. If you already have connectors in your cluster, click Add connector.

Step 3: Select your connector.

Click the Salesforce Platform Event Sink connector icon.

Salesforce Platform Event Sink Connector Icon

Step 4: Set up the connection.

Note

  • Make sure you have all your prerequisites completed.
  • An asterisk ( * ) designates a required entry.
  1. Select one or more topics.
  2. Enter a connector Name.
  3. Select an Input message format (data coming from the Kafka topic): AVRO, JSON_SR (JSON Schema), or PROTOBUF. A valid schema must be available in Schema Registry to use a schema-based message format (for example, Avro, JSON_SR (JSON Schema), or Protobuf).
  4. Enter your Kafka Cluster credentials. The credentials are either the cluster API key and secret or the service account API key and secret.
  5. Enter the Salesforce connection details. For more information about Salesforce authentication details and what they mean, see Connected App and OAuth Terminology.
  6. Enter the Connection timeout. The amount of time to wait in milliseconds (ms) when connecting to the Salesforce endpoint. The default is 30000 ms (30 seconds).
  7. Enter the number of tasks to use with the connector. More tasks may improve performance.

See Configuration Properties for configuration property values and descriptions.

Step 5: Launch the connector.

Verify the connection details and click Launch.

Step 6: Check the connector status.

The status for the connector should go from Provisioning to Running.

Step 7: Check for records.

Verify that records are being produced at the endpoint.

For more information and examples to use with the Confluent Cloud API for Connect, see the Confluent Cloud API for Connect section.

Tip

When you launch a connector, a Dead Letter Queue topic is automatically created. See Dead Letter Queue for details.

Using the Confluent Cloud CLI

Complete the following steps to set up and run the connector using the Confluent Cloud CLI.

Note

Make sure you have all your prerequisites completed.

Step 1: List the available connectors.

Enter the following command to list available connectors:

ccloud connector-catalog list

Step 2: Show the required connector configuration properties.

Enter the following command to show the required connector properties:

ccloud connector-catalog describe <connector-catalog-name>

For example:

ccloud connector-catalog describe SalesforcePlatformEventSink

Example output:

Following are the required configs:
connector.class: SalesforcePlatformEventSink
input.data.format
name
kafka.api.key
kafka.api.secret
salesforce.username
salesforce.password
salesforce.password.token
salesforce.consumer.key
salesforce.consumer.secret
salesforce.platform.event.name
tasks.max
topics

Step 3: Create the connector configuration file.

Create a JSON file that contains the connector configuration properties. The following example shows the required connector properties.

{
  "connector.class": "SalesforcePlatformEventSink",
  "input.data.format": "AVRO",
  "name": "SalesforcePlatformEventSinkConnector_0",
  "kafka.api.key": "****************",
  "kafka.api.secret": "************************************************",
  "salesforce.username": "<username>",
  "salesforce.password": "<password>",
  "salesforce.password.token": "<password-token>",
  "salesforce.consumer.key": "<consumer-key>",
  "salesforce.consumer.secret": "<consumer-secret>",
  "salesforce.platform.event.name": "<event-name>__e",
  "tasks.max": "1",
  "topics": "orders",
}

Note the following property definitions:

  • "connector.class": Identifies the connector plugin name.
  • "input.data.format": Sets the input message format (data coming from the Kafka topic). Valid entries are AVRO, JSON_SR, and PROTOBUF. You must have Confluent Cloud Schema Registry configured if using a schema-based message format (for example, Avro, JSON_SR (JSON Schema), or Protobuf).
  • "name": Sets a name for your new connector.
  • "kafka.api.key" and ""kafka.api.secret": These credentials are either the cluster API key and secret or the service account API key and secret.
  • salesforce.<...> Required Salesforce connection details. For more information about Salesforce authentication details and what they mean, see Connected App and OAuth Terminology
  • "tasks.max": This connector supports one task only.
  • "topics": Enter the topic name or a comma-separated list of topic names.

Step 4: Load the properties file and create the connector.

Enter the following command to load the configuration and start the connector:

ccloud connector create --config <file-name>.json

For example:

ccloud connector create --config salesforce-platform-event-sink-config.json

Example output:

Created connector SalesforcePlatformEventSinkConnector_0 lcc-do6vzd

Step 5: Check the connector status.

Enter the following command to check the connector status:

ccloud connector list

Example output:

ID           |             Name                       | Status  | Type | Trace
+------------+----------------------------------------+---------+------+-------+
lcc-do6vzd   | SalesforcePlatformEventSinkConnector_0 | RUNNING | sink |       |

Step 6: Check for records.

Verify that records are populating the endpoint.

For more information and examples to use with the Confluent Cloud API for Connect, see the Confluent Cloud API for Connect section.

Tip

When you launch a connector, a Dead Letter Queue topic is automatically created. See Dead Letter Queue for details.

Configuration Properties

The following connector configuration properties can be used with the Salesforce Platform Event Sink connector for Confluent Cloud.

salesforce.instance

The URL of the Salesforce endpoint to use. This directs the connector to use the endpoint specified in the authentication response. The default is blank and uses https://login.salesforce.com.

salesforce.username

The Salesforce username the connector should use.

  • Type: string
  • Importance: high
salesforce.password

The Salesforce password the connector should use.

  • Type: password
  • Importance: high
salesforce.password.token

The Salesforce security token associated with the username.

  • Type: password
  • Default: null
  • Importance: high
salesforce.consumer.key

The consumer key for the OAuth application.

  • Type: string
  • Importance: high
salesforce.consumer.secret

The consumer secret for the OAuth application.

  • Type: password
  • Importance: high
salesforce.platform.event.name

The Salesforce platform event name to subscribe to. The Event name should end with the __e suffix. For example: LoginEvent__e.

  • Type: string
  • Valid Values: Matches regex ( .*__e$ )
  • Importance: high
connection.timeout

The amount of time to wait in milliseconds (ms) while connecting to the Salesforce endpoint. The default is 30000 ms (30 seconds).

  • Type: long
  • Default: 30000
  • Valid Values: [5000,…,600000]
  • Importance: low

Next Steps

See also

For an example that shows fully-managed Confluent Cloud connectors in action with Confluent Cloud ksqlDB, see the Cloud ETL Demo. This example also shows how to use Confluent Cloud CLI to manage your resources in Confluent Cloud.

../_images/topology.png