Robovue
Start free
Menu

Automation Anywhere monitoring without changing a single bot.

Robovue signs in to your Control Room with an API key and reads its job activity every 3 minutes. Your team hears by email, or in Slack on the Team plan, when an automation fails or doesn’t run, alongside every other platform you use. You connect it yourself, with no sales call and no enterprise contract.

Start free See the three steps
Your Control RoomRobovue checks it every 3 minutes

Your automations this morning

Example
  • Supplier onboardingExpected 06:00Didn’t run
  • Purchase order entryFailed at 07:03Failed
  • Claims intakeCompleted at 07:30On time
  • Email to your team · 06:05Supplier onboarding didn’t run at 06:00.
  • Slack on the Team plan, #rpa-alerts · 06:05Supplier onboarding (Automation Anywhere) didn’t run.
An example morning: Robovue reads your Control Room’s job activity, and the 06:00 automation that never started reaches your team.

What Robovue watches

Every job the Control Room records becomes a run on the bot’s page, and a schedule on the bot catches the automations that never start.

  • Every job’s outcome. A running job shows as running. One that completes is a success; one that fails, is aborted or errors is a failure.
  • Automations that don’t happen. Give the bot a schedule and Robovue says “Didn’t run” when its time passes with no job.
  • One bot per automation. Each is named after the automation, with an owner, tags and a credential expiry date.
  • Alerts that don’t depend on the Control Room. Robovue sends them itself, so a problem with the Control Room’s own notifications can’t silence them.

Connect it in three steps

Nothing to add to your bots and no request to build: Robovue makes the requests.

  1. Open Automation Anywhere in Connections

    Start free, then a workspace Admin enters the Control Room’s address, a username and that user’s API key.

  2. Robovue checks the sign-in

    It tries the sign-in before saving and saves nothing the Control Room turns down. The key is never shown again.

  3. Run any automation

    On Robovue’s next check of your Control Room, every 3 minutes, the Automation Anywhere page shows it arrive, or says what went wrong when Robovue checked.

ExampleWhat step 3 shows in the app

Before the first run

Nothing has arrived yet.

This step checks again every 30 seconds.

Once a check has found a run

Connected. The last run was recorded at 07:30.

What it needs

A Control Room on the internet
Reachable over HTTPS at a public address. Robovue won’t connect to a private or local one.
A user with an API key
Robovue signs in as that user to read job activity. One Control Room per workspace.
Runs from now on
Only jobs that start after you connect are imported. Nothing earlier is copied across.
Checked every 3 minutes
Robovue reads your Control Room’s job activity on a schedule, so a run appears within a few minutes of starting.

Hear about the next failed automation first.

No card and no sales call. Connect your Control Room in a few minutes.

Start free See pricing