The document discusses the various challenges and methods for integrating with Salesforce, emphasizing the importance of understanding real-time data handling strategies and the use of pre-built connectors. It highlights key integration techniques such as using Salesforce APIs, platform events, and custom solutions tailored to specific use cases. Additionally, it explores different scenarios for pushing vs. pulling data out of Salesforce and provides an overview of potential use cases for integrating Salesforce with other systems.

1. The Integrations
Behind Connecting
With Salesforce
February 2021

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

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

4. Salesforce Integrations

5. One Perspective on
Salesforce

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

7. ● 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 AWS, MuleSoft, or
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

8. 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

9. ● Necessary to power downstream
systems/applications
● Do you push data out of Salesforce,
pull data out of Salesforce, or both?
● Pre-built connectors like AWS
AppFlow Salesforce Connector,
MuleSoft’s Salesforce Connector, and
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!

10. Real-Time Salesforce
Events

11. 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

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

13. Unlocking Salesforce Data With MuleSoft
Publisher (Platform Event)
Subscriber/Processing
Consumer Applications

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

15. ● Pre-built connectors help speed up
integrations
● Once data is in the
platform/technology of choice, can go
about integration processes like
normal
● Execute business logic
● Duplicate detection
● Can execute in a pub/sub model,
synchronize your data, and much
more
Salesforce Integration
Solutions

16. Use Cases

17. ● Centralize employee information and
management in a custom web
application
● Create reusable APIs that can be
secured, monitored, managed, and
tuned
● Manage system access
Use Case: API Ecosystem

18. ● 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 With Confluent

19. ● Synchronize data with a target system
to power a mobile application
● Two-way synchronization
● Duplicate detection
● Business logic
● Event-driven near-real-time
Use Case: Synchronizing SFDC Data

20. Hybrid and Demo Architecture

21. Two Different Perspectives
Vs.
Integration Centric
Salesforce Centric

22. Demo

23. Questions?

24. Appendix

25. References
● Salesforce API Documentation
● Comparing PushTopics, Platform Events, and Change Data
Capture
● External Objects
● Confluent KSQL
● Kafka Transformations
● MuleSoft Salesforce Connector
● AWS AppFlow
● Confluent Salesforce Connector