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
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Business Rules
- Storage Buckets
- MCP Servers
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator user guide
Last updated Oct 2, 2025
When storing an asset of type Credential in a Google Secret Manager (read only) credential store, you must create the secret in Secret Manager with:
-
The name of the secret must match the External Name configured for the value (if using values per robot) or the asset name otherwise.
-
Google Secret Manager can only contain letters (
A-Z, a-z), numbers (0-9), dashes (-), and underscores (_). -
The secret value must be saved as a Secret Version with the following JSON structure:
{"Username": "user", "Password": "pass"}{"Username": "user", "Password": "pass"}
When storing an unattended robot password in a Google Secret Manager (read only) credential store, you must create the secret in Secret Manager with:
-
The secret name must match the External Name for that robot.
-
If no External Name is configured, the Username field is used instead, with invalid characters replaced by
_. -
The secret value must contain only the password for the robot.
