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!
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
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/
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?
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
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.
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.
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.
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 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
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.
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?
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!
Awesome to hear. Enjoy.
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
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/
Now the get example got updated with named/external credentials here: salesforcebreak.com/2023/01/10/http-callout-beta-in-salesforce-spring-23/
Thank you! Very informative and useful!
Updated blog post with instructions: salesforcebreak.com/2023/01/10/http-callout-beta-in-salesforce-spring-23/
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?
That is a requirement of the API. Check the instructions for the API you are connecting to.
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?
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
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.
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.
These are very hard to troubleshoot. When you get stuck you may want to ask on sfxd.github.io/
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.
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
Hey, How did you resolve the issue? I am also facing a similar issue.
@@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
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.
Josh and I are here. Come; we can help: salesforcebreak.com/flow-support-slack/
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?
Have you set up trace and checked the logs?