Resources · Make integration

Automation Anywhere (Cloud) Make integrationAutomate Automation Anywhere (Cloud) with Make.

What if your bots started on their own when the right event happens in another app? The Automation Anywhere (Cloud) Make integration gives you 2 action modules, Trigger a Bot and Make an API Call. This guide shows how to link your Control Room and build a first scenario step by step.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Automation Anywhere (Cloud) integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Automation Anywhere (Cloud) Make integration do?

It lets Make start your Automation Anywhere bots for you. Make runs a scenario (the automation you build, a chain of modules), and one module of that chain asks your Control Room to launch a bot. The event that starts everything comes from another app or from a schedule you set in Make.

A bot that answers a form. A lead fills in a web form, a module of the form app picks it up, and Trigger a Bot starts the bot that keys the data into your back-office tool. Nobody has to open the Control Room.

A bot on a timer, set in Make. Set the schedule on the first module of the scenario and let Trigger a Bot launch the same bot each time the scenario runs. The default schedule of a new scenario is every 15 minutes.

The API calls the listed module skips. Make an API Call reaches any endpoint of the Automation Anywhere API with the connection you already set up, so a scenario can go further than launching bots.

One limit to know before you start: the app is reserved for the Make Enterprise plan. Check the Make pricing page to see where that plan sits. Automation Anywhere may also be available as an n8n node; the n8n vs Make comparison helps you pick a platform, and the Make training covers scenario building from scratch.

Connect

How do you connect Automation Anywhere (Cloud) to Make?

  1. 01

    Add a module and open the connection form

    In a scenario, add a module from the Automation Anywhere (Cloud) app, then click Add next to the Connection field. A connection is your account linked to Make once, then reused by every module of the app.

  2. 02

    Name it and point to your Control Room

    Type a label in Connection name. In Control Room URL, paste the address you use to reach Automation Anywhere, in the http://<domain>.my.automationanywhere.digital format, then enter your login in Username.

  3. 03

    Pick how to authenticate

    In Authentication Method, choose between an API key and your account password, fill in the matching value, and click Continue. The connection now shows up in the module, ready for every other scenario.

First scenario

Your first scenario: start a bot when another app sends new data

GoalWhen a new entry arrives in another app, Make launches your Automation Anywhere (Cloud) bot with Trigger a Bot.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since this app has no trigger, that first module comes from the app where the event happens.

  2. 02

    Add the starting app

    Search the app that holds the new entries, a form tool or a spreadsheet for instance, pick its module and create its connection. Each item it returns becomes a bundle, one record handed to the next module.

  3. 03

    Add Trigger a Bot

    Click the + on the right of the first module, search Automation Anywhere (Cloud) and choose Trigger a Bot. Select the connection you created and fill the module fields, mapping data from the first module where you need it.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can confirm the bot really started before anything goes live.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each run of a module on a bundle counts as one operation on your plan.

Modules

What can Make do with Automation Anywhere (Cloud)?

Automation Anywhere (Cloud) gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Automation Anywhere (Cloud)1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module sends your own request to the Automation Anywhere API and reuses the connection you already created, so there is no second login to manage.

When to use it
the action you need is not covered by Trigger a Bot, and you know which endpoint of the API does the job.
Watch out
this page cannot tell you which endpoints exist, so keep the API documentation open while you set it up.
Automation Anywhere (Cloud)2

Trigger a Bot

Action

In Make“Triggers a configured bot from Automation Anywhere.”

You get a bot that starts by itself: this action tells your Control Room to launch a bot you already configured in Automation Anywhere, at the exact step of the scenario where you place it.

When to use it
a record lands in another app and a bot should process it right after, with no one clicking in the Control Room.
Watch out
the bot must already be configured in Automation Anywhere; Make launches it, it does not build it.
Need help

Need help automating Automation Anywhere (Cloud) with Make?

A person reads every message.

FAQ

Automation Anywhere (Cloud) and Make: common questions

01Is the Automation Anywhere (Cloud) Make integration free?
No. The Automation Anywhere (Cloud) app is reserved for the Make Enterprise plan, so the Free plan cannot use it. The Free plan still gives you 2 active scenarios with a 15 minute minimum interval, which is enough to learn the editor with standard apps, and 3,000+ standard apps are open on every plan. Enterprise apps like this one need the Enterprise plan before the modules become usable in a scenario.
02What do you need to connect Automation Anywhere (Cloud) to Make?
You need access to your Control Room and one way to authenticate. The connection form asks for a connection name, the URL of your own Control Room, the address you open in your browser, your username, and an authentication method: either an API key or your account password. Once saved, the same connection serves both modules of the app, and the documentation lists no other prerequisite for the account or the app.
03Does Automation Anywhere (Cloud) trigger Make scenarios in real time?
No, because the app has no trigger module in Make. Its 2 modules are actions. To start a scenario anyway, open it with a module from another app, such as a form or a spreadsheet, or rely on the schedule of the first module, every 15 minutes by default. Make can also start a scenario when an app calls it through a webhook, then pass the data to Trigger a Bot.
04What if the Automation Anywhere (Cloud) module you need is missing in Make?
Use Make an API Call. It lets a scenario call any endpoint of the Automation Anywhere API with the connection you already set up, which covers what Trigger a Bot does not. You need to know which endpoint does the job, since the Make listing only names two modules and says nothing about the endpoints themselves. Keep in mind the app itself stays limited to the Enterprise plan whatever module you pick.
05Should you use Make or n8n with Automation Anywhere (Cloud)?
It depends on the platform your team already runs. On Make, the app gives you Trigger a Bot plus Make an API Call, and it requires the Enterprise plan. Automation Anywhere may also exist as an n8n node, so check what that node offers against your needs. Compare the modules available on each side for the bots you want to launch, then choose the tool your team is ready to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations