Easy HTTP Callout Builder with Josh Dayment - Salesforce Spring 23

  Рет қаралды 4,283

Salesforce Break

Salesforce Break

Күн бұрын

Пікірлер: 22
@anne-mariemessineo2244
@anne-mariemessineo2244 7 ай бұрын
Thank you so much! Was having problems with getting this to run (and troubleshooting was impossible) and it seems it was because I had it in a Create or Update. Switched to Create Only and now I see it work. PHEW! So glad I found your video!
@SalesforceBreak
@SalesforceBreak 5 ай бұрын
Awesome to hear. Enjoy.
@salesforcetr
@salesforcetr Жыл бұрын
Thank you for this great video. I suggest to store the apikey (Access Token/BEARER) in Named Credentials. By this way, we don't need to create a Custom Label to store credential info
@SalesforceBreak
@SalesforceBreak Жыл бұрын
Great tip! We illustrated better when we did the POST method blog series here: salesforcebreak.com/2023/06/03/http-callout-in-salesforce-summer-23-post-beta-3-3/
@SalesforceBreak
@SalesforceBreak 11 ай бұрын
Now the get example got updated with named/external credentials here: salesforcebreak.com/2023/01/10/http-callout-beta-in-salesforce-spring-23/
@rohberg2
@rohberg2 Жыл бұрын
Thank you! Very informative and useful!
@SalesforceBreak
@SalesforceBreak 11 ай бұрын
Updated blog post with instructions: salesforcebreak.com/2023/01/10/http-callout-beta-in-salesforce-spring-23/
@christophercollier2256
@christophercollier2256 Жыл бұрын
This was so helpful, specifically the parts about the asynchronous path and how response variables are stored. Question: how did you create the global variable to store the API key for reference in your flows?
@SalesforceBreak
@SalesforceBreak Жыл бұрын
Do join us here and ask your questions on the general channel. We are all listening: Join me on Slack -- it’s a faster, simpler way to work. Sign up here, from any device: join.slack.com/t/salesforcebreak/shared_invite/zt-va4v08ua-b2EvgXAGUR6X04JmyZcIFA
@jkaforever1
@jkaforever1 Жыл бұрын
He used Custom Label which stores single text value, can be found in Setup. I advise against it for security concerns and there are better ways to store/access your api keys.
@brocadecity
@brocadecity Жыл бұрын
This is exactly the video I've been needing. A very basic question: how is one able to tell if a flow needs an API key?
@SalesforceBreak
@SalesforceBreak Жыл бұрын
That is a requirement of the API. Check the instructions for the API you are connecting to.
@ceylankesenek8601
@ceylankesenek8601 Жыл бұрын
Hello, great video, excellent exercise. I have a question. I tried to implement the same flow but I am not receiving the data. When I debugged the flow it shows a 404 response. I couldn't figure out where the mistake could be. Do you have any ideas? Thank you.
@SalesforceBreak
@SalesforceBreak Жыл бұрын
Do join us here and ask your question on the general channel for efficient troubleshooting: join.slack.com/t/salesforcebreak/shared_invite/zt-va4v08ua-b2EvgXAGUR6X04JmyZcIFA
@AmanPathak17
@AmanPathak17 Жыл бұрын
Hey, How did you resolve the issue? I am also facing a similar issue.
@ceylankesenek8601
@ceylankesenek8601 Жыл бұрын
@@AmanPathak17 it's been a while, I couldn't figure out why. But those times it was beta feature. Now that it might work. I didn't try again since then
@AmanPathak17
@AmanPathak17 Жыл бұрын
Hi, I am stuck with a problem while doing an Integration with an External System using Salesforce Record --Triggered Flow that runs Asynchronously. The integration requires me to do multiple POST requests and proceed based on their response. But before the first HTTP Callout finishes the flow moves to the next HTTP callout which needs a value from the response of the previous HTTP call. So it is failing because the value is null as the first one hasn't been completed yet. Please help me with this.
@SalesforceBreak
@SalesforceBreak Жыл бұрын
These are very hard to troubleshoot. When you get stuck you may want to ask on sfxd.github.io/
@WillMoody-crmstorm
@WillMoody-crmstorm Жыл бұрын
Thanks guys! Do you know how the callout manages responses to tell it that it has been sucessfully received. I am sending to a webhook that responds 200, but Salesforce doesn't seem to be receiving it, and hence retries regularly, tripping the webhook multiple times and dreatign duplicate actions. The HTTP invocable action in my flow has the following error: Unable to map response for output parameter 2XX of invocable action CalloutInvocableAction. Received response: true . Do you have any ideas?
@SalesforceBreak
@SalesforceBreak Жыл бұрын
Have you set up trace and checked the logs?
@dazau
@dazau Жыл бұрын
I replicated the phone number verification flow and can get a 200 response (means all ok) but no details are being returned. Maybe I need to go back thru the video once more.
@SalesforceBreak
@SalesforceBreak Жыл бұрын
Josh and I are here. Come; we can help: salesforcebreak.com/flow-support-slack/
How to Integrate with No code! - Salesforce HTTP Callouts in Flow
26:26
Salesforce Adam
Рет қаралды 3,2 М.
Incredible New Salesforce Flow Features in Summer 24
23:01
Salesforce Break
Рет қаралды 4,4 М.
Random Emoji Beatbox Challenge #beatbox #tiktok
00:47
BeatboxJCOP
Рет қаралды 58 МЛН
CAN YOU DO THIS ?
00:23
STORROR
Рет қаралды 49 МЛН
Trick-or-Treating in a Rush. Part 2
00:37
Daniel LaBelle
Рет қаралды 42 МЛН
What is Salesforce (and why is it so good)?
12:47
David K. Liu
Рет қаралды 461 М.
Apex: What’s New and What’s Coming
32:03
Salesforce Developers
Рет қаралды 4 М.
How To Compare Flow Versions Using Gearset
8:56
Salesforce Break
Рет қаралды 209
Screen Flow UI Best Practices
52:34
Salesforce Apex Hours
Рет қаралды 5 М.
How The Transform Element Saves You Loops
9:48
Salesforce Break
Рет қаралды 1,5 М.