The Universal Form Automation Solution
Most form automation needs do not fit neatly into a category like "job applications" or "government forms." You might need to fill out product registrations, survey responses, event sign-ups, vendor onboarding forms, compliance questionnaires, or any of the thousands of web forms that businesses interact with daily. This is the general-purpose form automation workflow that handles any web form on any website.
How AI Form Filling Differs from Auto-Fill
Chrome's built-in auto-fill stores your name and address and pastes them into checkout forms. That covers maybe 5% of real form work. The other 95% — business forms, internal tools, legacy enterprise systems, partner portals — requires understanding form structure, handling conditional logic, uploading documents, and recovering from validation errors.
Autonoly's AI form automation opens a real browser, navigates to the form, reads the field labels the way a person would, fills in the data from your spreadsheet or database, handles the weird date picker, waits for the slow dropdowns, clicks Next on multi-step wizards, and repeats until the confirmation page appears. Then it moves to the next row.
Why Traditional Automation Breaks
Most form automation tools work by recording CSS selectors. You click a field, the tool saves something like #app > div.form-container > div:nth-child(3) > input.MuiInput-root, and next time it tries to find that exact selector. This approach is brittle by design:
CSS selectors are a house of cards. A developer renames a CSS class, wraps a form in a new
div, or upgrades from Material UI v4 to v5, and every recorded selector becomes invalid.Modern frameworks make it worse. React, Angular, and Vue generate DOM dynamically — field IDs change on every render cycle. Shadow DOM in web components creates encapsulated subtrees that traditional selectors cannot pierce.
Bot detection is getting smarter. Cloudflare Turnstile, reCAPTCHA v3, and hCaptcha run behavioral analysis. Scripts that fill fields instantly and in tab order get flagged immediately.
Vision-Based Field Detection
The AI renders the page in a real browser and analyzes the visual layout. It identifies form fields by their labels ("First Name," "Date of Birth," "Upload your resume"), their position relative to other elements, and their visual appearance. This works regardless of the underlying HTML structure.
A field labeled "Full Name" is recognized as a name field whether it is a plain <input>, a Material UI TextField, a Chakra UI Input, a custom web component, or a Salesforce Lightning lightning-input. The AI does not care about the implementation — it reads the label.
Self-Healing When Layouts Change
Because the AI identifies fields by label and context rather than by CSS selector, it naturally adapts when a website updates its layout. If a form redesign moves the "Email" field from the second row to the third row, or wraps it in a new container div, the AI still finds it — because it still says "Email."
This self-healing is not a bolt-on feature. It is the natural consequence of vision-based detection. There is nothing to "heal" because nothing "broke."
All Input Types Supported
The AI handles every form input type you will encounter:
Text inputs — single-line and multi-line, with format detection (email, phone, URL)
Dropdowns — standard HTML
<select>, custom JavaScript dropdowns, searchable dropdowns, and multi-selectCheckboxes and radio buttons — including grouped selections and toggle switches
File uploads — both
<input type="file">and drag-and-drop upload zonesDate pickers — calendar widgets, date input fields, and custom date picker components
Rich text editors — TinyMCE, CKEditor, Quill, and other WYSIWYG editors
Sliders and range inputs — drag to specific values
Color pickers — hex input or visual selection
Signature fields — digital signature pads
Multi-Step Form Navigation
Many forms span multiple pages or steps. The AI navigates through each step:
- Fills all fields on the current page
- Validates that all required fields are complete
- Clicks the Next/Continue button
- Waits for the next page to fully load (including dynamic content)
- Fills the next page and repeats
- On the final page, reviews the summary (if present) and submits
The agent tracks progress through the wizard and can resume from the last completed step if a session timeout or error occurs.
Handling CAPTCHAs
For simple image CAPTCHAs and basic challenge-response prompts, the AI has built-in solving capabilities. For reCAPTCHA v2, the real browser with human-like interaction patterns passes the behavioral analysis in most cases. For difficult CAPTCHAs, two fallback options:
- [Live Browser Control](/features/live-browser-control) — pause and notify you so you can solve it manually
- Third-party solving service — route the challenge to a CAPTCHA-solving API via API & HTTP
Error Recovery
When a form submission fails, the agent follows a specific recovery sequence:
- Read error messages — both inline field errors and page-level error banners
- Identify the failing fields
- Diagnose the cause — format mismatch, missing required field, invalid option
- Apply correction — reformat data, select the closest matching option
- Retry the submission
- Escalate if needed — after two failed retries, flag for human review
Accuracy and Speed Benchmarks
| Form Type | Field Detection Rate | Time per Submission | Notes |
|---|---|---|---|
| Standard HTML forms | 99.2% | 8-15 seconds | Plain inputs, selects, textareas |
| React / Vue / Angular forms | 97.5% | 12-20 seconds | Dynamic IDs but readable labels |
| Shadow DOM / Web Components | 95.4% | 15-30 seconds | Visual detection fallback |
| Legacy enterprise forms | 96.5% | 20-45 seconds | Weird markup but stable layouts |
| Multi-step wizards (3-5 pages) | 95.0% | 1-3 minutes | Includes navigation time |
Cross-Session Memory
When the AI successfully fills a complex form, it remembers the approach — which fields required special handling, what format the date picker expected, whether dropdowns needed a search query or a click-scroll-select sequence. On subsequent runs against the same form, it applies these learned behaviors immediately. The first run might take a few seconds of analysis per field. By the tenth run, the AI handles each field without hesitation.
Setting Up a Form Automation Workflow
Step 1: Prepare your data. Create a spreadsheet with columns matching the form fields, or connect to a Database. Clean your data with Data Processing — normalize phone formats, validate emails, standardize dates.
Step 2: Create the workflow. In the Visual Workflow Builder, add a data source node (Google Sheets, CSV, or database) and a Form Automation node with the target URL.
Step 3: Map fields. The AI auto-detects form fields. Review the mappings and adjust if needed.
Step 4: Test with one row. Run with Live Browser Control to watch the agent fill the form. Catch any issues before batching.
Step 5: Run the batch. Process all rows. Each processes independently — failures do not stop the batch. Review results in the execution log.
Step 6: Schedule if recurring. For forms you fill regularly (weekly reports, monthly filings), use Scheduled Execution to run automatically.
Best Practices
Format your data before it reaches the form. The number one cause of submission failures is data format mismatches. Run dates, phone numbers, and addresses through Data Processing.
Test with Live Browser Control on the first run. One test run saves hours of debugging later.
Do not assume submission succeeded because the button was clicked. Configure verification — check for confirmation pages, success messages, or reference numbers.
Handle CAPTCHAs up front. Discover the CAPTCHA strategy before building the workflow, not at runtime when your batch stops.
Build in delays for rate-limited sites. Add 30-60 seconds between submissions for sensitive portals.
Integration With Other Features
[Data Extraction](/features/data-extraction) — scrape data from one site and submit it as form entries on another
[Database](/features/database) — store form data and submission results for tracking
[Scheduled Execution](/features/scheduled-execution) — automate recurring form submissions
[AI Vision](/features/ai-vision) — handle complex custom widgets that resist standard interaction
[Logic & Flow](/features/logic-flow) — branch workflows based on form responses or submission results
[AI Content](/features/ai-content) — generate free-text answers, product descriptions, and cover letters
[PDF & OCR](/features/pdf-ocr) — extract data from PDFs to feed into form fields
Explore more about the tools and techniques used in this workflow: Automate Form Filling from Excel, No Code Automation Guide, Browser Automation.