- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- 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
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Automation Cloud™ Robots - Serverless
- Configuring VPN for Cloud Robots
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Review Requests
- Test Automation
API triggers offer a streamlined way of starting a job via HTTP, through a custom request URL created by you. They work as a layer wrapped around existing processes, and leverage the options that are already available for triggers.
Once you create an API trigger, you can easily start a job in an external application and consume its output.
API trigger invocations and calls are authorized through personal access tokens.
All you need to do is generate a token that you can use to access the resources you need. For example, if your process requires read and write access to Orchestrator
job, you would select the
Once generated and copied, you can paste it in your bearer token field to authorize job requests.
These are the permissions you need to perform operations on API triggers:
Triggers permission at the folder level (this dictates the actions you can take on API triggers):
View - allows you to see API triggers within your tenant.
Edit - allows you to make changes to API triggers.
Create - allows you to create API triggers.
Delete - allows you to delete API triggers.
Jobs permission at the folder level (this is required to invoke a job trigger and follow the job execution until the result is available):
Create - allows you to start an API call based on an API trigger.
View - allows you to view the status of the API request.