Publishing from a webhook to Telegram, Max and VK
One POST — and the post is on Telegram, Max and VK at once.
Telegram 
Max 
VK The problem
A service needs to publish to all platforms at once. That's three separate APIs — the Telegram Bot API, the Max Bot API, the VK API — each with its own tokens, formats and limitations. Three integrations to write, test and maintain.
How Crosslybot solves it
Crosslybot accepts a single POST to the webhook and distributes the post to every target of the project — Telegram, Max and VK. One integration instead of three, with idempotency, HMAC and retry.
Crosslybot accepts a single POST to the webhook and distributes the post to every platform of the project at once — Telegram, Max and VK. Instead of three separate integrations with platform APIs, the service works with one endpoint.
Crosslybot adapts text and media for each platform itself; you send a single payload. Idempotency protects against duplicates, and delivery to each target is independent — a failure in one doesn’t block the others. The sandbox endpoint lets you validate the payload without real publishing.
How to set up
Connect the platforms
In the Crosslybot dashboard, connect a Telegram channel, a Max channel and a VK community into one project.
Create a webhook endpoint
Create an incoming webhook and attach it to this project with all three targets.
Send a POST
Send JSON with text, media and idempotency_key — the post goes to every target.
Wire it into your pipeline
Call the webhook from your backend, cron, CI/CD or an AI agent.
What's inside
One integration instead of three
No need to write and maintain the Telegram Bot API, Max Bot API and VK API separately — one webhook covers everything.
Format per platform
Crosslybot adapts text and media for Telegram, Max and VK itself — you send a single payload.
Idempotency and retry
A repeated POST with the same key doesn't create a duplicate; delivery to each target is retried independently on failures.
Result
The service publishes to all platforms with a single request. Three platform APIs are replaced by one webhook.
FAQ
Can I choose which targets a specific post goes to?
Yes. By default the post goes to every target of the project, but the payload can specify targets for addressed publishing.
What if one platform is unavailable?
Delivery to each target is independent — a failure in one doesn't block the others, a failed one is retried automatically.
How do I test?
The /v1/sandbox/test endpoint validates the payload without real publishing to any target.
What plan is needed?
Webhook IN is available on the Pro plan and above.
Ready to try?
Connect the bot in 2 minutes. Free plan — no cards, no signup.