How ai-to-ai/auto-gmail-creator works
Project Type and Purpose
• This is a Python‐based automation bot (“Auto‐Gmail‐Creator”) that orchestrates a WebDriver (Chrome or Firefox) to programmatically register bulk Gmail accounts.
• It reads or generates user profiles (CSV), manages proxy settings, invokes an SMS‐verification API (sms-activate.org), and writes out successfully created accounts.
a. Data Layer
• CSV Databases (First_Name_DB.csv, Last_Name_DB.csv, Proxy_DB.csv)
• User Input CSV (user.csv)
b. Automation Engine (app.py)
• Config & Options Module (AUTO_GENERATE_USERINFO, proxy toggles, headless/UI mode, browser profile settings)
• Data Reader/Generator (reads CSV or synthesizes usernames/dates/passwords)
• WebDriver Manager (uses webdriver-manager to fetch and launch Chromedriver/Geckodriver)
• Stealth Browser Automation (selenium + seleniumwire + undetectable WebDriver)
• SMS API Client (interfaces with sms-activate.org for phone verification)
• Proxy Manager (applies SOCKS5 or HTTP proxies from Proxy_DB)
• Output Writer (writes “Created.txt” for successful registrations)
c. External Services
• Google Account Creation Endpoints (the public Gmail signup pages)
• sms-activate.org (phone verification service)
• Proxy Providers (any third‐party proxy service)
d. Generated Artifacts
• Created.txt (log of successful accounts)
• Local browser profiles (optional, if configured)
Relationships and Data Flows
1. CSV Databases → Automation Engine (Data Reader)
2. Automation Engine → webdriver-manager (driver download)
3. Automation Engine → Stealth Browser Automation → Google Signup Pages
4. Automation Engine → SMS API Client ↔ sms-activate.org
5. Automation Engine → Proxy Manager → Proxy Providers
6. Automation Engine → Output Writer → Created.txt
• Control flow inside the Automation Engine: Config → Data Reader/Generator → Browser setup → Phone verification → Form submission → Result logging.
Architectural Patterns and Design Principles
• Single‐process, modular architecture: break the bot into clear functional modules (Config, Data, Browser, API, Output).
• Separation of concerns: Data ingestion, browser orchestration, external API calls, and logging are independent.
• Plug-in style for WebDriver and proxy: options to switch Chrome/Firefox or enable headless mode with minimal code changes.