Node-RED

https://nodered.org/

Download no UiPath Marketplace

O Node-RED é uma ferramenta de programação para conectar dispositivos de hardware, APIs e serviços online.

Ele fornece um editor baseado em navegador que facilita a conexão de fluxos usando a ampla gama de nós na paleta que podem ser implantados no runtime com um único clique.

O Node-RED é a ponte que conecta a UiPath ao mundo digital. Ele oferece o Orchestrator no ultradrive, permitindo que você conecte o UiPath a ambientes como Webhooks, Interfaces Gráficas personalizadas e Internet das logs.

O Node-RED pode ser usado com os seguintes nós:

Conexão

Um nó de configuração que autentica todas as chamadas feitas ao Orchestrator e atualiza automaticamente os tokens de API quando necessário.

On Premises

• URL: The URL of your Orchestrator instance.
• Tenant: Your tenant
• Username: Your username
• Password: Your password. This value is encrypted when the flow is saved.

Cloud

• User Key: The secret key that identifies your user.
• Account: The logical name of your account at https://platform.uipath.com .
• Tenant: The logical name of the tenant (AKA service) to which you want to connect. Each account may support multiple tenants
• Client ID: The unique identifier of https://platform.uipath.com.

Solicitar

O nó de solicitação é um wrapper da API completa do Orchestrator que permite que qualquer solicitação seja feita. Atualmente, este nó é compatível com a v2018.4 e pode ser usado com unidades organizacionais (recurso experimental). Os seguintes campos são necessários:

• Login - The connection node used to authenticate all calls.
• Category - The target Orchestrator element (such as Robots, Queues, Assets).
• Action - The list of actions available in the selected category (such as Get All, Add to Queue, and Delete Asset).
• Parameters (optional) - Input parameters for the specified action. These are formatted according to the Swagger guidelines.

Start job

Esse é o nó de conveniência que inicia um trabalho. Os seguintes campos são necessários:

• Login - The connection node used to authenticate.
• Process - The name and environment of the process to be run. If no environment is provided, the first one found to contain the selected process is used. Please note that input parameters are available when starting a Job as of v2018.3.
• Execution Target - The robot scheme used to run the job. You can choose to run a job on a particular robot by its name, on all robots simultaneously, or to run the job a number of times, allocating the work to available robots. If an incorrect robot name is specified, jobs do not run. If a larger number of robots than are available is specified to run, the job runs on all robots.
  Observação:

  Complete Folder support will be added in the next version. To use Organization Units or Folders now, add the X-UIPATH-OrganizationUnitId parameter to the Request or Start Job nodes. Here is a sample flow that grabs the ID of the Organization Unit, saves it as a flow variable, and then uses it to get all Assets from Orchestrator. You can import this flow from the hamburger menu in the top right corner.

Output messages

Output messages are delivered as raw JSON objects. They contain the response from each API call in the msg.payload object.