UiPath Integration Service is the component of the UiPath Platform that makes the automation of third-party applications much easier by standardizing authorization and authentication, helping you manage API connections and also allowing faster integration into SaaS platforms.
By using pre-built APIs, the development of automation projects in UiPath Studio is more simple and more consistent, regardless of the third-party applications you are automating.
In a nutshell, Integration Service does the following:
- Enables automation with an out-of-the-box library of connectors.
- Helps setting up and managing connections easily with standardized authentication.
- Enables kicking off automations with server-side triggers or events.
- Provides curated activities and events (with additional data filters) for ease of use.
- Simplifies automation design by providing a uniform experience across all Studio designers.
The three components of Integration Service are:
Integration Service comes with a large and growing catalog of popular, pre-built connectors. Any third-party application can be coupled with the specific connector and server-side triggers, so that robots react and respond automatically. Once set up, these connectors can be used in UiPath Studio and other products as well, such as UiPath Apps. Each connector has its own separate section in this user guide, so check out the documentation for the connectors you want to use.
Each third-party application connector comes with a dedicated set of activities that allows you to combine automation at the API level with regular UI automation for that specific application.
The activity packages help you reduce the process development efforts for API-based native integrations. These native integrations allow robots to seamlessly communicate directly with third-party systems as part of an automated process.
Compared to UI Automation, API Automation often requires specific target platform knowledge and API automation development skills. Nevertheless, once implemented, API automations typically run a lot faster than UI-based automations and usually require significant less maintenance.
Complementary to any existing options that are available in the connector catalog, you can also build your own custom connectors for any system integration using the Connector Builder.
With Connector Builder you can rapidly add any third-party application in the connector catalog, based on third-party APIs, so that it becomes available across your UiPath portfolio. Once published, you can integrate with any API that you need, create connections, build applications with these connectors and so on. For more information, check out the Connector Builder section.
Connections allow you to establish tasks and exchanges between single users and external applications using the authentication process of the API provider.
When you select a connector, the connections for that specific connector are displayed. In the Connections tab, however, you can see a list of all the defined connections for all the connectors. If the connection status indicates Success, it means that the connections are functional and you can start using them in UiPath Studio to create automation projects.
With the introduction of folder awareness within Integration Service, connections are now created within the folders, following the Orchestrator's folder structure and permission management. You can now create connections in different folders and share the third-party application connections with other users across the organization. You can also make the connections accessible for both attended and unattended users, groups, and robots. For more information on folder structure and permission management, check out the Folders documentation in the Orchestrator guide.
For more information, check out the Connections page.
Triggers provide a mechanism for subscribing to specific events from the third-party applications, giving you the flexibility to automatically start processes in Orchestrator. Automations can be kicked off based on events in connected systems by using triggers. Before using triggers, you need to have an automation project created, published and a trigger configured for that specific context. For more information, check out the Triggers page.