Exploring Automa: A No‑Code Chrome Extension for Web UI Automation

This article reviews the Automa Chrome extension, detailing its installation, main interface, workflow creation, core actions, logging, and plugin utilities, while evaluating its strengths and limitations for automating repetitive web tasks without writing code.

FunTester
FunTester
FunTester
Exploring Automa: A No‑Code Chrome Extension for Web UI Automation

Installation

Automa can be installed from the Chrome Web Store at https://chrome.google.com/webstore/detail/automa/infppggnoaenmfagbfknfkancpbljcca or via alternative methods described in the GitHub repository https://github.com/Kholid060/automa.

Home Page Overview

Automa home page
Automa home page

The main interface contains three tabs:

Home

Workflow – lists each workflow (called a “case”) with its name, a run button, and the last‑edit timestamp.

History – shows execution records ordered from newest to oldest.

Workflow Management

Automa workflow interface
Automa workflow interface

Workflows can be created, exported, imported, and deleted through a simple CRUD interface.

Core Workspace

Automa core workspace
Automa core workspace

The left‑hand editor groups actions into four categories:

General actions : start, delay, repeat, export data.

Browser actions : open new tab, back, forward, close tab, screenshot.

Web page actions : click element, get text, scroll, follow link, get attribute, submit form.

Logic actions : conditional checks, existence verification.

Plugin Features

Automa plugin utilities
Automa plugin utilities

The search bar lets users locate specific workflows. A selector tool, accessed via a button that mimics the Chrome DevTools element picker, displays the CSS selector of the chosen element; the selector can be copied to create new actions.

Automa element selector demonstration
Automa element selector demonstration

Stability Considerations

Basic browser actions (opening tabs, navigation, screenshots) work reliably. More complex web‑element interactions, such as clicking dynamic video thumbnails on sites like Bilibili, may fail, indicating that the element‑interaction layer can be unstable in certain scenarios.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Chrome ExtensionNo-codeUI testingWeb AutomationAutoma
FunTester
Written by

FunTester

10k followers, 1k articles | completely useless

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.