Sudipta Deb

Sudipta Deb

Founder of Technical Potpourri, Co-Founder of Shrey Tech, Enterprise Cloud Architect

In the ever-evolving landscape of customer relationship management (CRM) and enterprise solutions, Salesforce continues to lead the charge with innovative updates and enhancements. The much-anticipated Spring ’24 Release brings a plethora of features aimed at empowering users to streamline their workflows and achieve unparalleled efficiency. Among the standout improvements is the revolutionary enhancement to Salesforce Flow, allowing users to verify API connectivity and perform HTTP callouts directly within the platform.

Traditionally, integrating external systems or fetching real-time data from web services within Salesforce Flows has been a multi-step process involving Apex code or external tools. However, the Spring ’24 Release marks a paradigm shift by introducing a built-in capability to validate API connections and execute HTTP callouts seamlessly, all within the intuitive and user-friendly environment of Salesforce Flow.

This enhancement not only simplifies the development process but also opens up a new realm of possibilities for administrators, developers, and business users. Now, with just a few clicks, Salesforce users can validate the connectivity of their APIs and effortlessly incorporate external data into their processes, all while harnessing the power of declarative automation.

In this blog post, I will delve into the details of this groundbreaking feature, exploring how it can be configured, its potential applications, and the significant impact it can have on the overall Salesforce user experience. 

Watch The Video Or Read The Article (or do Both)

Salesforce Spring 24 Release Youtube Playlist

📌 Salesforce Spring 24 Release Youtube Playlist – https://bit.ly/3wyAB9I

Prerequisite

Since I am going to build the flow from where I will be calling the API, I need two things. One is definitely the API which I will be calling and the second one is to configure Named, External Credentials and add them to the Permission Set. Finally I need to assign the permission set to my user record so that I can call the flow and perform HTTP callout.

API that I will be calling is called Bored API. The Bored API helps you find things to do when you’re bored! There are fields like the number of participants, activity type, and more that help you narrow down your results.

Link: https://www.boredapi.com/

For the second one to configure Named, External Credentials and add them to the Permission Set, I have dedicated blog post/video which you can read.

Link: How to add Named Credentials to Permission Set using Pricipals

 

Let’s Build The Flow

Let’s first start with a screen flow. In the first step, I will create a screen and inside the screen, I will be using a Display Text component with the message – Do you want to know what you can do next?

Now in the next step, I will add an Action element. Within the action element window, I will select Create HTTP Callout. Here I will be creating the external service and also select the named credential that authorizes the connection between Salesforce and the API. NoteBored is the name of my Named Credential.

Now in the next screen, I will configure HTTP callout method and details for the invocable action. In my case, I am labelling it as GetBoredCall. This is going to be a GET call, so I choose GET under Method. Finally in the URL Path, I am going to put /api/activity to complete it.

In the next screen, you will find the new feature that is coming up with Spring 24 release. Here you will get two options to select sample response method. The first one is Connect for schema which establishes a connection to the API endpoint and retrieves a response, generating an accurate, real-time sample response. The second one is to Use Example Response which is nothing bu to configure the sample response by pasting an example API response without establishing a real-time connection to the API endpoint.

I will choose the first option i.e. Connect for schema and click on Next. Here in the next screen, the moment I will click Connect, it will create a real-time call to the system. I will use the response from the selected system to configure the HTTP Callout. As you can see in the below screenshot, based on the response, the Data Structure is already being populated.

In the next screen, I will configure the action by giving it a name and label. Finally I will click on Done.

Finally, I will put one more screen to display the result of the API which is basically some sort of recommendation to come out of the boredom. Lastly, I will save and activate the flow.

Let’s Run The Flow

When I will run the flow, it will perform HTTP callout and fetch the recommendation, which I will display in the flow screen.

Conclusion

In conclusion, Salesforce’s Spring ’24 Release represents a pivotal moment in the evolution of the platform, with the introduction of a game-changing enhancement to Flow. The ability to validate API connectivity and execute HTTP callouts directly within Salesforce Flow marks a significant stride towards simplifying and democratizing the integration process. This newfound capability not only streamlines development but empowers users across roles to effortlessly bring external data into their workflows. As organizations strive for agility and efficiency in their operations, the Spring ’24 Release propels Salesforce Flow into a central role, where it becomes not just a workflow automation tool but a dynamic hub for seamless API interactions. 

I will be publishing more blogs and videosc around Spring 24 Release. So please subscribe to my blog and youtube channel

📌 Salesforce Spring 24 Release Youtube Playlist – https://bit.ly/3wyAB9I

Disclaimer

This article is not endorsed by Salesforce, Google, or any other company in any way. I shared my knowledge on this topic in this blog post. Please always refer to Official Documentation for the latest information.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *