Abstract: In some embodiments, a robotic process automation (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.

Abstract: 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.