How imgsus/formsbot works
Google Forms Bot automates respondent submissions through the main_fixed.py command-line workflow: it creates respondent rating profiles, opens the configured form in a browser, answers each page, advances or submits, and counts a response only after confirmation. The --inspect path walks the form without submitting; the normal path retries failed submissions and reports verified results. The README documents title-based answers, multi-page navigation, and blocker handling. Excerpts are partial, so the graph omits uncertain internal wiring and treats Google Forms and the browser as external systems.
Main entry points: main_fixed.py Submission runner
Components 14
Run control
- CLI entry
main_fixed.py - Submission runner
main_fixed.py - Rating profiles
main_fixed.py - Inspect mode
main_fixed.py
Form answering
- Page walker
main_fixed.py - Question classifier
main_fixed.py - Answer generation
main_fixed.py - Page navigation
main_fixed.py - Blocker detection
main_fixed.py - Submission verification
main_fixed.py
Browser integration
- Driver setup
main_fixed.py
Other components
- Operator
- Brave browser
- Google Forms
Connections 17
- Operator → CLI entry: runs command
- CLI entry → Inspect mode: dispatches inspect
- CLI entry → Submission runner: starts submissions
- Submission runner → Rating profiles: builds plan
- Submission runner → Driver setup: creates driver
- Submission runner → Blocker detection: checks blockers
- Submission runner → Page walker: walks form
- Submission runner → Submission verification: checks outcome
- Inspect mode → Driver setup: creates driver
- Inspect mode → Blocker detection: checks blockers
- Inspect mode → Page walker: walks without submit
- Page walker → Question classifier: classifies questions
- Page walker → Answer generation: answers page
- Page walker → Page navigation: advances or submits
- Driver setup → Brave browser: controls
- Brave browser → Google Forms: loads and submits
- Submission verification → Brave browser: reads page state