Access Token for Automation Anywhere

Configure an access token to connect to Automation Anywhere.

Figure: Automation Anywhere Access Token Configuration screen

Automation Anywhere Access Token Configuration screen

Background and Setup

Good to Know

  • In most cases, you can use a global access token or an app level access token:
    • Global access tokens are shared across all users and apps. If you want all process designers and runtime app users in your AgilePoint NX tenant to be able to connect to an external data source, use a global access token. An example is a SharePoint site on an intranet that all employees in a company can access.
    • Application level access tokens are shared with all processes in a process-based app, or restricted to use within a form-based app. Use application level access tokens if only process designers or runtime app users for a particular application should access an external system — for example, a Box account that is only used to share files within a small team.
  • Access tokens are collections of credentials that are used to authenticate communication directly between AgilePoint NX and an external system. Because it is the AgilePoint NX system that uses these credentials, rather than an app, there is no difference between design time and runtime access tokens. Access tokens are never checked in or published, and they do not use version control. If you change an access token in the App Builder or Manage Center, the access token changes immediately everywhere the access token is used. Changes to app level access tokens apply to all versions of an app, including running application instances. Changes to global access tokens apply everywhere they are used in AgilePoint NX. You can not roll back an access token to a previous version.

    For more information, refer to What Data Is Deleted When I Delete an App or Application Resource?

  • This screen may look different in different places. The UI varies for this screen depending upon how you open it. However, the fields for this screen are the same in all places.
  • Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Fields

Field NameDefinition

Token Name

Function:
Specifies the unique name for your connection to Automation Anywhere.
Accepted Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Function:
A description for your access token.
Accepted Values:
More than one line of text.
Default Value:
None
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Control Room URL

Function:
Specifies the base URL for Automation Anywhere Control Room.
Accepted Values:
The Control Room URL comes from Automation Anywhere.
Default Value:
None
Example:
https://trial.cloud.automationanywhere.digital

API Key/Password

Function:
Specifies whether to use an API key to connect to Automation Anywhere Control Room.
Accepted Values:
  • API Key - Uses an API key to connect to Automation Anywhere Control Room.
  • Password - Uses user credentials authentication to connect Automation Anywhere Control Room.
Default Value:
API Key

User Name

Function:
Specifies the user name for Automation Anywhere authentication account.
Accepted Values:
The user name for your Automation Anywhere account.
Default Value:
None
Accepts Process Data Variables:
No

API Key

Function:
Specifies the API key to call the Automation Anywhere service.

The API-Key is a 40-character string generated in Automation Anywhere Control Room.

To Open this Field:
  1. On the Automation Anywhere Access Token screen, click API Key .
Accepted Values:
An API key from Automation Anywhere.
Default Value:
None

Password

Function:
The password for the authentication account.
To Open this Field:
  1. On the Automation Anywhere Access Token screen, click Password.
Accepted Values:
An alphanumeric string that represents a password.
Default Value:
None
Accepts Process Data Variables:
No

OAuth 2.0 Access Token

Function:
Specifies an OAuth 2.0 access token fromAutomation Anywhere.
Accepted Values:
An OAuth 2.0 access token

This value comes from Automation Anywhere.

Default Value:
None.

Get OAuth 2.0 Access Token

Function:
Sends a request to the Automation Anywhere service to get the access token.

Renewal Rate

Function:
Specifies how frequently to renew your application's access token.
Accepted Values:
  • Disabled
  • Every 10 minutes
  • Every 15 minutes
Default Value:
Disabled