Concepts

Core Concepts

Core Concepts

GPAL Subsystems

Browsers and applications are only two of the things GPAL automates. Credentials, AI, REST, email, Excel, and file conversion are all separate subsystems reached through the same GPAL factory, using the same fluent pattern you already know.

One Factory, Many Subsystems

Beyond GPAL.Browser and GPAL.Application, the GPAL factory exposes a growing set of subsystems for work that is not browser or desktop interaction at all: GPAL.Credentials and GPAL.CredentialsFor for retrieving logins, GPAL.Ai for classification and other AI tasks, GPAL.RESTClient for HTTP calls, GPAL.Mail for sending email, GPAL.Excel and GPAL.Grid for tabular data, and GPAL.Converter for format conversion. Each follows the same fluent-chain-then-ToGPALObject pattern.

Subsystems Compose

Subsystems are designed to feed each other. A credentials lookup can produce a grid for FillInFrom on a browser. A REST call can carry an access token fetched from credentials. An AI classification can consume text scraped by a browser and write its result to a grid that another subsystem reads. None of this requires leaving the fluent style.

// Credentials feed a browser login

var grid = GPAL.Grid.ToGPALObject();

GPAL.CredentialsFor(CredentialServiceType.LastPass)

.GetCredentialsFor("example.com")

.SaveTo(grid);

browser.WithSelector("#username")

.WithSelector("#password")

.FillInFrom(grid);

// AI consumes scraped text and writes a result grid

GPAL.AI

.WithProvider(AIProviderType.OpenAI)

.WithTask(AITask.Classification)

.WithInputFrom("Great service, fast shipping.")

.WithOutputTo(out var sentiment)

.Execute();

TIP

This page is a map, not a manual. Credentials, AI, REST, Mail, Excel, and Converter each have their own reference section covering every method in detail. For the conceptual side of each subsystem, see Data Operations (GPALFile, GPALConverter, GPALGrid, GPALDatabase, Excel), Form Building (GPALForm and controls), Integrations (Mail, REST, Google Sheets/Drive), and Advanced (AI classification and generation, Google Dorking). Each builds on the fluent pattern introduced here. Automation Targets covers the browser and desktop side this page touches on.

Why Subsystems Matter

Real automation rarely stays inside the browser. Logging in needs credentials, classifying scraped text needs AI, notifying a team needs email, and exporting results needs Excel or a converted file format. GPAL treats all of these as first-class, fluent citizens rather than bolt-on utilities, so a workflow that spans several of them still reads as a single unified sequence.

On this page

Core Concepts
GPAL Subsystems
  • One Factory, Many Subsystems
  • Subsystems Compose
  • Why Subsystems Matter