Core nodes
Login, Navigate, and Action — the three building blocks of every flow.
Three node types do the work in most flows: Login establishes who you are, Navigate points the browser at a page, and Action performs the interactions. Everything else — assertions, waits, branches — builds on top of these.
01Login
The Login node sets the user context for the flow. In Flow Designer this step is labelled Acting As — use it anywhere the flow needs to establish or switch the current user.
Pick how the flow authenticates:
- A saved credential — binds the step to one specific account.
- A credential template — resolves the right credential at run time based on the run environment. Use a template when the same flow should run across environments, accounts, or roles without editing the step.
A flow can have more than one Login node. In segmented flows — for example after a Wait — add a Login node to re-establish the browser session before the next steps run.
02Navigate
The Navigate node directs the browser to a specific page. Choose a discovered page or enter a URL.
| Format | Example | Behavior |
|---|---|---|
| Absolute URL | https://app.example.com/settings | Goes to the exact URL |
| Root-relative path | /settings | Uses the run environment's base URL, then opens that path |
| Path with variables or macros | /accounts/$var.account_id/details | Resolves the value at run time, then navigates |
Use root-relative paths so the same flow runs across environments without edits. Use variables or macros when part of the destination changes between runs — type $ in the URL field to insert them. See Variables & macros.
03Action
The Action node performs a single user interaction on the current page. Describe what the user does — for example, "Create a new ticket" — and optionally supply input data. Keep each action focused on one user goal; Designing a good test covers the right granularity.
Inline assertions
An action can carry inline assertions — checks that run right after the action completes, so the verification stays coupled to the step that caused it. See Assertions.
Capturing values
An action can save values from the page for later steps to reuse — referenced as $var.{name}. This is how data flows from one step to the next. See Variables & macros.
AI-generated input values
Action inputs can use AI-generated values directly, so you get realistic one-off data — names, short subjects, simple form entries — without hardcoding a static string.
When you use a generated value, make sure later steps reference the produced value rather than assuming a fixed string.
First-class actions
Some actions run as distinct, reviewable steps in run history instead of being folded into a generic action:
| Action | Use it for |
|---|---|
| Table extraction | Capturing rows and columns from a table so later steps can reference structured results |
| Python execution | Running custom Python logic to transform data or drive follow-up steps |