What is the purpose of Iclient and how to use it in a flow?
iclients are used to store the company level credentials for APIs that use authorization/authentication frameworks that requires 2 levels of credentials (typically company and user level), and then any number of connections can re-use the same iclient so that fields like client id and client secret for oauth 2.0 based APIs do not need to be re-entered for every different connection.
iclients have mostly remained behind the scenes in integrator.io, and historically you had to use our API to manage them in your account. You can create and edit them in the UI from the HTTP connection drawer, but iclients are lacking full UI support and also lacking documentation.
Next year, we will be re-releasing this resource, and we will be exposing them as a first class citizen in the Resources section of the left nav side bar, and there will be full CRUD support in the UI, and full documentation, help text, etc... Please keep an eye out for this in our release notes.
I came here searching for iClient as I saw it mentioned in a help article. @scotthenderson when you say
HTTP connection drawer
What do you mean by "drawer"? Is it the dialog that opens when you click the edit icon on the client field on the HTTP connection?
Yeah, a "drawer" is just a dialogue that opens in a specific way on the screen.
On a side note, we just finalized all our frontend and backend designs this week for exposing iClients, and we are also planning to move a bunch of fields currently on the HTTP connection page to the iClient resource, and hopefully we get all this implemented in time for our first or second release early next year; and then it is going to be much much easier to configure oauth 2 based connections. I am really excited that we are finally improving this part of the product.