Script Management
The Scripts tab in the Web Automation module is where you manage all your recorded automation scripts.
Scripts List
The scripts list displays all your automation scripts in a sortable, searchable table:
| Column | Description |
|---|---|
| Name | Script name. Click to open the script editor. |
| Status | Active, Draft, or Inactive. |
| Category | Classification (General, Authentication, Navigation, Form Filling, etc.) |
| Tags | Custom tags for filtering and organization. |
| Steps | Total number of actions in the script. |
| Executions | How many times the script has been run. |
| Modified | Last modification date. |
Filtering and Search
- Search — Filter scripts by name using the search bar.
- Sort — Click column headers to sort ascending or descending.
- Pagination — Navigate through pages for large script collections.
Script Actions
| Action | Description |
|---|---|
| Execute | Run the script. If it has required input variables, you'll be prompted for values. |
| Clone | Create a copy of the script with a new name. |
| Edit | Open the script in the editor to modify actions, variables, and settings. |
| Delete | Remove the script permanently. |
| Bulk Delete | Select multiple scripts and delete them at once. Backed by a bulk-delete API that performs a soft delete (scripts are marked inactive rather than erased). |
Script Editor
Click on a script to open the editor. The editor lets you modify every aspect of the script.
Script Properties
| Property | Description |
|---|---|
| Name | Display name for the script. |
| Description | Optional description of what the script does. |
| Category | General, Authentication, Navigation, Form Filling, Data Entry, Validation, Smoke Test, Regression. |
| Tags | Comma-separated tags for organization. |
| Target URL | The initial URL the script navigates to when executed. |
| Status | Active (ready to run), Draft (work in progress), Inactive (disabled). |
| Reuse Session | When enabled, the browser session is reused across executions. |
Editing Actions
Each action in the script can be modified:
- Reorder — Drag and drop actions to change their sequence.
- Edit — Expand an action to modify its properties:
- Action type — interaction actions like
click,input,select, andlaunch(see Action Reference for what every action needs and an example), plus verification actions (verifydata,verifyorder,verifymedia,verifylayout,verifylinks,sortandverify) and web scraping actions (extractpagedata,extractstructureddata,capturenetwork,crawl,sparoute,randomselect) — see Verification & Web Scraping Actions. - Value — The input text, URL, or wait duration.
- Identifiers — Priority-ordered list of element selectors (XPath, CSS, ID, Name, aria-label). The execution engine tries each identifier in order until one matches.
- Optional — Mark as optional so execution continues if the element is not found.
- Wait Before — Delay in milliseconds before executing this action.
- Timeout — Maximum time to wait for the element (default: 30 seconds).
- Iframe — Configure nested iframe targeting if the element is inside an iframe. Available for element actions and for conditional-check actions, when the condition's element is inside an iframe.
- Action type — interaction actions like
- Clone — Duplicate an action within the script.
- Delete — Remove an action from the script.
- Add — Insert a new action manually at any position.
Input Variables
Input variables make scripts reusable across different environments or datasets:
- Click Add Variable in the script editor.
- Define the variable: name, default value, and whether it's required.
- Reference the variable in action values using
{{variableName}}syntax. - When executing the script, the user is prompted to provide values for all required variables.
Example: A login script might define {{username}} and {{password}} variables so the same script works for different test accounts.
You can also define input variables directly in the extension while recording — More (...) → Input Variables in the control box. Useful in demo mode, where there's no script editor yet.
Capture Variables
Extract text from a page during execution and use it in subsequent actions:
- Select an action and add a capture variable.
- Define the variable name and optional processing rules:
substring(start, end)— Extract a portion of the text.trim— Remove leading and trailing whitespace.replace(pattern, replacement)— Replace text.regex(pattern)— Extract text matching a regular expression.
- The captured value is available for use in later actions via
{{variableName}}.
Conditional Blocks
Conditional blocks recorded with the extension are fully editable in the script editor:
| Condition Type | Behavior |
|---|---|
| IF | Execute nested actions only if the target element exists on the page. |
| IF-NOT | Execute nested actions only if the target element does NOT exist. |
| MULTI-IF | Evaluate multiple conditions combined with AND/OR operators. |
Each condition block starts with a conditionalcheck action and ends with an endcondition action. Actions between them are nested and only execute when the condition is met.
Script Categories
| Category | Typical Use |
|---|---|
| General | Default category for uncategorized scripts. |
| Authentication | Login flows, SSO, MFA testing. |
| Navigation | Page routing and menu interaction scripts. |
| Form Filling | Data entry and form submission automation. |
| Data Entry | Bulk data input across multiple fields or pages. |
| Validation | Verifying that page content or form data meets expected values. |
| Smoke Test | Quick checks that critical features work after deployment. |
| Regression | Comprehensive test scripts run against each release. |
Import / Export Scripts
Scripts can be exported to a file and re-imported, which makes it easy to back them up or move them between environments.
- Export — Export selected scripts or all scripts to a file. Both JSON and CSV formats are supported.
- Import — Upload a previously exported JSON file to re-create the scripts. Import never overwrites an existing script: when an imported name clashes with an existing one, a timestamp is appended to the imported script's name so both are kept.
Next Steps
- Action Reference — What each action needs, and a worked example
- Verification & Web Scraping Actions — Add verify and scraping actions to a script
- Execution & Monitoring — Run scripts and monitor results in real-time
- Recording Guide — Record new scripts with the browser extension