ElementFlow

ElementFlow turns repetitive form-filling into a repeatable workflow. Point at the fields you care about, export a CSV template, fill it with your data, and ElementFlow types each row back into the page for you — including the tricky parts most autofill tools choke on. WHAT IT DOES • Pick fields visually — hover and click the fields on any page; ElementFlow captures a stable selector for each. Each picked field becomes a CSV column. • CSV in, form out — download a template, fill it in your spreadsheet, upload it back, and populate the form. Run a single row or process every row in sequence. • Handles real-world widgets — text inputs, textareas, native and custom dropdowns, radio/checkbox controls, "search and choose" lists, and calendar/date pickers. • Multi-step wizards — build a pipeline of steps with Next/Submit buttons and per-step success/failure detection. Branch to different steps based on your data, and skip or stop on rejected rows. • Run history — see what ran, when, and which rows succeeded or were rejected. • Save, export & import workflows — reuse a setup per site, back it up, or share it as a file. HOW IT WORKS 1. Open the side panel and pick the fields on the page. 2. Download the CSV template and fill it with your data. 3. Upload the CSV and run — ElementFlow fills the form, one row at a time. PRIVATE BY DESIGN ElementFlow has no servers and no analytics. Your workflows, history, and CSV data stay on your device (browser local storage) and are never transmitted. See the privacy policy for details. GOOD FOR Bulk data entry, registering or onboarding lists of records, QA/test data, and any web form you fill over and over. Note: Use ElementFlow only on sites and data you're authorized to automate. It works on standard HTML forms; some apps that render to canvas (e.g. Google Docs document bodies) can't be populated this way. Last changelogs: WHAT'S NEW IN 0.2.0 • ElementFlow is now completely free — no limits, no license key, nothing to buy. • Run a range of rows (2-10), not just one row or all of them. • Stop a run mid-way; test-run a single step while you build. • Tell a step what success or failure looks like by typing the words the page shows — one step can cover several outcomes. • Slow forms: wait after a submit, delay between steps, and a wait for fields that render late, with anything that never appeared reported instead of silently skipped. • Sturdier targeting, so a signal picked on one screen no longer misfires on another.