Automation Co-Pilot for Business Users using embedded widget and Chrome extension

Compare the two Automation Co-Pilot delivery methods of embedding automation to decide on the right component for your business needs.

Automation Co-Pilot is a platform for automation to assist business users with common workflows. Users can continue to automate using Automation Co-Pilot in their favorite web applications and CRM platforms, such as the ServiceNow service portal. When you use Automation Co-Pilot using embedded widget to set up your iFrame widget, you can now access Automation Co-Pilot through an embedded widget in your web application and deploy automation, all without the need to leave your environment.

Comparing components

As you explore Automation Co-Pilot using embedded widget and Automation Co-Pilot using Chrome extension, they might seem very similar. They are both solutions that provide your environment with an iFrame widget interface powered by AARI. The iFrame widget hosts automation from AARI on the web, offering the same power of automating with Automation 360.

Either Automation Co-Pilot using embedded widget or using Chrome extension can deliver a method of embedding automation. However, depending on where you aim to embed, one component might better suit your needs over the other.

Simply put, the decision to embed a widget in your environment relies on choosing one of the following methods:

Embedded widget: Add an iFrame widget to the source code of your web application.
Google Chrome extension: Develop custom bricks that are coded into your browser through an extension.

Consider technical specifications and styles of these components.

Automation Co-Pilot using embedded widget

Automation Co-Pilot using embedded widget embeds in web applications as an iFrame widget offering end-users access to automated processes and bots without leaving their environment.

Consider the following prerequisites for using Automation Co-Pilot using embedded widget:

Automation 360 v.26 or later.
Google Chrome, Microsoft Edge Chromium, or Apple Safari web browsers. See Browser requirements for Automation Workspace.
AARI licenses and fluency.
Automation Co-Pilot on the web interface.
Web application that supports the iFrame widget.

For further details on how to start using Automation Co-Pilot using embedded widget, click the image to navigate to the overview topic:

Image example of a widget in Automation Co-Pilot using embedded widget.

Automation Co-Pilot using Chrome extension

Automation Co-Pilot using Chrome extension relies on a Chrome extension of your web browser to embed automation. The widget appears outside the application as an Automation Anywhere stylized panel, as in the following image.

Consider the following prerequisites for using Automation Co-Pilot using Chrome extension:

Automation 360 v.26 or later.
Google Chrome web browser.
AARI licenses and fluency.
OAuth 2.0 Control Room configuration for server validation.

For further details on how to start using Automation Co-Pilot using Chrome extension, click the image to navigate to the overview topic: