Download and resolve the workbook
The workflow starts Chrome download monitoring, clicks the .xlsx fixture through CDP, waits for completion, and retrieves the actual path chosen by the current browser.
EXCEL + WEB FORM + EXCEL
Submit Excel Rows to a Web Form and Save Every Result
Turn a spreadsheet into verified form submissions while preserving the outcome of every row in a separate Excel report.
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 a genuine .xlsx input file and retrieve its complete local path from Chrome.
- Map spreadsheet columns to text, email, select, date, textarea, and checkbox fields.
- Submit each row with CDP silent browser commands and read the visible page response.
- Write the source email and confirmed result to a user-relative Excel output file.
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.
Read spreadsheet rows
A spreadsheet loop skips the header row and exposes each remaining row as a structured list, without embedding a developer-specific file location.
Map every form control
CSS selectors locate the destination fields. Text uses CDP silent input, the department is selected by visible text, the date is assigned through the page DOM, and checkbox state follows the workbook value.
Submit and capture evidence
A CDP silent click submits the form. The workflow reads the live status element after each row and stores that page-confirmed message with the source email.
Save an auditable result workbook
Runavelo resolves the current user Documents directory, writes all outcomes to Excel, closes the workbook, and logs its complete path.
EXPECTED OUTPUT
Evidence you can inspect after the run.
- A workbook named excel-form-results.xlsx in Documents\Runavelo Demo Results.
- One result row for every submitted email address, including the confirmation text read from the page.
- Runtime logs containing both the downloaded input path and the complete output path.
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 the sample use a real Excel file?
Yes. The application downloads and reads an actual .xlsx workbook, then creates a second workbook containing the per-row results.
Can the output include a record ID from the destination system?
Yes. Add a CSS element lookup after submission and append the returned ID to the result row before writing the workbook.
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.