PROJECT

Create Chrome Extension for Browser Automation and Custom Workflows

Custom software development, Chrome extension development, Browser automation, Workflow automation, Web-data extraction, Cross-browser compatibility, Business-system integrations

  • Industry: Software development
  • Estonia Location: Estonia
  • Delivery time: 10 weeks
  • Technologies: PHP, JavaScript / TypeScript (Node.js)
3 months

This client is a software development company from Estonia, and browser work costs its team time when repetitive actions, webpage data collection, and extension maintenance require manual effort. The software is a custom Chrome extension that takes workflow settings and web content. It gives the team automated tasks and extracted text.

Summary

Problem

The client spends time fixing browser extensions and repeating navigation, form, scrolling, and data collection tasks.

Solution

The solution became a custom Chrome extension with configurable workflows and browser automation. It also includes data extraction, testing, and compatibility tools.

Result

The software is designed to reduce manual work, repeated fixes, and rework related to extension updates.

Client story

The client is an Estonian software development company. It works with browser-based products, automation, web data collection, and business system integrations.

After loading failures, recurring errors, browser updates, and compatibility issues, its team was spending time maintaining extensions.

The request was straightforward: fix extension failures, automate browser interactions, support modern extension standards, and provide working versions with documentation.

Automation system was built as a modular Chrome extension with workflow configuration, an automation runner, web page data extraction, and a maintenance dashboard. The design also included testing, package creation, browser compatibility, and integration status.

The client wanted

  1. Fix extension errors, loading failures, compatibility issues, recurring errors, and update-related problems.
  2. Automate navigation, clicks, forms, scrolling, tasks, and web data collection.
  3. Support Manifest V3, Chrome APIs, content scripts, browser APIs, and web standards.
  4. Test, package, document, and deliver versions with source code and installation instructions.

Why ready-made software was not suitable

Ready-made browsers provide access to web information, but their extensions do not offer the combination of workflow configuration, browser automation, and web page data extraction this client needed. The solution was developed to combine these functions in one extension with client-specific behavior, integrations, and support.

Project overview

The solution was developed around a clear extension setup screen. It combines the extension name, status, and workflow settings.

A browser automation runner was provided for recurring browser actions. It displays the task queue and current action status while the extension moves through pages, clicks controls, and fills out forms.

A separate screen was created for web page data extraction. The extension previews page content, extracts selected text, displays the extraction status, and saves the result to a local file.

The dashboard brings loading issues, browser compatibility, and integration status together in one view.

It also provides testing scenarios and package status.

The solution was built in modules so new forms, automations, integrations, or browser support could be added later. Delivery included testing, package creation, documentation, and installation instructions.

Key features delivered

  • Configurable Chrome extension workflows
  • Browser navigation, clicks, forms, and scrolling
  • Task queue with execution status and logs
  • Web page text extraction and export to a local file
  • Manifest V3 and Chrome API support
  • Browser permissions summary
  • Loading and recurring error overview
  • Multi-browser compatibility monitoring
  • Integration status monitoring
  • Version creation, packaging, and documentation controls

Can be added

+ Connected API and webhook workflows + CRM, email, cloud, or internal system integrations + OAuth access + Randomized clicks for automation tasks + Accessibility improvements + Chrome Web Store publishing + Firefox, Edge, and Safari support

Who else can use this solution

These businesses have a similar browser-automation task, and the same solution can be adapted to their workflows.

An organization automating repetitive browser tasks

Task It needs to navigate pages, complete forms, run tasks, and collect web data.
How the solution helps The extension brings these browser actions into configurable automated workflows.

A company integrating browser tools with internal systems

Task It needs browser activity to exchange information with CRM, email, cloud, or internal platforms.
How the solution helps The solution connects extension workflows with APIs, databases, webhooks, and business platforms.

A product team maintaining browser extensions

Task It needs to review loading failures, compatibility issues, browser updates, and recurring errors.
How the solution helps The maintenance dashboard organizes compatibility, testing, integrations, and build-package status.

Technology stack

PHP

Protocol client language

PHP is the language of the Chrome DevTools Protocol client used in this project.

JavaScript / TypeScript (Node.js)

Extension and interface logic

JavaScript and TypeScript power browser functions, interfaces, configuration, and integration logic.

Python

API and configuration services

Python supports API connections and structured configuration processing.

jakubkulhan/chrome-devtools-protocol

Chrome browser control

jakubkulhan/chrome-devtools-protocol (a PHP client for Chrome DevTools Protocol) connects the software with Chrome automation.

jsonify

JSON browser handling

jsonify (a JavaScript library for working with JSON) handles browser configuration data without changing global objects.

seld/jsonlint

JSON validation

seld/jsonlint (a PHP JSON linter) checks configuration and integration data for valid JSON.

notion-client

Notion API connection

notion-client (a Python client for the official Notion API) connects workflows with Notion when required.

react

User interface library

react is a JavaScript library for building user interfaces.

webpack

Browser bundle packaging

webpack packages the extension code into browser-ready bundles.

Manifest V3

Chrome extension structure

Manifest V3 defines the extension configuration, permissions, and browser integration.

Integrations

Chrome

The extension connects to Chrome through Manifest V3, Chrome extension APIs, browser APIs, and the Chrome DevTools Protocol.

Notion

When required, the workflow exchanges documentation or configuration data with Notion through its official API.

External APIs, databases, and webhooks

The extension sends and receives workflow information through connected APIs, databases, webhooks, or business platforms.

Firefox, Edge, and Safari

The extension can exchange compatible browser packages and behavior across Firefox, Edge, and Safari when cross-browser support is included.

The result

Configure browser work in one place

The extension gives administrators a clear starting point for workflow settings, status, and browser permissions. Configuration is kept close to the functions it controls.

How it works

  1. The screen shows the extension name and status.
  2. The configuration area holds workflow settings and browser permissions.
  3. The extension saves the configuration and provides run controls.
  • Manifest V3 configuration
  • Permission summary
  • Workflow settings
Extension workflow setup

Extension workflow setup

Functions on this screen
Chrome Extension Configuration Create Chrome Extension

Run browser actions with visible status

The automation runner brings repetitive browser actions into a single view. It shows the task queue, current page, and action status.

The screen also shows collected data and the execution log.

How it works

  1. The runner shows the task queue and navigation steps.
  2. The automation flow records clicks, form actions, and scrolling.
  3. The screen updates task results, collected-data status, and the execution log.
  • Task queue
  • Current page and action status
  • Execution log
Browser automation runner

Browser automation runner

Functions on this screen
Browser Automation Tool Automate Project Task Management Connect automation flow

Extract webpage text into a local file

The capture screen turns webpage content into a usable local result. It provides a page-content preview, text-selection controls, extraction status, and local-file export.

How it works

  1. The screen shows the webpage text and content preview.
  2. The extraction module processes selected page content and creates structured extracted content.
  3. The extension reports extraction status and saves the local data file.
  • Webpage text preview
  • Structured extracted content
  • Local data file
Tip: Local export keeps the captured result available outside the browser extension.
Webpage data capture

Webpage data capture

Functions on this screen
Extract website content

Review extension health and compatibility

The maintenance dashboard brings technical checks into one place for the developer. It shows loading and error issues, supported browsers, and API connections.

Test scenarios and package status are also available for extension maintenance.

How it works

  1. The dashboard lists loading issues and recurring errors with supported-browser information.
  2. The integration area shows API connections and the test area shows functional scenarios.
  3. The build controls report package status for the extension.
  • Loading and error list
  • Browser compatibility matrix
  • Test scenario results
Extension maintenance dashboard

Extension maintenance dashboard

Functions on this screen
Debug legacy code Cross-Browser Compatibility

What the solution gives

With this solution, the software development company can:

  • Configure browser workflows and permissions in one extension.
  • Automate navigation, clicks, forms, scrolling, and task execution.
  • Extract webpage text and save it to a local file.
  • Review task status, logs, errors, and compatibility information.
  • Connect browser workflows with APIs, databases, webhooks, and business platforms.
  • Prepare tested, documented, and packaged extension builds.

In the end

In the end, the solution was made to reduce manual work between browser tasks, webpage data, and extension maintenance.

FAQ

Thinking about building a similar system? These answers explain what a custom browser extension can include and how the work is organized.