Questions and answers

What people ask before they connect a bot, answered straight: platforms, alerts, plans and your data. If yours isn’t here, email contact@robovue.co.uk.

Getting started

What is Robovue?

Robovue watches the bots you already run on UiPath, Automation Anywhere, Power Automate and your own code. It tells your team by email, and in Slack on the Team plan, when one fails or doesn’t run at all. Your bots keep running where they are: Robovue never starts, stops or changes them.

How is it different from the alerts my RPA platform already sends?

Each platform’s own tools see only its own bots. Robovue gives one view across all of them, catches runs that never happen as well as failures, and keeps owners, maintenance windows, credential expiry dates and time saved alongside each bot. Its alerts don’t depend on the platform being monitored, so a problem with the platform’s own notifications can’t silence them.

How long does setup take? Do I need to talk to anyone?

No sales call. You sign up, get your workspace’s credentials and connect a platform from the Connections pages, and a Verify step shows your first run arriving. Connecting your first bot takes about ten minutes, without help.

Do I need a card to start?

No. The Free plan needs no card, and neither does the 14-day Team trial.

Do I have to install anything on my bot machines?

No. UiPath Orchestrator and Power Automate send each run to Robovue themselves, and Robovue reads Automation Anywhere’s job activity from your Control Room. Your own bots send one signed HTTPS request, through the .NET or Python SDK or in plain code.

How do I check it’s working before I rely on it?

Every connection has a Verify step: send a request and watch it arrive, or see the exact reason it was turned away. A log shows every request from the last 7 days. Requests from your own code and from Power Automate can also be sent as a dry run, which runs every check and stores nothing.

Platforms

Which platforms does Robovue work with?

UiPath (an Orchestrator webhook), Automation Anywhere (Robovue checks your Control Room), Power Automate (an HTTP action in your flow) and anything else through the HTTP API. See UiPath, Automation Anywhere, Power Automate and custom bots.

Can I monitor Blue Prism, Python scripts or other tools?

Yes, through the HTTP API. Each run report carries a short platform label of your choosing, such as python or blue-prism, so those bots sit alongside the rest of your fleet. There’s no dedicated Blue Prism connector.

Is there an SDK for .NET or Python?

Yes: dotnet add package Robovue.Sdk from NuGet, for .NET Framework 4.6.2 or later and .NET 6 or later, and pip install robovue-sdk from PyPI, for Python 3.9 or later. Each signs every request, retries when the network or Robovue has a problem, checks a report before sending it, and can send dry runs while you set up. Anything else can send the request itself: the app gives it in C#, Python and shell, with a signature checker.

What licence are the SDKs under?

MIT, so you can use, change and ship them freely. The code examples in the app are under MIT-0, so you can paste them into your own code without keeping any notice. Neither licence ends when a subscription does.

My Automation Anywhere Control Room is on-premises. Will it work?

Only if it’s reachable at a public HTTPS address. Robovue won’t connect to private, local or internal addresses. It checks every 3 minutes and imports jobs that start after you connect, not earlier history.

Do I need a Premium licence for Power Automate?

Yes. The HTTP action that reports each run is a Premium connector, so the flow’s owner needs a Power Automate Premium licence.

Can I manage my setup from code?

Yes. A management API covers bots, tags, owners, maintenance windows, alert settings, Slack channels and run history, using the workspace’s management key. People, billing and deleting the workspace stay in the dashboard.

Alerts

What does Robovue alert on?

A bot that’s overdue (no run within its expected interval and grace period) and when it recovers, a run that fails, and runs passing again after failures. A failure can alert on the first one, after several in a row, or when a share of recent runs fail.

Where do alerts go?

By email to the people in your workspace, and to Slack channels on the Team plan and above. Each person can switch off any kind of email alert for themselves. There’s no SMS, other chat app or paging integration.

Are email alerts included on the Free plan?

Yes. Email alerts are on every plan. Slack alerts need Team or above.

Will I get flooded with alerts?

Robovue alerts when something changes, not on every run. An overdue bot sends one alert, then another when it recovers. A failing bot opens one incident and alerts again only when it passes. You can raise the failure threshold for the whole workspace or for one noisy bot.

How do schedules work?

Each bot has an expected interval between runs, from 1 minute to 30 days, and a grace period of up to 7 days. Once the interval passes it reads Late; once the grace passes too, it’s Overdue and alerts. Clock changes never shift a schedule.

Can I stop alerts during planned maintenance?

Yes. A maintenance window covers one bot or every bot with a tag. It holds alerts back but doesn’t cancel them: if a bot is still overdue or failing when the window ends, you’re told then.

Does Robovue warn me when a bot’s credentials are about to expire?

Record the expiry date of the credential a bot uses and Robovue flags the bot for review from 30 days before, then marks it expired. That shows in the dashboard; it doesn’t send an email or Slack alert.

How quickly will I hear about a problem?

Robovue checks for overdue bots and failed runs every minute and alerts as soon as it finds one. A bot’s schedule and grace period decide when a missing run counts as overdue.

Plans and billing

How much does Robovue cost?

Free is £0 for up to 5 bots with 30 days of run history. Team is £29 a month for 25 bots (more in blocks of 25 at £19 a month, up to 200) with 90 days of run history. Business, for unlimited bots with unlimited run history, isn’t open to new workspaces yet: talk to us. Prices are in pounds and include any tax. See pricing for every limit.

Do you charge per person?

No. Every plan has unlimited people, under fair use, priced by bots alone. Admins invite people and manage billing; Members run and configure the bots.

What does fair use mean for people?

A workspace can hold up to 10,000 people, counting invitations not yet accepted, with up to 25 Admins. It can send 5 invites on its first day, then 200 a day on a paid plan or 20 a day without one. Admins and a bot’s owners get every alert email; everyone else gets up to 2,000 alert emails a day between them (UTC), and alerts always show in the dashboard and on Slack. Running extra workspaces to get round these limits isn’t allowed; an agency can still keep one workspace for each client.

What does Team add over Free?

  • 25 bots instead of 5, and more in blocks of 25 up to 200
  • 90 days of run history instead of 30
  • Slack alerts
  • Failure screenshots
  • Hours and money saved, per bot
  • Reports: fleet trends and ROI roll-ups

Can I add bots without changing plan?

On Team, yes. Team includes 25 bots, and an Admin can add more on the Billing page in blocks of 25, at £19 a month each, up to 200 bots. Extra bots are available once the workspace is paying, not during a free trial. A block you add is charged straight away for the rest of the month. A block you remove stops at your next renewal, with no refund or credit, and you keep its bots until then. For more than 200 bots, talk to us about Business.

How does the free trial work?

Each workspace can try Team free for 14 days, once, with no card, as long as it has never paid. When it ends, the workspace goes back to Free and keeps everything it set up. Subscribe during the trial and your first charge waits for the day it would have ended, or pay today and the whole free days you haven’t used come off your first payment.

How do I get Business?

Business isn’t open to new workspaces yet. Talk to us about what you need. It adds unlimited bots and unlimited history, with single sign-on coming soon.

What happens if I go over my plan’s bot limit?

A new bot is turned away at the limit, and Admins are told. If a downgrade leaves you over the limit, every bot keeps alerting for 14 days. After that, only as many bots as the plan includes keep alerting: the ones an Admin picks, or otherwise the longest-standing. The rest keep recording runs, and nothing is deleted.

What happens if I downgrade or cancel?

A cancellation takes effect at the end of the period you’ve paid for, and the workspace moves to Free. Features the smaller plan doesn’t include pause with their settings kept, and come back if you upgrade. Run history older than the new plan keeps is deleted 14 days later. Fees already paid aren’t refunded, apart from the exceptions in our terms.

How do I pay, and who sends the invoice?

Monthly in advance. Link, Stripe’s reseller service, takes the payment: it sends your receipts and invoices, handles any VAT and may charge in your local currency. Changing plan, payment details and cancelling are all in the billing portal in the dashboard.

Data and security

Where is my data stored?

In the UK, in AWS’s London region. Some providers, such as Stripe and Slack, may process data outside the UK; those transfers are protected as UK data protection law requires. The subprocessors page lists them all.

Do you have a data processing agreement?

Yes. The data processing agreement is part of the terms of service, so there’s nothing separate to sign. Admins get 30 days’ notice by email before a new subprocessor is added.

What do my bots send, and how long is it kept?

Whatever your bots report: names, run status and times, error messages, an optional payload of up to 64 KB, and on the Team plan and above a screenshot or log on failed runs. Run history is kept for 30 days on Free, 90 days on Team and with no limit on Business. Screenshots and logs are kept for 30 days, or 7 or 14 if an Admin chooses. Please don’t send special-category personal data or card numbers.

How is my data protected?

It’s encrypted in transit and at rest, and each workspace can read only its own data. Bots authenticate with a key or a signed request that stops working within minutes, and Admins can rotate keys without breaking running bots. If a breach ever affected your data, we’d tell you within 48 hours of finding out.

How do I delete my data?

An Admin can delete a single run from its page, or a bot with all its runs once it’s archived. To delete everything, an Admin can delete the workspace from the Account page. That cancels any subscription at once and removes the workspace’s data and everyone’s sign-in. To ask about your own personal data, email contact@robovue.co.uk.

Do you support single sign-on (SSO)?

Single sign-on is coming soon on Business. Until then, you sign in with an email and password, and Robovue never sees your password.

The service

Who runs Robovue?

Robovue is based in England and registered with the Information Commissioner’s Office. It’s sold to businesses only. The operator’s details are under Who we are in the privacy policy. For help, email contact@robovue.co.uk, or use Send feedback inside the app.

Is there an uptime guarantee?

Plans don’t include a service level agreement. Robovue’s live status is on its status page, checked by an outside service.

The quickest answer is your own first run.

No card and no sales call. Connect a bot and watch it arrive.