Automa: Visual Browser Automation With a Workflow Marketplace Built Into the Extension
Hook
While Selenium and Puppeteer dominate enterprise automation, a Vue-based browser extension with 21,000 GitHub stars is quietly enabling non-developers to build complex workflows—and even compile them into standalone Chrome extensions.
Context
Browser automation has traditionally been the domain of developers wielding Selenium WebDriver or Puppeteer scripts. Need to scrape product listings daily? Write a Node.js script. Want to auto-fill forms across multiple sites? Build a custom extension or maintain brittle bookmarklets. This barrier meant repetitive web tasks remained manual for most users, while developers spent hours on automation that should take minutes.
Automa reimagines browser automation as a visual programming environment accessible through a browser extension. Instead of writing code, users connect functional blocks—such as form fillers, element clickers, data scrapers, and screenshot takers—into directed graphs that execute as workflows. The project’s AGPL license keeps it open-source while a commercial option enables monetization. What sets Automa apart isn’t just its no-code interface: it’s the marketplace for sharing workflows and the Chrome Extension Builder that packages workflows into distributable extensions without requiring recipients to install Automa itself.
Technical Insight
Automa’s architecture appears to split browser extension responsibilities across multiple components: a background worker for orchestration, content scripts likely for DOM manipulation, and a Vue-powered dashboard for workflow design. The visual workflow builder stores workflows as structured data where each node represents a functional block with configurable parameters and connections defining execution flow.
When a workflow executes, the system interprets the workflow structure, traversing nodes based on connections and conditional logic. For web page interactions, it likely injects content scripts that interact with the DOM. The workflow system supports variables that can reference data throughout execution, enabling dynamic automation.
The Vue frontend provides the drag-and-drop workflow builder, rendering nodes and edges for visual workflow construction. Cross-browser compatibility requires separate builds for Chrome and Firefox, as evidenced by the distinct dev:firefox and build:firefox scripts in the project setup. This reflects API differences between Chrome’s Manifest V3 and Firefox’s extension architecture.
The Chrome Extension Builder feature takes an Automa workflow and generates a standalone extension package. The generated extension appears to embed a runtime that executes the workflow without the full Automa UI. This allows distributing automations to users who don’t have Automa installed—imagine packaging a “Fill Our Company Forms” extension for your team or a “Daily Price Scraper” tool for clients. The builder essentially compiles the visual workflow into a deployable artifact, bridging the gap between no-code design and traditional extension distribution.
Automa’s block architecture appears extensible for advanced use cases. The extension likely stores workflows locally using browser storage mechanisms. Scheduling functionality enables workflows to execute at specified intervals, enabling automated periodic tasks without external infrastructure.
Gotcha
Automa inherits browser extension sandbox constraints that create hard limits on automation capabilities. Unlike headless browsers, it cannot access the file system directly (though it can trigger downloads and read uploaded files), cannot run in CI/CD pipelines without a visible browser instance, and depends on the browser’s lifecycle—close all browser windows and scheduled workflows won’t run. These aren’t bugs; they’re architectural boundaries of browser extensions.
The AGPL license is a double-edged sword. While it keeps the code open and prevents proprietary forks, it requires any derivative work to also be AGPL-licensed. If you modify Automa’s code for internal corporate use and distribute it to employees, technically you’re creating a derivative work that must be open-sourced. The commercial license option exists precisely for organizations that need to embed or modify Automa without open-sourcing their changes, but this adds licensing complexity.
The visual workflow paradigm also degrades for complex automation. Loops, error handling, and sophisticated conditional logic may be possible but can become difficult to manage visually at scale. Workflows with many blocks can be harder to debug than equivalent code with proper function decomposition and version control. Automa excels at straightforward task automation but may struggle as a replacement for programmatic tools when logic complexity increases.
Verdict
Use Automa if you need accessible browser automation for repetitive web tasks—form filling, periodic data scraping, screenshot generation, or scheduled page interactions—especially when sharing workflows with non-technical users or building simple automations without writing code. The marketplace accelerates common tasks, and the Chrome Extension Builder enables distributing automations as standalone extensions. It’s ideal for small teams, power users, and workflows with moderate complexity.
Skip Automa if you need headless execution for CI/CD, programmatic control over complex logic, automation that runs server-side without browser overhead, or the ability to fork and modify the codebase for proprietary use without purchasing a commercial license. In those scenarios, reach for Playwright, Puppeteer, or Selenium with code-based workflows that provide full programmatic control, debugging capabilities, and execution environments unconstrained by browser extension sandboxes.
