orchestrator
latest
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Connections
- About Connections
- Managing Connections
- Business Rules
- Storage Buckets
- MCP Servers
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting

Orchestrator user guide
Last updated Nov 11, 2025
Connections help in establishing tasks between single users and external applications. The connections are created once users authenticate with an API Provider.
The following table describes the fields available on the Connections page:
| Field | Description |
|---|---|
| Connection name | The name of the connection. |
| Connector | The name of the connector used to create the connection. |
| Connection account | The account used to create the connection. |
| Authentication type | The authentication type used to create the connection. The possible
options are:
Note: Available options may vary depending on
the connector.
|
| Status | The status of the connection. The possible options are:
|
| Polling frequency | How often the system checks an external application for updates or new events. |