Automation
Phones Parser
A monorepo for automating SIM card operations: collecting balance, tariff, service packages and profile data, maintaining minimum balance, paying tariffs on charge date, changing passwords and confirming operations through the UI.
Inside
- Support for tele2, MegaFon, Beeline and MTS through separate worker processes.
- Automatic minimum balance maintenance and tariff payment on charge date through QIWI tokens.
- The operations log shows task statuses, errors, manual payment confirmations and SMS requests.
Key points
4
mobile operators
QIWI
token-based payments
Excel
import and export
Product view
Phones Parser
The interface is built around an operations dashboard: the main screen shows an event log with queues, errors, manual payment confirmation and SMS code input, while separate sections manage QIWI tokens, phones and passwords. It is closer to an internal work tool than a showcase landing page.
Functionality
Features
Operator account parsing
The backend collects balance, tariff, service packages and profile data through automated scenarios for different mobile operators.
Payments and confirmations
The system can send a phone to payment automatically or leave the action for manual confirmation in the interface.
Phone management
A separate section lists phone numbers, operators, comments, autopay switches, activity state and quick access to a phone card.
Excel import/export
The project can export phones to Excel and parse an incoming Excel file with numbers, required balance and payment markers.
Workflow
From phone registry to controlled payment
The scenario is built around regular SIM card maintenance: load and configure numbers, collect current account data, determine whether payment is needed and complete it automatically or after manual confirmation.
- 01
Add phones and passwords
An operator adds phone numbers and links them with account passwords, QIWI tokens and autopay rules.
- 02
Run data collection
Service cycles send numbers to parsing queues, while worker processes collect balance, tariff, service package and profile data.
- 03
Review actions in the log
The main page shows statuses, errors, operation purpose and tasks that require an SMS code or payment confirmation.
- 04
Pay or cancel
For manual operations the user confirms or cancels payment; automatic actions go through the QIWI queue.
Under the hood
Technical side
Vue 3 + Vite + Vuetify
The frontend is an admin panel with sections for events, QIWI tokens, phones and passwords.
Node.js workers
The Express backend uses Puppeteer/Cheerio for operator scenarios and separate workers for MTS, Beeline, MegaFon, tele2 and QIWI.
Queues and real-time
RabbitMQ, Redis and Socket.IO separate background tasks, processing statuses and interface updates.