PixieBrix Docs
CommunityTemplates
  • Welcome to PixieBrix!
  • Quick Start
    • Productivity Enthusiasts
    • Mod Developer
    • Team Member
    • Enterprise Admin
  • Activating Mods
    • Linking Your PixieBrix Account
    • Using the Marketplace
      • Finding Mods
      • Activating From the Marketplace
    • Activating Your Assigned Mods
    • Updating Mods
    • Troubleshooting
  • Developing Mods
    • Building Your First Mod
    • Developer Concepts
      • Types of Mods
        • Context Menu Item
        • Button
          • Troubleshooting Buttons
        • Sidebar Panel
        • Trigger
          • Working with Custom Events
        • Quick Bar Action
        • What Are URL Match Patterns?
      • Text Template Guide
        • Basic Text Templates
        • Transforming Data with Filters
        • Writing Conditional Statements
        • Template Examples
      • Using Bricks
        • Brick Input Data Types
        • Bricks for Scraping Data
          • Retrieving Attributes from Elements
        • Bricks for Interacting with the DOM
        • Bricks for AI
          • Passing Custom Data to an LLM
      • Data Context
        • Types of Variables
        • Using Mod Variables
        • Using Page State (Advanced)
        • Referencing Variables
      • User Input
        • Show a Modal or Sidebar Form
        • Prompt for Input
      • Working With APIs
        • API Providers
        • Encoding URL Parts
        • Selecting and Transforming API Results
      • Working with Markdown
      • Control Flow
        • Conditional Field on Bricks
        • Control Flow Bricks
          • When to Use Control Flow Bricks
          • Control Flow Brick Output
          • Raising Exceptions/Errors
          • FAQs
      • Transforming Data
        • Using JQ in PixieBrix
        • Using JavaScript in PixieBrix
      • Building Interfaces
        • Understanding the Preview Panel
        • Styling Elements
        • Adding Advanced Elements
        • Custom Themes/CSS
      • Advanced: Brick Runtime
    • Customizing Existing Mods
    • Sharing Mods
      • Packaging a Mod
      • Exposing Activation-Time Mod Options
      • Sharing a Mod With Your Team
      • Updating Published Mods
    • Troubleshooting
    • Mod Development Best Practices
    • Advanced: Workshop
  • Platform Overview
    • Page Editor
      • Open the Page Editor
      • Page Editor Components
        • Mod Listing Panel
        • Brick Actions Panel
        • Brick Configuration Panel
        • Data Panel
    • Admin Console
      • Campaigns
    • Extension Console
  • Managing Teams
    • Creating a Team
    • Inviting Members
    • Access Control
      • Roles
      • Groups
    • Managing Team Integrations
    • Assigning Mods
    • Billing
    • Advanced: Isolating Development, Test, and Production Environments
  • Deploying Mods
    • Deployment Keys
  • Integrations
    • Configuring Integrations
    • Integration Scenarios
    • Embed Web Apps via IFrames
    • Integrate with Desktop Apps via Custom URL Schemes
    • Airtable
    • Atlassian
    • Automation Anywhere
      • Configure Automation Anywhere Integration in PixieBrix
      • Embedding the Automation Co-Pilot
      • Running AA Bots via Control Room
      • Creating AARI Requests
      • Enhancing AARI Table Fields
      • Enhancing AARI Forms
      • AARI Extensions Enterprise IT Setup Guide
        • Point PixieBrix Extension to Staging AuthConfig App
      • Create a Control Room Certificate on Windows
    • Google Drive
      • Creating Google Drive Integration
      • Google Drive Bricks
      • Migrating from Google Sheet to Google Drive Integration
      • Reactivating Your Google Sheet Mods
      • Troubleshooting Google Integration Errors
      • Sheety: Sharing Google Sheets without Google Workspace
      • [LEGACY] Configure Google Sheets Integration
      • [LEGACY] Adding a Google Sheet to Mod Input
    • Guru
    • Hunter.io
    • HTTP Basic Authentication
    • Microsoft
      • Connect to Custom Azure Applications/APIs
      • Add a Power BI chart to the Sidebar
      • Microsoft Power Automate
      • Microsoft Office
        • Microsoft OneDrive / Files
        • Microsoft Excel
        • Microsoft Sharepoint
        • Microsoft Teams
        • FAQs & Troubleshooting
    • Notion
      • Public (OAuth2)
      • Internal (API Token)
    • OAuth2 Client Credentials
    • Ollama
    • OpenAI/ChatGPT
    • Pipedrive
    • Retool
      • Embed a Retool App
      • Trigger Retool Workflows
    • Robocorp Control Room Integration
    • Salesforce
    • SerpAPI
    • ServiceNow
    • Slack
    • Streamlit
    • Trello
      • Configure Trello integration
      • Find board and list IDs in Trello
    • UiPath
      • Running unattended bots via UiPath Cloud Orchestrator
      • Embed a UiPath App
      • Running local bots via UiPath Assistant
    • Val Town
    • Zapier
    • Zendesk
    • Advanced: Custom Integrations
  • Storing Data with Team Databases
  • Enterprise IT Setup
    • Authentication
      • Enabling Login with Microsoft
      • Enabling Login with Google
      • Setting Up SAML/SSO
    • Browser Extension Installation and Configuration
      • Browser Extension Installation Policy
        • Google Workspace Policy
        • Windows Group Policy/ADMX
        • Windows Registry
        • Citrix Profile Configuration
        • Advanced: Create a Windows Installer EXE
      • Browser Extension Configuration Policy
        • Extension Authentication Configuration
        • Microsoft Edge Mini Menu Configuration
        • Microphone and Audio Capture Configuration
        • Extension Logo Configuration
        • Managed Storage Schema
      • Browser Extension Security
    • Network/Email Firewall Configuration
    • Custom Branding and Themes
    • Security and Compliance
    • Performance
    • Version Control and Backups
    • Web Application Platform Configuration
    • Enterprise Troubleshooting
  • Developer API
    • Service Accounts
    • Making an API Request
    • Team Management APIs
    • Package Management APIs
    • Deployment APIs
    • Database APIs
    • Health Check APIs
    • OpenAPI Specification
    • Deprecated Resources
  • How To
    • Installing the PixieBrix Chrome Browser Extension
    • Changing the Quick Bar Shortcut
    • Pinning the Chrome Extension
    • Updating the Browser Extension
    • Installing a PixieBrix Pre-Release Build
    • Editing Pages with iFrames
    • Adding bricks to mods
    • Opening the PixieBrix Sidebar
    • Troubleshooting
      • Troubleshooting Bad API Requests
      • Troubleshooting Network Errors
      • Troubleshooting IndexedDB Errors
      • Troubleshooting Browser Extension Performance and Crashes
      • Troubleshooting extension corruption errors
  • Release Notes
    • 🏗️Release 2.3.0
    • ✅Release 2.2.10
    • 📜Release Notes Archive
      • ✅Release 2.2.9
      • ✅Release 2.2.8
      • ✅Release 2.2.7
      • ✅Release 2.2.6
      • ✅Release 2.2.5
      • ✅Release 2.2.4
      • ✅Release 2.2.3
      • ✅Release 2.2.2
      • ✅Release 2.2.1
      • ✅Release 2.2.0
      • ✅Release 2.1.7
      • ❌Release 2.1.6
      • ✅Release 2.1.5
      • ✅Release 2.1.4 (Hotfix)
      • ✅Release 2.1.3
      • ✅Release 2.1.2
      • ✅Release 2.1.1
      • ✅Release 2.1.0
      • ✅Release 2.0.7
      • ✅Release 2.0.6
      • ✅Release 2.0.5
      • ✅Release 2.0.4
      • ✅Release 2.0.3
      • ✅Release 2.0.2
      • ✅Release 2.0.1 (Hotfix)
      • ✅Release 2.0.0
      • PixieBrix Browser Extension 2.0.0 Migration Guide
      • ✅Release 1.8.14
      • ✅Release 1.8.13
      • ✅Release 1.8.12
      • ✅Release 1.8.11
      • ✅Release 1.8.10
      • ✅Release 1.8.9
      • ✅Release 1.8.8
      • ✅Release 1.8.7
      • ✅Release 1.8.6
      • ✅Release 1.8.5
      • ✅Release 1.8.4
      • ✅Release 1.8.3
      • ✅Release 1.8.2
      • ✅Release 1.8.1
      • ✅Release 1.8.0
      • ✅Release 1.7.41
      • ✅Release 1.7.40
      • ✅Release 1.7.39
      • ✅Release 1.7.38
      • 🚫Release 1.7.37
      • ✅Release 1.7.36
      • ✅Release 1.7.35
      • ✅Release 1.7.34
      • ✅Release 1.7.33
      • ✅Release 1.7.32
      • 🚫Release 1.7.31
      • ✅Release 1.7.30
      • ✅Release 1.7.29
      • ✅Release 1.7.28
      • ✅Release 1.7.27
      • ✅Release 1.7.26
      • ✅Release 1.7.25
      • ✅Release 1.7.24
      • ✅Release 1.7.23
      • ✅Release 1.7.22
      • ✅Release 1.7.21
      • ✅Release 1.7.20
      • ✅Release 1.7.19
      • ✅Release 1.7.18
      • ✅Release 1.7.17
      • ✅Release 1.7.16
      • ✅Release 1.7.15
      • ✅Release 1.7.14
      • ✅Release 1.7.13
      • ✅Release 1.7.12
      • ✅Release 1.7.11
      • ✅Release 1.7.10
      • ✅Release 1.7.9
      • ✅Release 1.7.8
      • ✅Release 1.7.7
      • ✅Release 1.7.6
      • 🚫Release 1.7.5
      • ✅Release 1.7.4
      • ✅Release 1.7.3
      • ✅Release 1.7.2
      • ✅Release 1.7.1
      • ✅Release 1.7.0
      • ✅Release 1.6.4
      • ✅Release 1.6.3
      • ✅Release 1.6.2
      • ✅Release 1.6.1
      • ✅Release 1.6.0
      • ✅Release 1.5.11
      • ✅Release 1.5.10
      • ✅Release 1.5.9
      • ✅Release 1.5.8
      • ✅Release 1.5.7
      • ✅Release 1.5.6
      • ✅Release 1.5.5
      • ✅Release 1.5.4
      • ✅Release 1.5.3
      • ✅Release 1.5.2
      • ✅Release 1.5.1
      • ✅Release 1.5.0
      • ✅Release 1.4.12
      • ✅Release 1.4.11
      • ✅Release 1.4.10
      • ✅Release 1.4.9
      • ✅Release 1.4.8
      • ✅Release 1.4.7
      • ✅Release 1.4.6
      • 🚫Release 1.4.5
      • ✅Release 1.4.4
      • 🚫Release 1.4.3
      • 🚫Release 1.4.2
      • ✅Release 1.4.1
      • ✅Release 1.4.0
      • 🚫Release 1.3.2
      • ✅Release 1.3.1
      • ✅Release 1.3.0
      • ✅Release 1.2.11
      • ✅Release 1.2.10
      • ✅Release 1.2.9
      • ✅Release 1.2.8
      • ✅Release 1.2.7
      • ✅Release 1.2.5
      • ✅Release 1.2.4
      • ✅Release 1.2.3
      • ✅Release 1.2.2
      • ✅Release 1.2.1
      • ✅Release 1.2.0
      • ✅Release 1.1.12
      • ✅Release 1.1.11
      • ✅Release 1.1.10
      • ✅Release 1.1.9
      • ✅Release 1.1.8
      • ✅Release: 1.1.7
      • ✅Release: 1.1.6
      • ✅Release: 1.1.5
      • ✅Release: 1.1.4
      • ✅Release: 1.1.3
      • ✅Release: 1.1.2
      • ✅Release: 1.1.1
      • ✅Release: 1.1.0
      • ✅Release: 1.0.3
      • ✅Release: 1.0.2
      • ✅Release: 1.0.1
      • ✅Release: 1.0.0
      • ✅Release: 0.2.2
      • ✅Release: 0.2.1
  • Tutorials
    • Developer Tutorials
      • Beginner
        • Search Yelp Reviews from OpenTable
        • Right-click Currency Conversion
        • Web Highlighter Tutorial
        • Trello Status Sidebar
        • Right-click Google Scholar Search
        • Google Dorking
        • Tweet a Link
        • Ask AI To Generate a LinkedIn Connection Request
        • How to Customize the AI Rate and Fix Mod
        • Right-click Translate Language
        • Basic Translation Tutorial
        • AI Bot Sidebar
        • Search and Highlight Words on a Page
      • Intermediate
        • Create a status nudge button in Github
Powered by GitBook
On this page
  • Overview
  • Data Flow / Architecture Diagram
  • Networking/Firewall Rules
  • Chrome Browser Extension Distribution
  • Authentication
  • Security Resources
  • Frequently Asked Questions

Was this helpful?

  1. Integrations
  2. Automation Anywhere

AARI Extensions Enterprise IT Setup Guide

Information on setting up Automation Anywhere Automation Co-Pilot

PreviousEnhancing AARI FormsNextPoint PixieBrix Extension to Staging AuthConfig App

Last updated 2 months ago

Was this helpful?

Overview

This guide is intended for Enterprise IT Administrators provisioning AARI Extensions within their organization.

The Automation Anywhere Automation Co-Pilot documentation can be found at

AARI Extensions have been renamed Automation Co-Pilot Extensions. This documentation page will be updated to reflect the name change

There are three scenarios for deploying AARI Extensions. Each are covered by your AARI license.

The "Lite" Integration is the fastest way to get started. We recommend to starting with the "Lite" integration for building prototypes and demonstrating the business case.

Scenario
Overview
Benefits
Limitations

"Full" Integration The most comprehensive integration

  • The Control Room is used as the source of truth for users and extension entitlement

  • Server-server link between PixieBrix and Control Room

  • Manage users and entitlements in Control Room

  • Automatic authentication with SAML/SSO

  • Requires SAML/SSO to use AuthConfig App

  • More initial setup — AuthConfig App and server-server link

  • Requires allowlisting traffic from PixieBrix to your Control Room

"Lite" Integration The best way to build initial prototypes fast

  • Users are managed both in PixieBrix and the Control Room — no server-server link

  • PixieBrix is used as the source of truth for extension entitlement

  • End-user configures password or API credential for browser extension API calls

  • Less IT infrastructure setup — no server-server link is created

  • Available without SAML/SSO

  • End-users must configure password or API credentials for extension API calls

  • Users cannot be logged into the Control Room Web Interface and make Control Room API calls at the same time

Co-Pilot Widget Sidebar Integration The easiest way to embed Automation Co-Pilot on any site at scale Introduced July 2024

  • Extension fetches the Automation Co-Pilot sidebar and data mapping definitions

  • No server-server link required

  • Central shared secret management

  • No additional end-user account management in PixieBrix

  • Can only embed the Co-Pilot widget and define data mappings

  • Mods cannot make direct API/Bot Task calls to the Control Room

Data Flow / Architecture Diagram

System Components

  • Automation Anywhere Control Room: source of truth for user entitlements, Process Requests, Bot Tasks, and API Tasks

  • PixieBrix: source of truth for Automation Co-Pilot Extension definitions. Hosted on Salesforce Heroku (in the United States) and utilizes Cloudflare as a Content Delivery Network (CDN)

  • /: OAuth2 client authentication between the browser and the Control Room

  • : browser extension application error telemetry. Datadog is out-of-band from PixieBrix to facilitate service disruption detection and response

Data Categories

  • Automation Co-Pilot Extension Definitions: define where and how the extension operates on a page. Similar to a Automation Anywhere Bot definition that instructs what steps for a bot to take when executed on a machine.

  • Automation Co-Pilot Extension Metadata: available Automation Co-Pilot extension metadata, e.g., name and version

  • User Entitlements: Automation Co-Pilot assignments for a user

  • Browser Extension Application Error Telemetry: user information (browser version, IP address, team id, browser extension version) and error information (error message, error type, code version, code stack trace, timestamp). Does not include page content.

Data Flows for "Full" Integration

  • Outgoing connections from the Browser to:

    • Automation Anywhere Control Room: Co-pilot Widget, Bot/API Task Deployment API, other Control Room API calls

    • PixieBrix: Browser requests Automation Co-Pilot Extension Definitions and sends business telemetry to surface in Admin Console (errors, usage of each extension), receives Co-Pilot Extension Definitions. Browsing data is not transferred to PixieBrix

    • Auth0: OAuth2 PKCE authentication flow to obtain JSON Web Token (JWT) for calls to PixieBrix and Automation Anywhere Control Room

    • Websites/SaaS: user accesses via browser as usual

    • Datadog: browser extension application error telemetry. Browsing data is not transferred to Datadog

  • Outgoing connections from PixieBrix to:

    • Automation Anywhere Control Room: PixieBrix pushes Automation Co-Pilot Extension metadata, and requests user entitlement information. The Control Room responds with user entitlements

    • Datadog: application error and security telemetry

  • Outgoing connections from the Control Room to:

    • PixieBrix: there are no outgoing connections from the Control Room to PixieBrix

    • 3rd Party APIs: API Task calls

Data Flows for Co-Pilot Widget Sidebar Integration

  • Outgoing connections from the Browser to:

    • Automation Anywhere Control Room: Co-pilot Widget (served in iframe)

    • PixieBrix: Browser requests Automation Co-Pilot Extension Definitions and sends business telemetry to surface in Admin Console (errors, usage of each extension), receives Co-Pilot Extension Definitions. Browsing data is not transferred to PixieBrix

    • Websites/SaaS: user accesses via browser as usual

    • Datadog: browser extension application error telemetry. Browsing data is not transferred to Datadog

  • Outgoing connections from PixieBrix to:

    • Datadog: application error and security telemetry

Networking/Firewall Rules

Outbound Hostnames from the Browser

Outbound hosts to allowlist from client devices:

  • Automation Anywhere Control Room host

  • app.pixiebrix.com: PixieBrix package registry

  • https://*.browser-intake-datadoghq.com: error telemetry

  • fonts.gstatic.com: font content delivery network

For more information, see Network/Email Firewall Configuration.

Inbound On-Premise Control Room Firewall Rules

The PixieBrix Web Service makes API calls to the Control Room API for syncing permissions and AARI Extensions. If you’re running your Control Room behind a firewall (e.g. inside a Virtual Private Cloud or on-premise), the firewall may block inbound traffic from the PixieBrix Web Service, causing the Control Room connection to fail:

To enable the connection from PixieBrix to your Control Room, you’ll need to allowlist incoming traffic from the PixieBrix server in your firewall configuration.

PixieBrix static outbound IP addresses and ports for the Control Room link:

The PixieBrix platform provides a load-balanced pair of outgoing IP addresses for the server-server Control Room connection. If one IP fails, traffic will automatically route through the second IP using automated failover:

Troubleshooting Connection Issues

  • Ensure the DNS record you provide is for a publicly accessible destination. If the DNS record is for a private IP address on your network (e.g., starting 192.X.X.X or 172.X.X.X), the PixieBrix server will not be able to connect to your Control Room

  • Ensure your firewall policy is set to allow incoming HTTPS traffic from the above IP addresses

Chrome Browser Extension Distribution

For detailed information on provisioning the Chrome Browser Extension to your organization, see: Browser Extension Installation and Configuration

Browser Support

AARI Extensions officially supports the latest two versions of the Chrome Web Browser.

Browser Extension Installation

Force install browser extension via Google Workspace, Group Policy, or your Enterprise Device Management policy:

  • Display Name: PixieBrix

  • Chrome Web Store ID: mpjjildhmpddojocokjkgmlkkkfjnepo

Browser Extension Managed Storage Configuration

Enterprise Browser Extensions are configured using Chrome’s managed storage feature. For end-users, set the following extension properties:

Name
Type
Value
Purpose

managedOrganizationId

REG_SZ (string)

The UUID of the PixieBrix tenant

Enforces association with a particular PixieBrix tenant

partnerId

REG_SZ (string)

automation-anywhere

Applies Automation Anywhere branding and enforces Control Room authentication

controlRoomUrl

REG_SZ (string)

URL (including scheme) of the Control Room to connect to

Pre-fills the controlRoomUrl for connecting the Automation Anywhere

Locating the UUID of the PixieBrix tenant

The UUID of the PixieBrix tenant is in the URL path when the team is selected:

The team UUID in the URL

Windows

On Windows, use the registry to set the properties for the extension:

HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Google\\Chrome\\3rdparty\\extensions\\mpjjildhmpddojocokjkgmlkkkfjnepo\\policy

Authentication

The initial AARI Extensions setup requires the Admin to login via Google, Microsoft, or email. After the initial setup, AARI users will login with Automation Anywhere using Automation Anywhere OAuth2 services support.

Admin Login for Initial Setup:

  • Login with Google: see Enabling Login with Google

  • Login with Microsoft: see Enabling Login with Microsoft

  • Login with Email (aka Magic Link): see Network/Email Firewall Configuration

Login with Automation Anywhere Control Room

Security Resources

Additional security information on the Chrome Browser Extension is available here: Security and Compliance

Frequently Asked Questions

Does PixieBrix work with on-premise Control Rooms?

Yes, PixieBrix works with cloud and on-premise Control Rooms. For the "Full" Integration, the only requirement is that incoming traffic from the PixieBrix service IPs can be allowlisted. See the Data Flow / Architecture DiagramandNetworking/Firewall Rules sections above.

My Control Room is on an intranet (e.g., accessed via IP address 192.168.XX.XXX). Do we need to allow incoming public traffic to use Automation Co-Pilot extensions?

For the "Full" Integration, you must allowlist incoming traffic from the PixieBrix service IPs. See the Data Flow / Architecture Diagram andNetworking/Firewall Rules sections above.

If you are using a hostname for your Control Room, ensure the DNS records are accessible.

Is an outgoing internet connection from the browser required for using PixieBrix with Automation Anywhere Business Co-Pilot?

Yes, an outgoing internet connection is required for two reasons:

  • An external internet connection is required to request extension definitions from the PixieBrix service, which is hosted on Heroku Salesforce (in the United States) and uses Cloudflare's Content Delivery Network (CDN)

See the Data Flow / Architecture DiagramandNetworking/Firewall Rules sections above.

Does PixieBrix offer a fixed IP address for outgoing traffic from the browser to PixieBrix?

No, because PixieBrix uses Cloudflare as a Content Delivery Network (CDN), there is no fixed IP address for outgoing traffic from the browser to the PixieBrix web service.

Why is the whitelisting of PixieBrix URLs required (e.g., app.pixiebrix.com)?

In the Automation Co-Pilot solution, the PixieBrix server acts as the source of truth for the extension definitions. The browser must be able to access the PixieBrix service to fetch Automation Co-Pilot Extension definitions.

Why is the "Lite" Integration easier to allowlist than the "Full" Integration?

The "Full" integration requires a server-server link integration initiated by the PixieBrix server (hosted on Amazon Web Services). Enabling the link requires allowlisting incoming traffic to the Control Room from PixieBrix's static IP addresses (see Networking/Firewall Rules).

Firewalls distinguish between incoming vs. outgoing traffic. IT security teams generally apply stricter policies to incoming traffic (i.e., traffic initiated from an external source). The "Lite" integration requires less setup/approvals because in the "Lite" integration, there is:

  • No server-server link

  • The only traffic with PixieBrix is initiated from the end-user’s browser (outgoing)

Does PixieBrix need permissions to "Read and Change all your data on all websites"?

PixieBrix does not read/change data on websites unless you've activated a mod that performs those reads/changes data on a website.

You can prevent PixieBrix from having access to certain pages by setting the runtime_blocked_hosts and/or runtime_allowed_hosts policies in your extension configuration. See Browser Extension Securityfor more details.

Do Automation Co-Pilot Extensions work on Microsoft Edge?

When a mod is created, where does PixieBrix store the code and data?

PixieBrix store team mod and brick definitions in your team's Package Registry. The Package Registry is hosted in the United State on Salesforce Heroku (backed by Amazon Web Services) and encrypted with AES-256 block-level encryption.

Similar to programming languages, you should avoid hard-coding secrets/credentials in definitions. Instead use PixieBrix's Integrations feature (see Integration Scenarios).

By default, PixieBrix does not transmit or store browsing data from the device. PixieBrix only transmits data if you activate a mod that uses an Integration and/or our Team Database.

What kind of information is going out to PixieBrix?

See the Data Categories section for the information transmitted by the PixieBrix browser extension and service.

What kind of information is coming in from PixieBrix?

See the Data Categoriessection for the information transmitted by the PixieBrix browser extension and service.

What kind of controls does PixieBrix have on transmitted and stored data?

Who has admin access to PixieBrix?

For teams, PixieBrix makes available Role-Based Access Control (RBAC) and Group-Based Access Control (GBAC). For more information, see Access Control. The PixieBrix support team can advise on configuring PixieBrix in a way that is consistent with your security goals.

What kind of controls does Automation Anywhere have on PixieBrix?

Teams using the "Full" Integration between PixieBrix and Automation Anywhere control end-user mod entitlements via their Control Room.

Automation Anywhere does not have access to the PixieBrix service or infrastructure.

Browser authenticates API calls

A shared secret is set on the browser extension. See

OAuth2 Authentication:, the JWT is used for the browser extension to authenticate with the Automation Anywhere Control Room and the PixieBrix service

SAML Configuration:

For a full list of PixieBrix's service providers, see our

Automation Anywhere Auth Config App: to

For a full list of PixieBrix's service providers, see our

https://*.cloudflare-ech.com : Cloudflare . Read more about

Firewall, port, and protocol requirements for Automation Anywhere deployment: .

AARI Extensions is also known to work on Microsoft Edge for most use cases. To confirm support for your use case, email

See in the Automation Anywhere documentation portal for how to set up Login with Automation Anywhere

Our and are available publicly.

For a copy of our SOC 2 Type 2 report audited by (or other reports, e.g., Independent Penetration Test), please contact .

An external internet connection is required to use

Chrome shows this permission prompt on installation from the Chrome Web Store because PixieBrix utilizes Chrome's tabs and webNavigation API to .

The PixieBrix extension is source-available. You can .

Automation Co-Pilot Extensions are also known to work on Microsoft Edge for most use cases. To confirm support for your use case, email .

PixieBrix's controls are audited for the SOC 2 Type 2 trust criteria of Security, Confidentiality, and Availability. For a complete list of audited technical controls, request a copy of our SOC 2 Type 2 report from .

For a public summary of our controls, see our .

PixieBrix follows the Principle of Least Privilege. Platform admin access is restricted to members of our platform team that require access for site reliability. For a copy of our System Access Control policy, contact .

Automation Co-Pilot using Chrome extension
Automation Anywhere AuthConfig App
Auth0
Datadog
OAuth2 PKCE authentication to obtain JWT
SAML registration token to set up OAuth2 services
Privacy Policy
set up OAuth2 services
Privacy Policy
Encrypted Client Hello (ECH) endpoint
ECH for security here
Automation 360 Ports, protocols, and firewall requirements
3.222.129.4:9294
54.205.35.75:9294
[email protected]
Use AuthConfig App to enable OAuth2 services
Security and Compliance Overview
Privacy and Security Policies
A-LIGN
[email protected]
Automation Anywhere OAuth2 services
detect page navigation in Single Page Applications (SPAs)
view/audit the code on GitHub
[email protected]
[email protected]
Security and compliance overview
[email protected]
Deployment Keys
using Automation Anywhere OAuth2 Services
Automation Co-Pilot Extensions Data Flow Diagram for "Full" Integration
Automation Co-Pilot Extensions Data Flow Diagram for Co-Pilot Widget Sidebar Integration
Error message displayed during setup if the Control Room is not accessible