Salesforce currently has 150,000 customers across the world who use Salesforce in some capacity. If you are one of those customers, you've likely had to work through how to integrate it with your other back office systems: ERP, Marketing Automation, BI systems, etc. Or perhaps you're a brand new Salesforce customer and are just now trying to understand what options exist for integration. It is undeniable that the rate of integrating with Salesforce is increasing, and extracting the valuable data that is in Salesforce is not always an easy feat when you have to consider how to do this best in your own unique environment. In this webinar, Big Compass and Confluent will talk about the various techniques for getting data out of Salesforce, and how Confluent and Kafka can play an integral role in not only brokering these messages at an incredibly fast and scalable rate, but to also make it very easy to exchange data with Salesforce. YOU WILL LEARN: What integration capabilities exist within Salesforce How Confluent can be used to integrate with Salesforce Techniques in Confluent for pub/sub, streaming, and building business logic using KSQL and Kafka Streams Patterns of Salesforce integration in general and specifically with Confluent Strengths and weaknesses of each pattern and scenarios where they work best WHO SHOULD ATTEND: IT leaders who are looking for the most efficient methods for integration with Salesforce Developers/System Integrators who are interested in seeing Salesforce integration techniques Anyone in the Salesforce ecosystem who is interested in integration REASONS TO ATTEND: Learn about methods of Salesforce integration and explore Confluent’s built-in capabilities if you're considering an off-the-shelf solution

1. Unlocking the Power of
Salesforce Integrations
with Confluent
Presented By:
Big Compass and Confluent
November 2020

2. 1. Integration Pain Points With Salesforce
2. Ways to Integrate with Salesforce
3. Solving the Challenge of Unlocking Salesforce Data
4. Salesforce + Confluent
5. Use Cases: Extracting Data out of Salesforce with
Confluent
Agenda

3. ● Consulting - specializing in
integrations and related technologies
● Confluent partners
● We build connections between
systems, applications, people, and
ideas
Big Compass

4. Salesforce Integrations

5. ● Subscription tier limits
● API/Event limits
● Countless customizations
● Custom code/triggers to push data
out of Salesforce
● Unexpected API Security
Integration Pain
Points With Salesforce

6. ● How: Create triggers (PushTopics,
Platform Events, CDC) in Salesforce to
send events to a target
● When to Use: Great for real-time or
event-driven use cases
● Skills: Deeper Salesforce knowledge
required to create events
● Complexity: Higher - Create trigger in
Salesforce and subscribe to the event
using a tool like Confluent
Pushing vs. Pulling Salesforce Data
Considerations when choosing whether to send events out of Salesforce or use Salesforce APIs to pull data out of Salesforce
Pushing Data
● How: Use Salesforce APIs to query
data on-demand
● When to Use: Great for batch or on-
demand use cases
● Skills: Some Salesforce knowledge is
useful but not required
● Complexity: Lower - Least number of
moving parts to the solution -
Salesforce API, consumer/connector,
target system
Pulling Data

7. Ways to Integrate with Salesforce
Integration Method Description Good For Not Suitable For
Batch Single event/request
for many objects in
Salesforce
Easiest way to
implement a solution
for non-real-time
solutions
Constantly changing
data
Real-Time Create individual
events for each
change that occur in
Salesforce
Real-time use cases
and handling events
individually
Less frequently
changing data
AppExchange Install out of the box
apps in Salesforce to
integrate with other
systems
Use cases that
integrate with
common systems
Apps that are not built
yet or use cases that
go beyond the scope
of connectors
Custom Salesforce UI Expose your
Salesforce data via
custom UI built in
Salesforce
Organizations who
are all-in on
Salesforce
Organizations who
need the Salesforce
data in another
system

8. ● Necessary to power downstream
systems/applications
● Do you push data out of Salesforce,
pull data out of Salesforce, or both?
● Pre-built connectors like Confluent’s
Salesforce Connector can help speed
up integration
● Not a trivial task without pre-built
connectors!
○ Need to author custom code
Unlocking Salesforce
Data - Not a Trivial
Task!

9. Real-Time Salesforce
Events

10. Eventing Out of Salesforce
Event Type Description Advantages Disadvantages
Platform Events Custom pub/sub events 1. Highly customizable
2. Scalable
1. Requires Salesforce
knowledge
PushTopics PushTopic events track
field changes in Salesforce
records
1. Out of the box
PushTopics can
kickstart your
implementation
1. Lower ability to
customize the event
Change Data Capture Notification on changes on
an object
1. Easy to implement 1. Lower ability to
customize the event
Outbound Event Send SOAP message to
web service
1. Can be used to
event to a RESTful
or SOAP endpoint
1. Lower ability to
customize the event
2. Uses SOAP

11. Unlocking Salesforce Data
Publisher (Platform Event) Subscriber/Processing Target Systems
Consumer Applications

12. Use Case: Synchronizing SFDC Data
Publisher (Platform Event)
Subscriber/Processing
Real-Time Target
Data Storage Target
Consumer Applications

13. ● Pre-built source and sink connector to
speed up integrations
● Once data is in Confluent, easy to use
pub/sub model to process and route
the data
● Joining from multiple sources
● Streaming data
● Duplicate detection
● Execute business logic
● Run SQL queries
● Detect events
● Much more than standard pub/sub
Salesforce
Integrations with
Confluent

14. ● Need to enrich and transform data
from multiple sources before it is sent
to a target system
● Clean your data
● Enrich your data
● Stage your data
Use Case: Data Prep

15. ● Gain valuable insight about your
customers from multiple data sources
● Enrich data from various sources
● Generate actionable insight about
your customers
● Predict customer actions in real-time
Use Case: 360
Customer View

16. ● Synchronize data with a target system
to power a mobile application
● Two-way synchronization with source
and sink connectors
● Duplicate detection
● Business logic
● Real-time streaming
Use Case:
Synchronizing SFDC
Data

17. Use Cases In Action: SFDC Sync From Multiple
Sources

20. http PUT cp01.woolford.io:8083/connectors/sfdc-contact-updates/config <<< '
{
"confluent.topic.bootstrap.servers": "cp01.woolford.io:9092,cp02...",
"confluent.topic.replication.factor": "1",
"connector.class": "io.confluent.salesforce.SalesforcePushTopicSourceConnector",
"kafka.topic": "sfdc-contact-updates",
"name": "sfdc-contact-updates",
"salesforce.consumer.key": "********",
"salesforce.consumer.secret": "********",
"salesforce.initial.start": "all",
"salesforce.object": "Contact",
"salesforce.password": "cxI3o3R$****",
"salesforce.password.token": "iggX9UEPizeaizvpg02Vj****",
"salesforce.push.topic.name": "ContactUpdates",
"salesforce.username": "alex@woolford.io",
"tasks.max": "1"
}'
PushTopic pushTopic = new PushTopic();
pushTopic.Name = 'ContactUpdates';
pushTopic.Query = 'SELECT Id, [...] FROM Contact';
pushTopic.ApiVersion = 50.0;
pushTopic.NotifyForOperationCreate = true;
pushTopic.NotifyForOperationUpdate = true;
pushTopic.NotifyForOperationUndelete = true;
pushTopic.NotifyForOperationDelete = true;
pushTopic.NotifyForFields = 'All';
insert pushTopic;

26. mysql> use healthcare;
Database changed
mysql> select * from patient;
+----+-----------+------------+--------------+------------+
| id | firstname | lastname | enroll_start | enroll_end |
+----+-----------+------------+--------------+------------+
| 1 | Donald | Trump | 2019-04-14 | 2020-04-13 |
| 2 | Vladimir | Putin | 2019-05-20 | 2020-05-19 |
| 3 | Boris | Johnson | 2019-01-24 | 2020-01-24 |
| 4 | Mark | Zuckerberg | 2019-03-03 | 2020-03-02 |
| 5 | Benjamin | Netanyahu | 2019-08-24 | 2020-08-23 |
| 6 | Jair | Bolsonaro | 2019-09-19 | 2020-09-18 |
| 7 | Farty | McFartface | 2019-08-23 | 2020-08-22 |
+----+-----------+------------+--------------+------------+
7 rows in set (0.00 sec)

27. http PUT http://cp01.woolford.io:8083/connectors/mysql-cdc-healthcare/config <<< '
{
"name": "mysql-cdc-healthcare",
"connector.class": "io.debezium.connector.mysql.MySqlConnector",
...
"include.schema.changes": "false",
"snapshot.mode": "when_needed",
"table.whitelist": "healthcare.patient",
"transforms": "unwrap,HoistField",
"transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",
"transforms.HoistField.type": "org.apache.kafka.connect.transforms.ExtractField$Key",
"transforms.HoistField.field": "id"
}'

29. CREATE STREAM AILMENT (
id STRING,
ailment VARCHAR
) WITH (
kafka_topic='ailment',
value_format='JSON',
KEY='id'
);
CREATE TABLE PATIENT (
id STRING,
firstname VARCHAR,
lastname VARCHAR,
enroll_start BIGINT,
enroll_end BIGINT
) WITH (
kafka_topic='deepthought.healthcare.patient',
value_format='JSON',
KEY='id'
);

30. select
ailment.id as id,
ailment,
firstname,
lastname,
case
when ailment.rowtime > enroll_start * 86400 * 1000
and ailment.rowtime <= enroll_end * 86400 * 1000
then true
else false
end as covered
from ailment inner join patient
on ailment.id = patient.id
emit changes;

31. Questions?

32. Appendix

33. References
● Salesforce API Documentation
● Comparing PushTopics, Platform Events, and Change Data
Capture
● External Objects
● Confluent KSQL
● Kafka Transformations