This article is an experiment with a twist: it describes setting up auto-posting to MAX — and is published by that very pipeline. Here is what the AI agent actually did and how article publishing works now.
A Task in One Sentence
In September 2026 I set myself a goal: be present on MAX, the messenger Russian business audiences are actively migrating to. The classic path means an evening with the docs, a developer console, and scripts. My path: open ZCode and tell the agent — “let’s get started with MAX.”
What followed was a quest with surprises — and they are exactly what makes this case useful for anyone going the same way.
What Happened in One Session
The real battle log, unretouched:
- Bot registration. The bot was created on the MAX partner platform. Under the 2026 business rules, every bot goes through moderation — ours passed within hours.
- The token trap. A token copied manually from the UI was silently rejected by the API. The reason was embarrassingly simple: manual selection clipped the end of the string. Copy with the icon — that is not aesthetics, that is functionality.
- The documentation trap. The base URL from the official docs did not respond — from Russia or abroad. The agent probed alternatives and found the working host by controlled trial and error. The platform docs are young; that is fine — but be ready for it.
- The auth trap. The classic way of passing the token is deprecated and rejected. The working format is an authorization header without a prefix. You only learn these things in battle.
- The channel. A public channel was created. But adding the bot as admin via “settings → administrators” failed: a fresh bot is invisible in search. The workaround came through subscribers: open a dialog with the bot, press Start, add the bot as a channel subscriber — only then it appears in the list and can be promoted to admin.
- The code. The agent designed and wrote a publisher in TypeScript: API calls, error classification, per-platform text adaptation.
- The first post. Went out to the channel automatically, with a link button to the article. From the phrase “let’s get started” to the first automated publication — one working session.
What Publishing Looks Like Now
The real change is in the operator’s role. “Post this to social media” used to mean four browser tabs, four copy-pastes, four length adjustments. Now I write one phrase to the agent — “publish this article” — from any of my projects.
The pipeline then:
- normalizes and publishes the article on the blog;
- the agent writes a separate adaptation for each platform — not a copy, but a repackage: its own hook, length, and tone;
- I see every text and press OK — nothing goes out without explicit human approval;
- posts land in the Telegram channel, the VK community, and the MAX channel.
I want to stress this: no post is published without my explicit consent. Automation removes the drudgery; the decision stays with the human. In B2B, reputational risk costs more than any time saved.
Why This Matters for Business, Not Just Engineering
The case looks technical, but the economics are simple:
- B2B content marketing only works with consistency. One post a month builds no authority; two or three a week do. The bottleneck is never ideas — it is the mechanics of distribution. The agent removed the mechanics.
- The entry barrier for new platforms dropped to zero. MAX appeared — one session later I have a channel with auto-posting. The next platform plugs in with a token, no code.
- An agent is a new infrastructure layer. I did not hire a developer for a one-off setup or burn my own evening. I set the task, supervised the decisions, accepted the result.
A MAX Bot API Cheat Sheet
Short version, to save you an evening:
- Bots are created on the partner platform (a verified sole-proprietor / company / self-employed profile is required); moderation takes from hours to a day.
- Grab the token with the copy icon; send it in an authorization header — query parameters are no longer accepted.
- Adding a bot to a channel: first open the bot’s dialog and press Start, then “Subscribers → Add”, then promote to admin.
- The channel ID arrives as an event in the bot’s update queue — there is no static way to look it up.
- Rate limits are generous; content posting fits comfortably.
What’s Next
The pipeline lives and grows: new platforms are added with a token, not code. And this article, as promised, went out to social media not by hand — with a single “publish” phrase.
If you want the same pipeline for your blog or store — let’s talk.
Disclosure: this case comes from the author’s own practice — the auto-posting pipeline was built by and runs on automata.sale projects. MAX technical details are current as of September 2026; the platform is evolving, so specifics may change.