- Introduction
- Getting started
- Build on any canvas
- Build with Case
- Reference
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Build with Flow
- HTTP Request
- Create a connection
- Popular connectors
- Build with BPMN
- Operating
- Monitoring
- Optimizing
- Reference information
Create a connection
Create a connection from a connector node, so that the Flow process can sign in to an app, without leaving the canvas.
A connection holds the sign-in details that connector nodes use to work with an app, such as Slack or Salesforce. You can create it from the node, and other nodes can then select the same connection. Connections are managed by Integration Service.
Before you start
- A connector node on the canvas. Connector nodes describes how they work.
- The sign-in details that the app asks for, such as an account in the app or an access key. The Integration Service page of each connector lists its sign-in methods. Popular connectors links to the most common ones.
Create the connection
- Select the connector node on the canvas.
- In the properties panel, on the Parameters tab, select the connection field, for example Slack connection.
- Select Add new connection. The Connect to page of the app opens.
- In Folder in which connection is stored, select the folder that holds the connection.
- If the page has Authentication Type, select the sign-in method.
- Fill in the fields that the page shows. They depend on the app and on the sign-in method.
- Optional: for an app in a private network, under Advanced settings, set Connection Type to Private (Relay) and fill in the URLs under Private Connection URLs, such as Base URL. Keep Standard for any other app.
- Select Connect.
- If the app's own sign-in page opens, sign in to the app and allow UiPath to access it. For Slack, for example, you enter your workspace, then select Allow.
- Back in the properties panel, the connection field still shows Select a connection. Open it and select the new connection.
Private (Relay) routes the connection through your own infrastructure, and an administrator must set up Relay first. Only connectors that use HTTP support it, so Snowflake, SAP BAPI, Oracle NetSuite, and Database Hub don't.
Result
The node uses the new connection. The connection list groups the connections by folder and shows the status of each one, such as Connected. Other nodes for the same app can select the same connection.
In Studio Web, the connection also appears under Connections in the resources of the Explorer. It can take a moment to show up there. Selecting it opens the connection in a tab, with its status and Edit connection.
To change a connection, select the pencil icon next to it in the list. To review all existing connections, select Open connections. It opens the Connections page, which lists each connection with its connector, account, status, and creation date.
Next steps
- Connector nodes: inputs, output, and errors of a connector node.
- Build a Slack notification workflow: create a Slack connection and use it, step by step.
- Connections in the Integration Service guide: share, reauthenticate, and manage connections.