Http Endpoint to Trigger and receive data from Flow

Process: I want to be able to start a ‘flow’ by hitting a unique endpoint, that essentially kicks off the flow, and the output of the flow gets returned as a response in the HTTP payload of the calling request.

Steps:

1 - Create a flow (trigger would be the HTTP hitting of the Flow URL that is unique once the flow is created)

2 - Flow does some things, like say a. retrieve an RSS feed, then converts the output to a new format using some field mappings

3 - The response action will be an HTTP output that renders the data from the flow process that may take a second or more to execute

Benefits:

1 - extend the flow triggers to utilize HTTP triggers (like webhooks but on-demand)

2 - Real time execution and response can be leveraged

3 - workflows that require some pre-processing can easily be created with no/low code persons and the output available to other calling apps

4 - lowers the need to ‘send the output of this to another server’ or even ‘schedule this to run at a certain time, then have that output be available somewhere else’. Its all done in real time, on-demand at a URL endpoint

5 - allows for authentication checking to be done as well (future) as part of the HTTP trigger i.e. Ensure some header matches, or do some basic digest or basic auth to check if the process can proceed to the next step etc (header / meta data from the call can be available in the next ‘flow’ action which can then verify whether the request should be responded to, separating the Trigger from the Authentication needs of the flow.

Profit