top of page

Hi there! I’m Paris

Homepage- CB.png

Building custom connectors to enhance cloud automation

Project

UiPath - Connector Builder

Summary

UiPath, a leader in UI Automation, was expanding into cloud automation. To support this shift, there was a need for a more streamlined approach to adding and deploying native API integrations. As the lead designer, I was responsible for creating the Connector Builder MVP, a developer-friendly solution to address complex technical challenges and enhance the platform’s integration capabilities.

Lead Product Designer

Role

Defining the Problem

​Creating API integrations involves connecting different software systems, which can be challenging due to compatibility, complexity, scalability, and security concerns. Each system may use different technologies, making smooth communication difficult. Integrations need to be easy for developers to set up, scalable as demands grow, and secure when sharing data. The Connector Builder was designed to guide users through these technical challenges and complexities, providing a user-friendly, flexible, and secure solution.

Setting the project scope

Connector Builder was envisioned as a solution for native cloud integration. The business chose to develop the MVP to validate market need and explore future integration with the rest of the product line. Key areas of focus included solving the authentication process, adding resources, normalizing data, debugging, and deployment.

Discovery

To understand how API developers create integrations and where RPA developers would utilize this solution, I collaborated with the research team to plan and execute evaluative research. Key activities included:

  • User Interviews: Informal discussions with API developers to clarify the anatomy of APIs.

  • Card Sorting: Workshops with RPA developers to gauge their understanding of APIs.

  • Analysis: Reviewing findings and sharing insights with the team.

​

Key Learnings:

  1. Understanding and Planning: Around 30% of the time is spent preparing and understanding third-party services. Successful integration requires users to have a solid grasp of the API’s capabilities.

  2. User Expectations: RPA developers expect a plug-and-play experience. A low-friction setup helps them focus on the bigger goal of building automation, reducing task abandonment and missed information.

  3. Documentation Needs: RPA developers often build automations to solve business problems, and these solutions must be maintainable by others. Clear documentation attached to integrations is crucial.

Connector Building - User Journey.png

Prototyping a Solution

While engineers developed a technical proof-of-concept, I began designing the first prototype in Figma. This prototype aimed to validate the solution and support discussions about user flow, language, features, and resource prioritization.

Connector Builder User Journey 4.png
Connector Builder User Journey 01.png
Initial Prototype.png
Prototype Iteration 1.png
Prototype Iteration 2.png
Prototype Iteration 3.png

Through multiple user interviews, we prioritized features and identified three main use cases, focusing on their business impact and technical feasibility. After each iteration, the research team and I conducted user testing sessions, gathering insights that drove rapid iterations to validate our hypotheses.

MVP Iterations

Outcome

The final solution enabled the creation of UiPath native connectors, allowing RPA developers to enhance UI automation with cloud solutions and reuse these integrations across different automations with varied credentials. 

 

To guide users through the complexities of creating integrations, we included features such as importing API schemas for a faster starting point, single-resource debugging/testing, and a publishing process that added essential context to each connector.

bottom of page