Connector nodes that integrate third-party services directly on the canvas with pre-built operations.

Connector nodes let you work with other apps directly from the canvas, without setting up HTTP requests yourself. Each connector provides ready-made nodes for one app, such as GitHub, Salesforce, Slack, or Microsoft 365, with typed inputs and outputs, and a connection that handles sign-in for you.

Connector nodes are in the Connector category of the Add node panel. The category starts with HTTP Request, which calls any web address, followed by the apps, from Act! 365 onward. Each app opens the list of its actions.

The connectors available to you depend on your organization, and the Connector category of the Add node panel lists all of them. They cover apps such as Salesforce, ServiceNow, and Slack. Popular connectors links to the most common ones, and Connectors in the Integration Service guide documents each one, with its setup, sign-in, and operations.

The Add node panel lists the connectors available in your organization. Each connector node maps to a specific API operation on the target service.

When you add a connector node to the canvas, Maestro Orchestrate fetches its input schema and renders a dynamic configuration form in the properties panel. You fill in the required fields, select a connection for authentication, and the node handles the API call at runtime.

Every connector node needs a connection, which signs UiPath in to the app with your account. You select the connection in the properties panel when you set up the node. The connection field lists the existing connections, grouped by folder, with Add new connection to create one without leaving the canvas, and Open connections to review all of them. Create a connection has the steps.

Connections handle token refresh, OAuth workflows, and credential storage automatically. Auth headers and secrets are not managed directly. Connections are managed by Integration Service. Connections in the Integration Service guide describes how to share and manage them.

Each connector node has its own input fields based on the API operation it wraps. The properties panel renders these dynamically. You'll see different fields for a "Create Issue" node than for a "List Repositories" node, even within the same connector.

All input fields support variable expressions ($vars.<nodeName>.<property>).

Connector node output is available at $vars.<nodeName>.output. The shape of the output depends on the specific node and the API it calls.

Connector nodes support error handles. If the API call fails and an error handle is connected, the run continues on the error path with the standard error object at $vars.<nodeName>.error.

Error handling has the details.

Some connectors also provide triggers: start events that fire when something happens in the external service (e.g., a new email arrives, a form is submitted). Connector triggers appear in the Triggers section of the node palette.

Trigger inputs are owned by the trigger and accessed as $vars.<triggerName>.output.<inputName>. Triggers has the details.

Rule of thumb: The node palette is the first place to check for a connector. HTTP Request is the fallback when no connector exists for the target service.