Skip to content
Agentic Workflowdocs
v0.8.2Install free

releases

Browser automation, loops and new ways to start a workflow

UI Automation, the Loop node, form tooling, structured extraction, new triggers and Show Notification.

v0.4.0 Chrome Breaking changes & migration

New 5

  • Nodes UI Automation clicks, types, submits and waits for elements. UI Automation
  • Nodes The Loop node runs the same steps for each item. Loop
  • Nodes Form Fill fills a page form from your data. Form Fill
  • Nodes Page Load, Context Menu, Browser Startup and Schedule triggers. Schedule
  • Nodes Show Notification reports a result without opening the builder. Show Notification

Improved 1

  • Workflows Workflow node limits per plan, and size limits on uploaded text. Rate limits

UI Automation adds browser interaction steps for workflows that need to do more than read page content. Use it when a workflow must click, type, submit, wait for page elements, or manipulate visible elements before extracting data.

Relevant docs:

The Loop node makes repeated processing a first-class workflow pattern. Use it when each item, row, link, or page result needs the same downstream steps. Keep the loop body focused and inspect item output before adding browser actions inside the loop.

Relevant docs:

Delete Elements supports workflows that need to clean up a page before reading or displaying content. This is useful when overlays, banners, cookie notices, or repeated elements get in the way of extraction or screenshots.

Relevant docs:

Get Forms Schema helps a workflow inspect forms before attempting to fill them. It gives downstream nodes a structured view of the page form, which is easier to reason about than raw HTML.

Relevant docs:

Form Fill adds a higher-level form automation step. Use it after the workflow has enough structured data to decide what values belong in each field.

Relevant docs:

Structured data extraction improves page-reading workflows that need machine-readable facts instead of plain text. Use it when downstream nodes need fields, entities, metadata, or embedded schema values.

Relevant docs:

This release added a group of new node implementations across the browser and workflow palette. The practical effect is a broader set of ready-made steps, especially around page inspection, UI manipulation, triggers, and data display.

Relevant docs:

New trigger nodes expand the ways a workflow can start. This makes it easier to run automations from page load, browser startup, context menu actions, schedules, or manual execution.

Relevant docs:

Show Notification lets a workflow report a result without requiring the user to inspect the builder. Use it for completion messages, reminders, extracted values, or warnings when a workflow branch needs attention.

Relevant docs:

Workflow node limits help keep runs within the active user plan and prevent workflows from growing beyond supported execution boundaries. If a workflow hits a limit, split it into smaller workflows or simplify repeated sections.

Relevant docs:

Uploaded text size limits protect browser performance and AI calls from oversized input. For AI workflows, send the smallest relevant text instead of full pages or large documents.

Relevant docs:

Ask Aria