n8n integration with Telegram, VK and Max via webhook

n8n collects data — Crosslybot publishes. One HTTP Request node.

How to set up

Create a webhook input in Crosslybot

Open Crosslybot, go to Channels → Webhook → Create → Inbound. Copy the Bearer token (shown once) — you'll need it for n8n authorization.

Attach the webhook to a project

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

Build a workflow in n8n

Create a new workflow in n8n. Add a trigger — RSS Feed Trigger, Schedule Trigger, Email Trigger or any other. This becomes the data source for posts.

Add HTTP Request node

After the trigger, add an HTTP Request node: Method = POST, URL = your Crosslybot webhook URL, Authentication = Header Auth → Header Name: Authorization → Header Value: Bearer crossly_live_..., Content-Type: application/json. Body sends JSON with text, media, buttons fields.

Activate the workflow

Run the workflow manually to test. Crosslybot received the post → published to all project targets. Then enable the schedule (Schedule Trigger every hour for example) — n8n will send posts automatically.

Features

Any n8n trigger

RSS, Email, Calendar, Postgres, MongoDB, Webhook, Schedule — n8n supports 400+ triggers and integrations. Any of them can be a source for posts.

Compatible JSON format

Crosslybot accepts payload close to Telegram Bot API format: text, entities, media, buttons. In n8n you can use a Set node to transform data into the required structure.

Idempotency via external_id

Pass a unique external_id (e.g. RSS Item ID or DB primary key) — re-sending with the same ID won't create a duplicate post.

Error handling

Crosslybot returns standard HTTP codes: 200 OK on success, 4xx for validation errors, 5xx for internal issues. Use n8n's Error Trigger for logging and retries.

FAQ

Does this work with self-hosted n8n?

Yes. Crosslybot webhook is a regular HTTP API endpoint. Requests can come from any n8n instance: cloud (n8n.cloud), self-hosted on your server, or local for development.

Which n8n triggers work best for content?

Most popular scenarios: RSS Feed Trigger (news aggregation), Schedule Trigger (scheduled publishing), Webhook (receiving data from external systems), Postgres/MySQL (DB selection).

Can I send to different Crosslybot projects from one workflow?

Yes, create a separate webhook endpoint in Crosslybot for each project. In n8n use Switch or IF nodes to route to the appropriate URL.

What about media — how do I send them?

Crosslybot accepts media[] with public HTTPS URLs. If you have a local file, first upload it to any public CDN (S3, Cloudflare R2, ImgBB), then pass the URL. Crosslybot downloads and publishes.

Can I use n8n Cloud Free?

Yes, n8n Cloud Free allows 5000 executions per month — enough for 100+ posts per day. For high-volume production, self-host n8n or upgrade the plan.

n8n is an open-source workflow automation platform, an alternative to Zapier and Make.com. Used by thousands of teams for no-code integrations between services. One of the most common scenarios is collecting data from sources (RSS, databases, forms) and publishing to social networks.

Without Crosslybot you need separate n8n nodes for Telegram, VK and Max. Each requires a token, OAuth, different request format. With Crosslybot — one HTTP Request node to a single webhook URL, and the post flies to all three platforms at once.

Typical n8n scenarios

RSS aggregator: RSS Feed Trigger → Set node (formats data into Crosslybot payload) → HTTP Request → post in TG/VK/Max
Email-to-channel: Gmail Trigger → AI Code node (parses email, generates post) → HTTP Request
DB-to-social: Postgres Trigger (new row) → Function node (forms text) → HTTP Request
Manual approval pipeline: Webhook Trigger (from external form) → Wait For Approval → publish only after approval
Cron-posting: Schedule Trigger (every hour) → Random Item from List → HTTP Request → content rotation

Crosslybot vs direct n8n nodes

No need to configure VK OAuth (Crosslybot already did the work)
No need to deal with Telegram file_id (you pass a regular image URL)
No need to implement retry logic per case — Crosslybot retries publication itself
Built-in AI processing (translation, style) — n8n nodes don’t offer this
Sequential queue — Crosslybot publishes posts in arrival order, n8n doesn’t guarantee that

Getting started

Sign up for Crosslybot, activate Pro+ (required for webhook input)
Create a webhook endpoint in the Channels section
Get the Bearer token
Test the format via sandbox: POST /v1/sandbox/test (you can do this from an n8n HTTP Request node)
Attach the webhook to a project, add target channels
Configure your n8n workflow with HTTP Request node