Download controlled fixtures
The application monitors Chrome while downloading CSV, text, and JSON samples, then retrieves the complete local path for each task.
DIALOG-FREE UPLOAD
Automate File Uploads Without a System File Dialog
Assign downloaded files directly to browser inputs, submit them through CDP, and verify the uploaded file count without automating a fragile operating-system dialog.
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.
- Download public sample fixtures and retrieve their actual local paths.
- Populate upload metadata through CDP silent browser commands.
- Assign one primary file and multiple supporting files directly to HTML file inputs.
- Submit the form and read both the upload status and verified file count.
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.
Enter upload metadata
Project ID and description use CDP silent input, while the document type is selected by visible option text.
Locate native file inputs
CSS selectors identify the primary and multiple-file inputs directly in the page DOM.
Assign files without opening a dialog
Runavelo passes the resolved paths to the webpage upload command. No Windows file chooser appears and no coordinate-based desktop interaction is required.
Submit and verify
A CDP silent click submits the form. The workflow reads the upload status and verified count so success is based on page evidence.
EXPECTED OUTPUT
Evidence you can inspect after the run.
- A submitted demo record containing one primary file and two supporting files.
- Runtime logs showing all downloaded fixture paths before upload.
- A visible upload status and verified file count read back from the page.
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.
Will the Windows file picker appear?
No. The webpage upload command assigns approved local paths directly to the HTML file input, so the workflow does not automate the operating-system file chooser.
Can I upload files created earlier in the workflow?
Yes. Pass the output path returned by a download, spreadsheet, document, or file-processing step into the upload command.
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.