AI agent autoposting (ChatGPT, Claude) to Telegram, VK and Max

AI writes — Crosslybot publishes. One webhook, all social networks.

How to set up

1

Create a webhook input in Crosslybot

Open Crosslybot, go to Channels → Webhook, click Create and pick Inbound. You'll get a Bearer token — it's shown once, save it securely (e.g. in your AI agent's environment variables).

2

Attach the webhook as a project source

Create a cross-posting project and set your webhook as the source. Add target channels — Telegram, VK, Max or any combination. Configure AI processing, filters and signatures the same as for a regular source.

3

Teach your AI to send posts

In your GPT agent, Claude Project or custom automation, add an HTTP request to the webhook URL. Send JSON with text (the message itself) and optionally entities (formatting), media (images/videos), buttons (URL buttons).

4

Test via sandbox

Before going live, validate your payload format via POST /v1/sandbox/test. Sandbox checks the JSON schema and media URLs without real publishing, returns errors and warnings.

5

Turn the agent on — posts fly to all targets

AI sends webhook → Crosslybot receives, processes (AI translation, filters, footer trim, signature) and publishes to all project targets. No manual steps between generation and publishing.

Features

Simple Bearer token

Authorization: Bearer crossly_live_... — the standard pattern every LLM and SDK understands.

Accepts Telegram Bot API entities

Incoming webhook accepts the entities field in Telegram Bot API format (offset, length, type). If your AI already generates formatted posts for Telegram — it already speaks Crosslybot. No new format to learn.

Idempotency-Key against duplicates

Pass external_id or Idempotency-Key — re-sending the same ID returns the cached result. Your AI agent can retry safely without risk of duplicate posts.

Full traceability

The trace_id field in the payload links your AI request to the publication in Crosslybot. Logs show the full path: receipt → processing → delivery to all targets.

FAQ

Which plans support webhook input?

Webhook input (receiving posts from external systems) is available on Pro, Maxi and Business plans. Webhook output (sending posts out) — from Standard and above. Sandbox for testing payload format — on all plans.

Can I use the same webhook for multiple AI agents?

Yes, one Bearer token can be used by different agents or scripts. For separate projects, create separate webhook endpoints — that simplifies logging and allows independent token revocation.

What happens if AI sends a post during a target pause?

If one of the project targets has an active deferred pause (via is_advertisement or manual) — the post for that target queues up and publishes after the pause expires. Other targets get the post immediately.

How do I protect against AI agent compromise?

The Rotate token button immediately revokes the old Bearer. You can also temporarily deactivate the webhook via is_active=false without deleting it — all incoming requests will return 403.

Does the webhook support polls and video notes?

MVP doesn't. Supported: text, photo, video, audio, URL buttons, entities (formatting), is_advertisement marker. Polls, video_note and stickers — coming later.

Modern AI agents (ChatGPT, Claude, Gemini, custom LLM pipelines) can write posts as well as humans. The problem is elsewhere: to automatically publish generated content to Telegram, VK and Max, a developer has to integrate three different APIs, implement OAuth for VK, deal with file_id quirks for Telegram, add retry logic. Hours of work — for each new integration.

Crosslybot webhook solves this with a single HTTP request. The AI sends JSON with text and media — Crosslybot receives it, runs it through AI processing (translation, style), ad filters, target signature, and publishes to all configured platforms.

Why webhook instead of direct platform APIs

Telegram Bot API requires a bot token and dealing with file_id which is bot-bound. VK requires OAuth with a custom redirect_uri (we walked that path — it took a month). Max is a separate API with its own auth. For an AI agent that’s three different integrations, three different error formats, three different rate limits.

Crosslybot already solved these and supports all three platforms. Webhook is the interface for AI agents: one URL, one token, one payload format, one error-handling path.

What sets Crosslybot webhook apart

  • Unified payload for all platforms. No need to format separately for VK and Telegram — the AI generates one JSON, Crosslybot adapts it for each target
  • AI processing on Crosslybot’s side — even if your AI is in English, the VK post can go out in Russian (auto-translation)
  • Filters and formatting work the same as for a regular source channel: ad filter, footer trim, word replace, text limits
  • Sequential publish queue — posts from the AI go through the same queue as regular posts, no risk of simultaneous publishing to one channel

Getting started

  1. Sign up for Crosslybot (Free to start, Pro for webhook input)
  2. Create a webhook endpoint in the Channels section
  3. Get the Bearer token (shown once)
  4. Test the format via sandbox
  5. Attach the webhook to a project as source, add target channels
  6. Integrate with your AI agent — POST to your webhook URL

Webhook input is available on Pro, Maxi and Business plans. Sandbox for format testing — free on all plans.

Free plan

Ready to try?

Connect the bot in 2 minutes. Free plan — no cards, no signup.

More about the bot →