Quick question
How many times have you typed your email into a form this week?
The hook. Ask it, then wait a beat.A 3-second opener before the first chapter.
Version texte
- Quick question: How many times have you typed your email into a form this week?
Filling out repetitive forms is one of the most soul-crushing tasks on the web. Job applications that ask for your work history after you’ve already uploaded your resume. Support tickets that demand the same account details every single time. Lead forms, onboarding questionnaires, registration flows: the same fields, the same answers, over and over. An AI form filler running in the browser can handle this for you, with an understanding of the form that traditional autofill does not have.
The problem with repetitive forms
A knowledge worker fills out many web forms every week. Each one demands a context switch: find the right information, type or paste it in, reformat it to match the field’s expectations, and submit.
The pattern
Same fields. Same answers. Typed again, every time.
Every time. That repetition is what a workflow removes.Values you type more than once belong in data a workflow can reuse.
Version texte
- The pattern: Same fields. Same answers. Typed again, every time.
It adds up. Here is what a modest habit of forms can cost in a week:
Time spent on forms, per week
1h 35m
About 20 forms a week, a few minutes each. Chiffres d'exemple
Where it goes: finding and typing, mostly.Lookup and typing are what a data node and Form Fill replace.
Version texte
- Time spent on forms, per week: 1h 35m
- Finding the information: 30 min
- Typing and pasting: 35 min
- Fixing formats and errors: 18 min
- Writing free-text answers: 12 min
Beyond the time, manual form-filling introduces errors. A mistyped email address, a wrong date format, a skipped required field: small mistakes with sometimes significant consequences. Automation solves both problems at once.
Why autofill hits a ceiling
Browser autofill and password managers are the most common attempts to solve this problem, and they’re useful as far as they go. But they hit a ceiling fast.
- Browser autofill only handles a fixed set of fields (name, address, credit card). It can’t adapt to custom field labels, multi-step forms, or fields that need a written answer.
- Password managers (1Password, LastPass) extend autofill slightly but are designed for login credentials, not general-purpose form completion.
- RPA tools like UiPath or Automation Anywhere can fill forms programmatically, but they need professional setup and dedicated infrastructure, which is overkill for individual or small-team use. If you’re not a developer, browser automation for non-developers is a more practical starting point.
- Copy-paste libraries save snippets of text but still need manual selection and placement: they organise your clipboard, they don’t fill anything.
Autofill already does this for me.
Autofill matches a few known field types. It cannot read a question like “Why do you want this job?” and answer it.
Flip it. Autofill matches types; it does not read the question.Custom labels, free-text questions and multi-step wizards fall outside the fixed field types.
Version texte
- Autofill already does this for me.
- Autofill matches a few known field types. It cannot read a question like “Why do you want this job?” and answer it.
None of these tools understand the context of a form. They can’t read a label like “Briefly describe your relevant experience” and write a tailored answer. An AI form filler can:
What changes
What an AI form filler adds to autofill
- Reads what each field is asking (fait)AI step
- Writes answers that fit the page (fait)AI step
- Formats dates, phones and limits (fait)AI step
- Pulls values from your own data (fait)AI step
- Waits for your OK before sending (fait)AI step
You approve before anything is typed or sent.Wait For Approval pauses the run until you confirm.
Version texte
- What an AI form filler adds to autofill
- Reads what each field is asking
- Writes answers that fit the page
- Formats dates, phones and limits
- Pulls values from your own data
- Waits for your OK before sending
How it works: the page plus a language model
Agentic Workflow combines two capabilities to make AI form-filling possible: access to the page and LLM reasoning. The browser extension can read every element on a web page, including form labels, input types, placeholder text and field names, even on websites that don’t have an API. It passes that structure to a local or cloud model, which decides what value belongs in each field. The values are then typed into the page, as if you had typed each answer.
The form fills itself. You review, then submit.Form Fill types each value into the field with the matching id.
Version texte
- The form on the page: Name · Email · Why this job?
- Get Forms Schema: 3 fields: name, email, motivation
- Your profile: { name, email, experience }
- AI maps fields to values: motivation → 2 tailored sentences
- Form Fill: 3 fields typed in the page
Because everything runs in the browser, form data does not leave your machine unless you add a node that sends it somewhere. With a local model (WebLLM in the browser, or Ollama on your computer), even the AI step stays on your device.
With a local model, nothing leaves your browser.WebLLM runs the model with WebGPU inside the extension; no network after the download.
Version texte
- Your device: Votre navigateur · The internet: Serveur d’une entreprise d’IA
- Votre navigateur → Serveur d’une entreprise d’IA: the form + your profile
- Serveur d’une entreprise d’IA → Votre navigateur: the values to type
- Aller-retour: ≈ 1,5 s · Quitte votre appareil: oui
- Serveur d’une entreprise d’IA → Your device · Réseau: aucun · Quitte votre appareil: non · Fonctionne hors ligne: oui
Build your AI form-filler, step by step
The quickest start is the docs example Fill Form from JSON. It keeps your values in one node, asks before filling, types each value into the matching field and submits the form. No AI yet: it is the reliable base you add AI to.
Fill Form from JSON
Run it. Each node shows what it did.One run, five nodes, outputs shown per node (example values).
Version texte
- fill-form-from-json.awf
- started from the page
- name, email, message
- approved by you
- 3 fields filled
- form sent
Start it on the form
Open the page with the form and run the workflow from the right-click menu. A Page Load trigger can offer it every time you open that page instead.
Keep your answers in one node
An Edit Fields node holds your profile: name, contact details, background, the answers you give again and again. For job applications you can keep several variants, one per kind of role.
Approve before anything happens
Wait For Approval pauses the run. Nothing is typed until you say yes, so you can check the page first.
Fill each field
Form Fill types each value into the field whose id matches. If you don’t know the ids, run Get Forms Schema once: it lists every field of the form with its id, name and type.
Submit, or leave it to you
Submit Form sends the form. Delete this step if you’d rather review the filled form and press the button yourself.
See every step
Each run shows what every node received and produced, so when a field stays empty you can see why.
Add the AI step
To make the filler understand any form, put an AI step between your data and Form Fill:
- Add Get Forms Schema after the trigger to read the fields of the form on the page.
- Add a Basic LLM Chain with a model (a local Web LLM or a cloud model) and a Structured Output Parser. In the prompt, give it the list of fields, your profile, and ask for a JSON object of field id → value.
- Switch Form Fill to Manual mode and map its values to the model’s output.
This is where the AI reasoning happens: the model works out that “Full Name” is your name, that “LinkedIn URL” is your LinkedIn, and that “Why do you want to work here?” needs a written answer based on the company description it can read on the same page.
Entrées
fieldslistprofileobjectpage texttextRéglages
Sorties
valuesobjectWhat comes out: a value for every field.Form Fill (Manual mode) reads this object as its values.
Version texte
- Map fields to values (AI)
- fields (list), profile (object), page text (text)
- Model: Web LLM · on this device · Prompt: Return a value for each field id · Output: Structured Output Parser (JSON)
- values (object)
Test and refine
Run the workflow on a test form first. Check the filled values and adjust your prompt or profile data as needed. Pay attention to fields with strict formats (dates, phone numbers) and to optional fields you may want to skip. Once it performs reliably, save it and run it with one click whenever you meet that form.
Advanced: AI that understands the whole page
The real power of an AI form filler shows when the model sees the full page, not just the form. For a job application, it can read the job description on the same page and tailor every answer to it. For a support ticket, it can read your previous ticket from a connected data node and keep the case details consistent. A static autofill tool cannot do this.
Minutes saved on every application.Example timings.
Version texte
- Using my profile and the job description on this page, answer: Why do you want to work here? Two sentences.
- I've spent four years building internal tools for support teams, and your focus on making support faster for small shops is exactly the problem I enjoy. Your new self-serve help centre is the kind of project where I can contribute from the first week.
- Writing it yourself: 10 min · AI draft + your edit: 1 min
Where it helps
- Job applications: fill application forms, cover-letter fields, screening questions and availability with answers tailored to each role
- Lead generation forms: fill contact and company information quickly and consistently across many platforms. For outreach at scale, pair this with a strategy for automating LinkedIn prospecting without getting banned
- Support tickets: pre-fill issue descriptions, account details and troubleshooting steps from your own data
- Vendor registrations: onboard to supplier or partner portals without re-entering the same company information every time
- Survey and feedback forms: automate routine internal surveys where your answers are predictable
Petit sondage
Which form would you hand over first?
Résultats d’exempleReveal. (Example results.)Example results, labelled on screen.
Version texte
- Which form would you hand over first?
- Job applications: 34% · Supplier and partner portals: 22% · Support tickets: 26% · Internal surveys: 18%
Try it
Browser autofill was built for a simpler web. Today’s forms are complex, context-dependent and often multi-step. A workflow that reads the form, picks the right value from your data and fills every field in seconds, with you approving first, turns that data entry into one click.
À vous
Start from the form-filler workflow
Open it in AWFlow, put your own values in, match the field ids, then add the AI step.
Ouvrir dans AWFlow (s’ouvre dans un nouvel onglet)docs.awflow.io/examples/fill-form-from-json.awfCall to action. Scan the code or click the link.Opens the Fill Form from JSON docs example in AWFlow's import page.
Version texte
- Start from the form-filler workflow · Open it in AWFlow, put your own values in, match the field ids, then add the AI step. · https://docs.awflow.io/examples/fill-form-from-json.awf
In short
- Autofill matches types, AI reads the question
- Your answers live in one node
- You approve before anything is sent
Three. You stay in control.Wait For Approval before Form Fill and Submit Form.
Version texte
- In short
- Autofill matches types, AI reads the question
- Your answers live in one node
- You approve before anything is sent



