RPA Workflow API Invocation for Reusable Automation Fragments

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex RPA projects often require specialized knowledge and are costly due to multiple parties involved in maintenance and customization, and existing automation solutions are not easily reusable or adaptable to specific tasks and environments, posing challenges for 'citizen developers' lacking advanced programming skills.

Innovation Solution

A computer system with an RPA conductor that coordinates RPA robots, receives user inputs to select workflows, determines API call parameter values, and selectively triggers execution by RPA robots, facilitating user-friendly automation for non-specialist developers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If RPA projects are designed by specialized developers, then automation functionality is achieved, but maintenance and customization become costly and slow due to multiple parties involved

Engineering Contradiction:
Improveease of automation developmentVSAvoidmaintenance and customization time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent enables citizen developers to independently create, configure, and maintain RPA workflows through intuitive visual interfaces without requiring specialized programming knowledge. Users can directly modify workflow parameters, add activities, and customize automation behavior through drag-and-drop operations, eliminating dependence on specialized RPA developers for routine maintenance and customization tasks.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The workflow editor provides a universal interface that handles multiple automation tasks and configurations through a single unified system. The same visual editor can create different types of workflows, manage various RPA robots, and adapt to diverse automation scenarios, reducing the need for multiple specialized tools and developers.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Manufacturing precision

If RPA solutions are tailored to specific tasks and environments, then automation precision is improved, but reusability and adaptability decrease

Engineering Contradiction:
Improveautomation task precisionVSAvoidworkflow reusability
Core Design Contradiction:
Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The patent segments RPA projects into modular workflows that can be independently configured, executed, and reused. Each workflow represents a discrete automation task that can be selectively invoked based on specific conditions or triggers, allowing precise automation for particular tasks while maintaining the ability to reuse and recombine workflow components across different environments and use cases.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If RPA workflows are made user-friendly for citizen developers, then ease of operation improves, but system complexity increases due to selective invocation mechanisms

Engineering Contradiction:
Improveuser-friendliness of RPA interfaceVSAvoidcomplexity of workflow selection mechanism
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system introduces an intermediary workflow registration and selection mechanism that automatically matches user needs with appropriate workflows. Instead of requiring users to manually configure complex selection logic, the system provides automated routing and workflow discovery features that simplify the interaction between citizen developers and the underlying complex workflow management infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12498701B2Selective invocation of RPA workflows via API calls
Publication Date: 2025.12.16 UIPATH INC
  • US12498701B2 patent drawing
  • US12498701B2 patent drawing
  • US12498701B2 patent drawing

AI summary

In some embodiments, an RPA design interface enables a user to select an RPA workflow forming a part of a complex RPA project, and define the selected workflow as a distinct executable entity that can be invoked remotely via an API call (e.g., HTTP request) issued to an RPA conductor orchestrating the execution of multiple RPA robots. The RPA design interface enables the user to customize a set of API call parameters (e.g., HTTP method, URI, input and/or output arguments) for invoking the respective RPA workflow. The user-defined, workflow-specific API call parameter values may then be transmitted to the RPA conductor, for instance as metadata attached to a specification of the RPA project. In turn, the RPA conductor automatically generates an API specification (e.g., OpenAPI or Swaggerâ„¢) for the workflow fragment. In response to receiving an API call configured with the respective workflow-specific call parameter values, the RPA conductor selectively triggers execution of the selected RPA workflow on a selected RPA robot.