Avito Reviews Automation

Overview

An online Avito specialist - someone who promotes on Avito, Russia’s largest classifieds platform - came to me to automate review posting, and specifically through his preferred anti-detect browser, Dolphin Anty.

The concept was first built on Dolphin Anty RPA and then moved to Browser Automation Studio, an engine that holds up better under bulk account work. The bot loads reviews from a file, handles Avito accounts through cookies and login/password, and posts reviews with proxy rotation.

Problem

Posting reviews by hand hits two walls at once. The first is speed: one account, one form, one review at a time. The second is account management: each account has its own session that must be brought up, kept alive, and saved back - and in bulk, spread across proxies so the logins do not all come from one address.

Plus the client’s requirement: work inside his anti-detect browser (Dolphin Anty) rather than a foreign environment - the automation had to fit the process he already had, not replace it.

Solution

The bot takes reviews from Excel or TXT and parses them from the file. Avito accounts are connected through cookies (and login/password) rather than a manual sign-in each time. The logic is then built around an honest check of session state.

That check is the most important part of the script. Before posting, the bot verifies IS_LOGGED_IN: if the cookies are valid it runs the PlaceReviews branch, then SaveCookies (persisting the refreshed session) and ChangeProxy (rotating the proxy before the next account). If the cookies have expired, a separate Fail branch fires with an explicit “cookies invalid, replacement needed” message. Without that step the bot would silently post reviews “into the void” on logged-out accounts and report success.

Review texts are drawn from a file with a random-variant pick via a loop and a random node, so posts are not copies of each other.

Features

• Review loading from Excel/TXT with parsing from the file
• Avito accounts handled through cookies and login/password
• Session-validity check (IS_LOGGED_IN) before every post
• Refreshed cookies saved to a separate folder after a run
• Proxy rotation between accounts
• A dedicated branch for invalid cookies with a clear replacement message
• Random review text picked from a file - variety instead of copies
• Compatibility with the Dolphin Anty anti-detect browser (the first concept ran on Dolphin Anty RPA)
• Multithreading

Development Process

The project began on Dolphin Anty RPA because that was the client’s tool, but it hit the ceiling of that RPA’s capabilities under bulk work and moved to BAS, where account, cookie and proxy handling is more flexible. That is a common fork: stay in the tool the client knows, or take the one that carries the task. The compromise - concept on his platform, production on the right one.

As always in bots like this, the real work went not into “click the review button” but into state management: bring the session up from cookies, verify it is alive, save the refreshed one back, rotate the proxy. The Fail branch for expired cookies is not a detail but what separates a working bot from a demo: without it, bulk posting quietly goes nowhere on logged-out accounts.

Results

• Reviews are posted in bulk from a file rather than one at a time by hand
• Accounts are brought up from cookies with a validity check - no “posting into the void”
• Proxy rotation spreads logins across addresses
• Refreshed sessions are saved back and reused
• The automation slotted into the client’s existing Dolphin Anty stack

What Was Learned

The main technical takeaway is that in account-driven bots the difficulty is in session management, not in the target action. Posting a review is one step; everything else is cookie authentication, liveness checks, saving and proxy rotation. The branch for an invalid session matters more than it looks: it is what turns “the bot reported success” into “the review was actually posted”.

The second takeaway is about the client’s tool. Starting in his environment (Dolphin Anty) is right for speed of entry, but moving to an engine that carries scale saves more. The same logic - a working version first, the right platform second - has run through several projects in this portfolio.