Salesforce composite upsert Sink
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
Upsert Composite List of sObjects in Salesforce.
Configuration Options
The following table summarizes the configuration options available for the salesforce-composite-upsert-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
Consumer Key | Required The Salesforce application consumer key. | string | |||
Consumer Secret | Required The Salesforce application consumer secret. | string | |||
Password | Required The Salesforce user password. | string | |||
Object Id Name | Required The Field Name of the External ID of the Salesforce object. Required if using a key-value pair. | string | |||
Object Name | Required The type of the Salesforce object. Required if using a key-value pair. | string | Contact | ||
Username | Required The Salesforce username. | string | |||
Login URL | The Salesforce instance login URL. | string |
Dependencies
At runtime, the salesforce-composite-upsert-sink
Kamelet relies upon the presence of the following dependencies:
-
camel:core
-
camel:jsonpath
-
camel:jackson
-
camel:salesforce
-
camel:kamelet
Camel JBang usage
Prerequisites
-
You’ve installed JBang.
-
You have executed the following command:
jbang app install camel@apache/camel
Supposing you have a file named route.yaml with this content:
- route:
from:
uri: "kamelet:timer-source"
parameters:
period: 10000
message: 'test'
steps:
- to:
uri: "kamelet:salesforce-composite-upsert-sink"
You can now run it directly through the following command
camel run route.yaml
Salesforce Composite Upsert Sink Kamelet Description
Salesforce CRM Integration
This Kamelet integrates with Salesforce CRM using composite upsert operations. Composite operations allow multiple records to be processed in a single API call, improving efficiency and reducing API usage.
Upsert Operations
Performs upsert (insert or update) operations that create new records if they don’t exist or update existing records based on external ID fields. This provides flexible data synchronization capabilities.
Batch Processing
Composite operations enable batch processing of multiple records in a single request, reducing API call overhead and improving performance for bulk data operations.
External ID Matching
Uses external ID fields for record matching, allowing integration with external systems while maintaining data relationships and avoiding duplicate records.