Open a controlled form
The application opens the contact-entry lab and retains a webpage object so all selectors and commands operate in the same browser context.
FORM AUTOMATION
Bulk Web Data Entry with an Editable Visual Workflow
Enter structured records into a browser form, verify the saved count, and keep every field and decision visible for review.
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.
- Map structured records to text, email, select, date, notes, and checkbox controls.
- Use CDP silent browser input and clicks rather than physical mouse automation.
- Exercise both selected and unselected checkbox states in a deterministic test.
- Verify the number of saved records from the page after the loop completes.
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.
Iterate through structured records
A list loop supplies first name, last name, email, department, date, notes, and subscription state for each fictional contact.
Locate every field explicitly
Stable CSS selectors identify the corresponding page controls. The workflow comments explain what each selected element represents.
Enter and submit through CDP
Text is replaced with CDP silent input, selects are set by option text, checkbox state is applied deliberately, and the submit control is clicked through CDP.
Read back the saved count
After all records are processed, the workflow reads the visible contact count and prints it to the runtime log as a simple completion assertion.
EXPECTED OUTPUT
Evidence you can inspect after the run.
- Two fictional contact records saved in the resettable demo page.
- A visible contact count read back from the page after submission.
- A runtime log that records the verification value.
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 records come from a spreadsheet?
Yes. The demo keeps the input embedded for reproducibility, but the same loop can consume rows read from Excel or another approved source.
Why use CDP input?
CDP input addresses the browser element directly. It avoids moving the operator's physical mouse and is better suited to background browser work than coordinate-based clicking.
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.