I’ve been successfully using ordinary HTTP request activity to trigger Orchestrator APIs (on-prem if that matters) and recently I discovered that there is a dedicated Orchestrator HTTP request activity, which should be easier to use (I guess?).
I thought it will use the robot’s connection to Orchestrator to trigger APIs (which was a wild guess) but turns out I still need to authorize first. However, in the Orchestrator HTTP request there is no way to set the “Authorization” header in a consecutive API call.
So my question is, how do you use it?