Begin download monitoring
Monitoring starts before the first click, preventing fast downloads from completing before the workflow records their task identifiers.
BROWSER DOWNLOADS
Download Multiple Files from a Browser List
Search for several invoice records, download the available files, and capture the exact local path of every completed browser download.
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.
- Monitor Chrome downloads before any download link is activated.
- Search invoice identifiers and click the corresponding action through CDP.
- Include an intentionally unavailable record so absence is visible and testable.
- Wait for registered download tasks and print the complete local file path for each result.
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.
Search each invoice ID
A list loop uses CDP silent input to replace the invoice search value and identifies the matching action control.
Activate the available action
The same stable selector resolves to a download link for available invoices or a disabled unavailable control for the negative test case.
Collect browser task identifiers
After the search loop, Runavelo stops monitoring and obtains the download tasks registered during the controlled window.
Wait and report every file
A second loop waits for each task, retrieves its downloaded path, and prints that path to the runtime log.
EXPECTED OUTPUT
Evidence you can inspect after the run.
- CSV files for every available invoice in the sample list.
- A visible status log for both available and unavailable invoice IDs.
- The complete local path returned for each finished browser download.
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.
Can the URL or invoice list come from Excel?
Yes. Replace the included list with rows read from a spreadsheet, while retaining download monitoring and per-file path logging.
Why print the downloaded path?
A later workflow step can move, parse, attach, or archive the file only when it knows where the browser actually saved it.
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.