Create a Workflow

A workflow is a set of steps (nodes) connected together.

Each step does one thing, like:

Get text from the page
Click a button
Fill a form field
Clean or format the data
Send the result somewhere

How to build a new workflow

Click the Agentic WorkFlow icon in your browser.
Click Add Workflow. This opens a single wizard with three steps:
1. Source — choose how you want to start: Template (browse a curated gallery of ready-made templates), Blank (start empty, triggered or lambda), Marketplace (browse and install a community-published workflow, with its permissions shown before you install), or Import (load a workflow from a .awf file or a URL).
2. Choose — pick the specific template, marketplace listing, or file/URL for the source you selected (skipped for Blank).
3. Details — name your workflow, add an optional description, and pick where it’s saved (this defaults to your storage preference; anonymous users save to Local).
Click Create, then Add first step… on the canvas.
Search for a node you want (for example Get Selected Text) and add it.
Click the node to open its settings and choose the options you want.
Add more nodes and connect them.
To test, open the page you want to automate, then click Execute Workflow.
Click each node to see its output.

When you open a template (or any pre-wired workflow) for the first time, the editor shows a checklist of what’s missing before you can run it — such as a credential to connect or a required field to fill in. Fix each item from the checklist, then click Run once everything is ready.

You can automate tasks such as:

Extracting page content
Interacting with forms or elements
Processing data with AI
Branching logic or loops
Combining browser and external data

If you’re new, try the Quick Intro Tutorial first to experiment with basic browser nodes.

Run workflows manually vs automatically

Manual execution

Best for testing, or when you want to decide exactly when to run:

Open the page you want to automate.
Open the extension and choose your workflow.
Click Execute Workflow.
Nodes will run in order using the current page state.

After a run finishes, the canvas shows what actually happened in plain words — not raw logs. On success, you get the real-world effect of the run (for example, “Sent to #general”) plus a link to verify it yourself. On failure, you get the plain-language cause and one concrete next action to try, with the option to show technical details if you need them.

Automatic execution (future feature)

If your workflow starts with a trigger node, it can start automatically.

Examples:

Start when a page loads
Start on a schedule
Start when you click a built-in button

To learn more about triggers, see When Started and Schedule Trigger.

Even when you use triggers, manual runs are still useful for testing.

Execution context and limitations

Workflows run in the page you currently view, so they see real-time content and page structure.
Because they run inside the browser, workflows are subject to browser security rules (e.g. cross-origin constraints).
Very large workflows or heavy processing may hit browser performance limits (memory, CPU).
Workflows are saved locally in your extension — they persist across browser sessions. You can export/import workflows to share or back them up.

Tips for building reliable workflows

Add nodes gradually. Test often instead of building everything at once.
Use If / conditional nodes to manage different paths.
In each node, inspect results to understand what data you have.
Use meaningful names or notes for nodes — this helps you and others read the flow.
Start with small exported examples or existing workflows to learn patterns and best practices.