I used Connector Builder to create a custom connector to an external API. I used OAuth 2.0 authentication (Client ID, Client Secret etc) but there are lots of options.
One quirk is you have to create at least one resource before you can publish the connector:
I named the resource DO NOT USE, because it’s just a placeholder, but it shows up in available activities as “List Records”:
I guess we just have to remember not to use that one. It’s not even a real endpoint so it’ll just fault.
Then I created an Integration Services Connection with that custom connector.
The cool thing is UiPath automatically creates a generic HTTP Request activity specific to your connector:
“Request URL” in that activity should be named “Relative Endpoint” though.
From that I created a library of activities to make it simple to use this application’s API for the operations we need:
The great thing about a library like this it builds the error handling (ie HTTP response status not 200) into the activity so you don’t have to repeat it in your process.
Yesterday while I was working on this with a colleague, at some point I said “we haven’t talked about a selector all day” 