Skip to main content
Prompts Node.js Account Registration Automation System

developer coding user risk: high

Node.js Account Registration Automation System

Directs the model to generate complete runnable Node.js code, package.json, and instructions for a production-ready account registration automation system using Playwright or Puppe…

  • Policy sensitive
  • Human review
  • External action: high

PROMPT

ROLE: Senior Node.js Automation Engineer

GOAL:
Build a REAL, production-ready Account Registration & Reporting Automation System using Node.js.
This system MUST perform real browser automation and real network operations.
NO simulation, NO mock data, NO placeholders, NO pseudo-code.

SIMULATION POLICY:
NEVER simulate anything.
NEVER generate fake outputs.
NEVER use dummy services.
All logic must be executable and functional.

TECH STACK:
- Node.js (ES2022+)
- Playwright (preferred) OR puppeteer-extra + stealth plugin
- Native fs module
- readline OR inquirer
- axios (for API & Telegram)
- Express (for dashboard API)

SYSTEM REQUIREMENTS:

1) INPUT SYSTEM
- Asynchronously read emails from "gmailer.txt"
- Each line = one email
- Prompt user for:
  • username prefix
  • password
  • headless mode (true/false)
- Must not block event loop

2) BROWSER AUTOMATION
For EACH email:

- Launch browser with optional headless mode
- Use random User-Agent from internal list
- Apply random delays between actions
- Open NEW browserContext per attempt
- Clear cookies automatically
- Handle navigation errors gracefully

3) FREE PROXY SUPPORT (NO PAID SERVICES)
- Use ONLY free public HTTP/HTTPS proxies
- Load proxies from proxies.txt
- Rotate proxy per account
- If proxy fails → retry with next proxy
- System must still work without proxy

4) BOT AVOIDANCE / BYPASS
- Random viewport size
- Random typing speed
- Random mouse movements (if supported)
- navigator.webdriver masking
- Acceptable stealth techniques only
- NO illegal bypass methods

5) ACCOUNT CREATION FLOW
System must be modular so target site can be configured later.

Expected steps:

- Navigate to registration page
- Fill email, username, password
- Submit form
- Detect success or failure
- Extract any confirmation data if available

6) FILE OUTPUT SYSTEM

On SUCCESS:

Append to:
outputs/basarili_hesaplar.txt
FORMAT:
email:username:password

Append username only:
outputs/kullanici_adlari.txt

Append password only:
outputs/sifreler.txt

On FAILURE:

Append to:
logs/error_log.txt

FORMAT:
${timestamp} Email: X | Error: MESSAGE

7) TELEGRAM NOTIFICATION

Optional but implemented:

If TELEGRAM_TOKEN and CHAT_ID are set:

Send message:

"New Account Created:
Email: X
User: Y
Time: Z"

8) REAL-TIME DASHBOARD API

Create Express server on port 3000.

Endpoints:

GET /stats
Return JSON:

{
  total,
  success,
  failed,
  running,
  elapsedSeconds
}

GET /logs
Return last 100 log lines

Dashboard must update in real time.

9) FINAL CONSOLE REPORT

After all emails processed:

Display console.table:

- Total Attempts
- Successful
- Failed
- Success Rate %
- Total Duration (seconds & minutes)

10) ERROR HANDLING

- Every account attempt wrapped in try/catch
- Failure must NOT crash system
- Continue processing remaining emails

11) CODE QUALITY

- Fully async/await
- Modular architecture
- No global blocking
- Clean separation of concerns

PROJECT STRUCTURE:

/project-root
  main.js
  gmailer.txt
  proxies.txt
  /outputs
  /logs
  /dashboard

OUTPUT REQUIREMENTS:

Produce:

1) Complete runnable Node.js code
2) package.json
3) Clear instructions to run
4) No Docker
5) No paid tools
6) No simulation
7) No incomplete sections

IMPORTANT:

If any requirement cannot be implemented,
provide the closest REAL functional alternative.

Do NOT ask questions.
Do NOT generate explanations only.
Generate FULL WORKING CODE.

OPTIONAL CONTEXT

  • target site registration details

ROLES & RULES

Role assignments

  • Senior Node.js Automation Engineer
  1. NEVER simulate anything.
  2. NEVER generate fake outputs.
  3. NEVER use dummy services.
  4. All logic must be executable and functional.
  5. NO simulation, NO mock data, NO placeholders, NO pseudo-code.
  6. Use ONLY free public HTTP/HTTPS proxies
  7. NO paid services
  8. NO illegal bypass methods
  9. Do NOT ask questions.
  10. Do NOT generate explanations only.
  11. Generate FULL WORKING CODE.
  12. Must not block event loop
  13. Handle navigation errors gracefully
  14. Failure must NOT crash system

EXPECTED OUTPUT

Format
markdown
Constraints
  • complete runnable Node.js code
  • package.json
  • clear run instructions
  • no simulation
  • no mock data
  • no placeholders
  • fully functional

SUCCESS CRITERIA

  • Build a REAL production-ready Account Registration & Reporting Automation System
  • Perform real browser automation and real network operations
  • Implement all system requirements including input browser automation proxy support bot avoidance account creation file output telegram notification dashboard and error handling
  • Produce complete runnable code package.json and instructions

FAILURE MODES

  • May generate simulated mock or placeholder code
  • Might use paid proxies or services
  • Could produce incomplete or non-functional sections
  • May block event loop or crash on errors
  • Might not handle proxy failures or bot detection properly

CAVEATS

Missing context
  • Specific target website and registration URL/selectors.
  • Format of proxies.txt and sample content.
  • Telegram credentials input method.
  • Sample gmailer.txt content.
  • Exact form field selectors/IDs for account creation.
Ambiguities
  • Target registration page/URL not specified.
  • Proxies.txt format not defined (e.g., ip:port per line?).
  • How to set TELEGRAM_TOKEN and CHAT_ID (env vars, prompts?).
  • 'Acceptable stealth techniques only - NO illegal bypass methods' is vague.
  • 'Extract any confirmation data if available' undefined.
  • Dashboard 'real time' update mechanism unclear (WebSockets, polling?).
  • User-Agent 'internal list' source undefined.

QUALITY

OVERALL
0.75
CLARITY
0.90
SPECIFICITY
0.90
REUSABILITY
0.20
COMPLETENESS
0.70

IMPROVEMENT SUGGESTIONS

  • Specify target website URL and exact DOM selectors for form fields.
  • Define proxies.txt format (e.g., 'ip:port' per line) with sample.
  • Clarify Telegram setup (e.g., prompt for token/chat_id or use env vars).
  • Provide a sample list of User-Agents.
  • Add Socket.io for real-time dashboard updates.
  • Make target site URL a configurable input parameter for reusability.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER