AI agent
Creates content and metadata, selects the action sequence, handles errors and generates a report.
WORKING · AI AGENT · CONNECTED SERVICES
One piece of content.
Many channels.
A working setup where an AI agent prepares copy and cover images, adapts content for each platform, publishes it and returns live links.
The task
Remove hours of manual layout without losing platform specificity
Several projects carry different brands, audiences and channels. Manually publishing one piece of content across social networks, website feeds and video hosts requires repeated copy preparation, image adaptation, metadata editing and uploads. The solution turns this into a managed workflow: a human sets a topic or supplies finished video, then the agent executes the full tool chain.
Four layers
The agent reasons. Connectors execute.
MCP connectors
Translate agent commands into concrete API calls for each platform and hide the technical specifics.
Secure access
Gives the agent single OAuth access to connectors without passing secrets into the working cloud environment.
Server system
Isolated services, encrypted connections, secret separation and controlled recovery after failures.
Connected tracks
Text, images, feeds and video
Communities and personal profile
Posts, photos, video, cover images and reposts with separate personal and group permissions.
Long post with cover
Bypasses the bot signature limit: up to 4,096 characters plus a large preview in a single message.
Self-hosted Postiz
Text and image publishing through a self-deployed scheduler.
Five websites
Own RSS and embedded widget replace Tilda's missing write API.
Full upload cycle
Preparation, file upload, cover set and video publish within a community.
Resume-capable upload
Video survives connection drops; privacy and final publish account for app review status.
Workflows
Three routines replacing a manual chain
Content
Topic → copy → cover → adapt → Telegram and VK → topic usage journal.
Video
Google Drive → VK Video → YouTube → cover and metadata → result links.
Reposts
Latest video → personal profile and VK communities → Telegram → Dzen → website feeds.
Engineering value
Reliability lives in the details
OAuth instead of plain tokens — a custom shim makes connectors agent-compatible.
Images by link or SVG — avoids unreliable transmission of long base64 strings through the model.
Large video via cloud system — stable channel and no workstation sleep.
VK upload retries — a brief node failure doesn't leave a publish coverless.
Secrets stay on the server — the cloud routine calls tools but never receives platform tokens.
Control
Automation without losing oversight
Within an approved routine, publishing proceeds without extra confirmations. Deleting or editing already published content requires an explicit command. For YouTube, final visibility depends on app review status; until Google approval, uploaded video remains private.