Workflow - HTTP Request Action Source

Hello Fellow Developers,

I am currently building out a workflow and need to implement the HTTP Request action. Could someone advise if the Workflow HTTP Request action is cloud executed, or VA executed? If it is cloud executed, do we know the Fully Qualified Domain Name (FQDN) of the source?

I have reviewed the documentation, but I could not identify any such details. This information is needed for network architecture and raising firewall rules.

All actions/processes in a workflow are cloud executed. As these are run as microservices on AWS cloud (most likely containerized packages) there would not be a FQDN for the source.

Are you trying to call a private API?

1 Like

Hello @iamnithesh,

Thank you for the confirmation, that is what I had suspected.

Yes, I am trying to call a private API. Since workflow is cloud executed, I suspect I will need an API Gateway to expose the interface to the cloud. Unless you know of simpler solution? Is there a way to pass the request off as a job to the VA?

Just curious , What do you mean by private API here?

I don’t think there is (or am sure there is not :smiley: ) a way to pass a job to VA.

In fact, there is no incoming traffic allowed to VA (but for local access via port 22) and it’s actually the VA pinging ISC cloud to pick the job from a task list.

Yes, exposing to cloud via an API Gateway is probably your only option in this case

1 Like

something that runs inside a private network like on-prem

2 Likes

private API URLs are accessible from the network only. those URLs are not public and cannot be accessed over internet

Got it . Thanks !
got confused with Private API terminology .