Open the lookup page
The workflow opens the resettable product lookup lab in Chrome and keeps the resulting webpage object for every subsequent command.
BROWSER + EXCEL
Automate Product Lookups and Export Results to Excel
Turn a list of product identifiers into a structured spreadsheet without copying search results one row at a time.
WHAT THE AI WILL BUILD
A real visual workflow, not a conceptual diagram.
The AI guide supplies a precise goal, safe target page, inputs, output contract, and verification rules. Paste that prompt into Runavelo's built-in assistant, then inspect and edit every generated command before execution.
- Submit several SKU values through the same browser search form with CDP silent input and clicks.
- Read the returned product name, price, and stock from stable CSS-selected elements.
- Preserve missing-price and not-found outcomes instead of terminating the complete batch.
- Write one two-dimensional result table to an Excel workbook without opening Microsoft Excel.
Responsible use: adapt this pattern only for systems and data you are authorized to automate.
WORKFLOW WALKTHROUGH
How the visual workflow operates.
Each stage has a specific input, browser context, output, and verification point. Edit these commands directly when the destination system differs.
Loop through product identifiers
Each SKU replaces the current field value through CDP silent input, then a background CDP click submits the search without taking over the physical mouse or keyboard.
Branch on the visible result
A conditional checks for the not-found message. Successful rows read name, price, and stock; unsuccessful rows receive an explicit status rather than disappearing.
Create a user-relative output path
Runavelo resolves the current Windows Documents folder and creates a Runavelo Demo Results directory, so the application contains no developer-specific path.
Write and report the spreadsheet
The accumulated table is written in one spreadsheet operation. The final log prints the exact workbook path instead of forcing the operator to search for it.
EXPECTED OUTPUT
Evidence you can inspect after the run.
- A workbook named product-lookup-results.xlsx in Documents\Runavelo Demo Results.
- One row per requested SKU, including explicit missing-price and not-found results.
- A runtime log containing the complete output file path for immediate verification.
Runavelo's runtime log connects the visible workflow line to its result. That makes missing elements, rejected updates, and unexpected page states easier to locate than a generic success message.
COMMON QUESTIONS
What to change for a real workflow.
Does this example read its input from Excel?
The downloadable example uses a small embedded list so anyone can run it immediately. In the editor, replace that list with a spreadsheet read step when your source of record is an Excel file.
Does repeat execution require another AI request?
No. After the visual workflow is built and approved, the browser and spreadsheet commands run deterministically without asking a model to rediscover the procedure.
Copy the goal, let AI build, then inspect and run.
The prompt targets the matching test page and states the expected evidence. A reference QYA remains available for comparison with a verified implementation.