Automation Anywhere (Cloud)
With the Automation Anywhere modules in Make you can:
trigger a bot
call APIs
To get started with Automation Anywhere, create an account here.
Connect Automation Anywhere (Cloud) with Make
Note
To connect to the Automation Anywhere (Cloud) app, you must have:
a Bot Runner license in the Automation Anywhere Control Room
a default device assigned to a user in the Automation Anywhere Control Room
Log in to your Make and add a module from the Automation Anywhere (Cloud) app into a Make scenario .
Click Add next to the Connection field.
In the Connection name field, enter a name for the connection.
In the Control Room URL field, enter your control room URL address in the
http://<domain>.my.automationanywhere.digital
format. This is a URL address used to access your Automation Anywhere application.In the Username field, enter your account's username field.
You can authenticate the Automation Anywhere account either by using API key or your account password. In the Authentication Method field, select the option and enter the value to authenticate the account.
In the API Key field, enter the API key generated in your account. Using API keys is a way to authenticate an application accessing the API, without referencing an actual user (for example, in the organizations that support SSO). The app adds the key to each API request, and the API can use the key to identify the application and authorize the request. Users can generate an API key in the AA control room. See how to generate the API key.
In the Password field, enter your account's password.
Click Continue.
You have successfully established the connection and can now build scenarios .
Trigger a Bot
Triggers a configured bot from Automation Anywhere.
This module allows you to trigger the bot that was configured in your Automation Anywhere Control Room and execute it on the user’s default device. Only unattended automation is possible at this point.
Prerequisites to deploy or trigger a bot:
View and Run my bots feature permissions
Run and schedule permissions for the folder that contains bots
Access to Bot Runner licensed users
Access to either a default device or a device pool
Connection | Establish a connection to your Automation Anywhere (Cloud) account. |
Type of Action | Select the action type for the bot:
|
Bot | Select or map the bot (created and pre-configured in Automation Anywhere) you want to trigger and enter the details in the fields that auto-populate based on the selected bot. Map function allows a user to map a value from one of the previous modules instead of selecting a Bot from the dropdown list. For example, to dynamically define which bot has to be triggered based on the conditions fulfilled or not in the previous apps of the flow. If there are any input variables configured for the bot in your Automation Anywhere account, they would be shown in the app when you select the bot. Users can either enter the data manually or use the output values from the previous apps. |
Other
You can make API calls using the following module.
Make an API Call
Performs an arbitrary authorized API call.
Connection | |
URL | Enter a path relative to |
Method | Select the HTTP method you want to use: GET to retrieve information for an entry. POST to create a new entry. PUT to update/replace an existing entry. PATCH to make a partial entry update. DELETE to delete an entry. |
Headers | Enter the desired request headers. You don't have to add authorization headers; we already did that for you. |
Query String | Enter the request query string. |
Body | Enter the request query string. |
Example of Use - List Device Pools
The following API call returns the device pools from your Automation Anywhere (Cloud) account:
URL
/v2/devices/pools/list
Method
POST
Matches of the search can be found in the module's Output under Bundle > Body > list.
In our example, 1 device pool is returned: