Choose “ No Authentication” for “ Authentication Protocol.”. (YesNo’s “API” doesn’t require you to log into it to use it.). Choose “ Anonymous” for “ Identity Type.”. Enter something useful like YesNo into “ Label” and “ Name.”. Outside of Flow Builder, in Salesforce Setup, search for and visit “ Named Credentials.”. Securityįirst, we need to tell Salesforce that it’s safe to talk to 3rd-party resources starting with. This time, instead of asking YesNo for a silly GIF by incorporating an “ Apex Action” into our Flow, we’ll do it by incorporating an “ External Service Action” into our Flow. The URL to a random GIF expressing the yes/no/maybe emotion returned, labeled “ image”. A true/false indicating whether we forced the answer to a specific yes/no/maybe value, labeled “ forced”. A random yes/no/maybe answer, labeled “ answer”. We’ll leverage a really fun “API” on the internet called “YesNo.”Īccording to its documentation, an HTTP GET request to will respond with plain text formatted according to the JSON standard indicating: #FINAL FANTASY 1 CHEAT CODES CODE#
Keep reading to try it yourself with an amusing side project.Īs before, it sure would be nice if we could leverage amazing code other people have put on the internet to do something fun with a Flow, right? About YesNo It might take a developer’s comfort with code, though, to write it in a way that is compatible with Salesforce External Services.)įor all practical purposes – particularly with real-world “APIs” from major companies – what you’re about to read is no-code.Įxternal Services use a small amount of “copy-and-paste” code that someone else wrote to let admins building Flows create business logic that talks to non-Salesforce computers over the internet. That’s what I had to do for the YesNo silly GIF service so that you could follow along in this tutorial.
(If the 3rd-party company forgot to write a schema, it is possible to write one yourself. The difference is that this time, we don’t have to write it. In that way, it functions like the Apex-Defined Data Types and Apex Invocable Action code we hand-wrote in the original post. The code you’ll be copying and pasting is called a “schema.” A “schema” specifies to your flow how the 3rd-party “API” you’re using wants to be talked to, and how it will respond. But it’s no more complicated than grabbing the snippet of HTML code that YouTube makes available when you click “Embed this video.”. Technically, you have to copy and paste a snippet of code, provided by a 3rd party (like Slack). Disclaimer: As I said, this is almost no-code.
0 kommentar(er)
