let a bot fill a web form up to the review screen
the venue wants the same stall details again, but this time the form asks for watts. let a bot copy the answers you already approved into its own browser.
tell it to stop at unfamiliar units, declarations or the final button. you settle the exceptions while you can still see the fields.

the routine
pick an application you can review before it goes through. confirm how the site saves entries first.
paste this into a chat with your bot
each monday at 10, look for a row marked ready in my stalls sheet. use the first ready row only. ask me to confirm it hasn't already gone through. open its venue link on your own desktop. enter approved answers only where the field, unit and event date match. skip blanks. if a next button might send the application, stop there.
show me what you entered and what needs an answer. stop before declarations, uploads, signatures, payment or submission. don't start a second copy. if the site saves entries as you type and i haven't approved that, stop before typing.- when
- mondays at 10 am when the stall coordinator is available
- needs
- an approved row in google sheets, read only access and the bot's own browser
what comes back looks like this (an example, not a real inbox)
example field review
curtis | saturday craft stall | frontage 3 metres entered
power draw | blank | sheet says 'one socket', form asks for watts
trader declaration | untouched | coordinator needs to read and signdecide what can safely go in the boxes
reuse answers only where the question still means the same thing. “stall frontage” and “total floor area” can both look like size fields. keep the form label, value and unit together. include the event date so last year's insurance details don't slip in.
move from the sheet to the form
keep the source row open beside the work.
take over at the point of commitment
you make the declaration and press submit. take control to handle a sign-in, captcha or two-step code. hand control back when the form is ready.2 if the site blocks automation, finish it manually.
choose ordinary browser autofill for a simple address form. dusk bot makes sense when you have several differently worded questions to match.
the guard rails
- confirm whether typing creates a saved draft. use a blank practice form if the site's behavior is unclear.
- keep passwords, payment details and signatures out of the answer sheet. enter them yourself when needed.
- read only applies to the sheets connection. watch what the bot types into the website separately.
- for connected-app sends, dusk asks first by default.2 browser forms still need a clear stopping point.
what it looks like
an invented application for a weekend market
before
curtis has a three-metre stand and asks for a socket. the venue wants frontage in metres, total watts and the trader's signature.after the bot
frontage goes in as 3. the bot leaves watts blank. curtis reads the appliance label, enters the correct draw and signs after reviewing the venue terms.an illustration with made-up names and numbers.
try it in 2 minutes
- choose a permitted practice form
- prepare a sheet row with one exact match and one missing value
- watch the bot fill the match and stop at the gap
mistakes people make
treating a required box as permission to guess
leave it blank and quote the full question. a required field still needs a true answer.
starting again after a timeout
look for an existing draft or receipt first. the site may already hold the entry.
what it could save you
about 5 minutes on a familiar form if these timings fit
9 minutes reading and typing by hand
- 4 minutes supervising and reviewing the filled form
= 5 minutes per applicationa rough estimate. it assumes:
- time yourself on the same form version
- include corrections, takeovers and time spent preparing the sheet
- include the final review under both methods
questions
can i give it a verification code in chat?
enter the code yourself with take control. that also lets you see which account and site requested it.
what if there is no final review screen?
choose an earlier stopping point with a clear boundary. if the first field commits the entry, fill that form yourself.
sources
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].
a google sheets bot that flags low stock by row
prepare a client onboarding brief before kickoff
an ai agent that controls a computer for you
watch the unit price on items you reorder
claude connectors: connect the job you actually need
add new records to the end of a google sheets table