This document provides an overview of the Salesforce Composite API and its benefits for consultants. It discusses how mastering integrations through the Composite API can help consultants become more valuable team players and ensure project success. Examples are given of how the Composite API allows performing multiple operations in a single request, such as creating an account and contact together. Authentication using the Connected App or user credentials is also summarized. Overall, the document encourages consultants to learn the Composite API to improve their technical skills and better understand client needs for integrations.
3. A consultant's journey towards career growth by
- mastering integrations
- becoming an indispensable team player
- driving project success through collaboration, expertise, and confidence
4. Success story from client I work with:
2 external systems connected to Salesforce
Hundreds of orders daily
Data sync from external database
Few weeks delivery time ( design, POC, development, testing, documenting, waiting for third parties )
3 people team
Don't hold yourself back when things are a little bit more technical
Empower yourself with confidence and expertise, leaving uncertainty behind as you master the integrations.
External
Database
Salesforce
Accounting
System
Project success story:
5. Quick Technical Overview: What is integration + key terms
- IT integration, or systems integration, is the connection of data, applications, APIs, and devices across organizations
External
System
Salesforce External
System
Salesforce
External
System
Salesforce
INBOUND OUTBOUND BIDIRECTIONAL / TWO WAY
basic request vs composite request
- single operation vs multiple operations in one request
- integration provider (e.g. Mulesoft )
- what is endpoint?
a specific URL where a web application or a web service
can be accessed and interacted with.
- what is request?
- specific instruction made from one system to another.
- getting or posting data
- query, create, update
6. - why should you care?
- potentially better understanding of client needs and business process
- avoid task/communication ping pong with devs
- by managing to pass a request successfully you have a proof for devs or external parties.
- you can identify and solve potential obstacles sooner: validation rules, missing permissions, fields naming
typos and more
Become an essential team player by synergizing with senior developers on cutting-edge integration projects.
7. 5 keys to open a vault: SF Authentication
Connected app: 2 keys:
1. Client Id,
2. Client Secret
User perspective: 3 keys:
1. Secret token (login as user, reset secret token),
2. Username
3. User password
Tool:
Use postman to authorize an send requests to Salesforce
Free to use
🗝 CLIENT ID
🗝 CLIENT SECRET
🗝 USERNAME
🗝 PASSWORD + 🗝 SECRET TOKEN
🗝 ACCESS TOKEN
ENDPOINT:
HTTPS://[SF_ORG URL]salesforce.com/services/oauth2/token
9. Write documentation effortlessly
- You will know what you documenting, because you have understanding
- Just provide few sentences of context + request
- Request (CURL) itself can be used as a documentation
- Don’t forget anonymization of sensitive details
- no dev would ever complain about this documentation style
- feel free to attach printscreens from postman
10.
11. Composite requests examples:
example: create Account + Contact in a single request
query and insert/update in single request
multiple queries example
multiple objects creation
all or none attribute
internal referencing within the composite request (@annotation)
15. Summary
- Personal Impact - don’t hold yourself back
- Business Impact - be more valuable for your client, more competent for external parties
- Technical Impact - improve integrations by implementing Composite API
- I am happy to meet you at Enehano stand to discuss more details
- Don't hesitate to reach me at Linked-In for more details or help :)
- www.linkedin.com/in/julius-hudak/