System

Auto posting classifieds to Facebook groups

Posts on schedule and in different words every time. Reach without an ad budget.

3636 postsOver 62 working days since early July, from one live account.

59 a dayThat is the average. 104 on the best day.

95% still liveEvery morning the system reopens its past posts and checks they are still there. A group that removed most of them drops out of rotation on its own.

10+ carsSold from leads out of those groups. A person closes the leads; the system brings them in.

What they came with

Classifieds are posted to groups by hand, every day and in dozens of places. Identical text gets throttled as spam, and paid ads do not pay off at that volume.

What was built

The agent posts by itself, driving a browser. A model reads each group and writes a separate text for every post. Posts go out on schedule, and volume grows by adding accounts rather than by loading one harder: each has its own daily cap. Everything is run from Telegram. A human closes the leads; the agent's job is reach without a budget.

Text per groupThe model rewrites the ad for every post and for that specific group, so no two posts are the same.
Reading the groupsGroups are sorted by make, language and rules: where an ad will land and where it will be taken down.
Several accountsPosts are split between accounts: each has its own share and rhythm, and platform limits are never exceeded.
ScheduleSet once, after that nobody has to be involved.
Run from TelegramCommands and reports arrive in the same place, no separate dashboard needed.

Stack

PythonPlaywrightChromeTelegram Bot APIOpenRouterHetzner

What turned out to be hard

Identical text gets throttled as spamThe text is rebuilt for every post: a template with swappable pieces plus a model on top.
There are many groups and few that fitA model sorts the groups: make, language, category, posting rules. A post only goes where it will be accepted, and a group that removed most of what was sent drops out of rotation on its own.
One account cannot publish muchThe daily cap is reached quickly, so volume grows by adding accounts. But volume is not the point; keeping the accounts alive is. A separate layer watches that: pauses, caps, group rotation and an auto stop on warning signals. There have been quiet throttles, but no bans.
An untested scenario burns an accountThere is a dry run: the scenario goes the whole way through without publishing anything.

Cases

Let's talk

Come with the task in your own words: we get on a call, talk it through and work out the answer together.