RSS feed into channels: auto-publishing via webhook
A new RSS entry — and it's automatically on every channel.
Telegram 
VK 
Max The problem
Content goes live on a site, blog or podcast and lands in the RSS feed. But it's still posted to social media by hand — with a delay and not always. The RSS exists, but it's of no use for the channels.
How Crosslybot solves it
Crosslybot accepts posts via webhook, which means the RSS feed can be connected through any no-code service: a new entry in the feed → the Crosslybot webhook → publishing to every channel. Fully automatically.
Crosslybot lets you publish an RSS feed to every channel automatically. Through a no-code service (n8n, Make, Zapier) an RSS trigger catches a new entry and sends it to the Crosslybot webhook, from where the post goes to Telegram, VK and Max.
The source can be any RSS feed — a site, blog, podcast, aggregator. The entry is published right after it appears, with no delay, and idempotency_key protects against duplicates. RSS starts working not just for readers, but for social media too.
How to set up
Create a webhook endpoint
In the Crosslybot dashboard, create an incoming webhook and attach it to a project with targets.
Set up an RSS trigger
In n8n, Make or Zapier, add an RSS trigger on your feed and an HTTP Request step.
Build the payload
Map the entry's fields (title, description, link, image) to the webhook request body.
Enable automation
A new RSS entry automatically goes to Crosslybot and on to every channel.
What's inside
Any RSS feed
A site, blog, podcast, news aggregator — anything that exposes RSS becomes a post source.
No delay
The entry is published to the channels right after it appears in the feed — not when someone gets to it.
Idempotency
idempotency_key protects against duplicates if the RSS trigger fired twice for one entry.
Result
All RSS content automatically spreads across the channels. The feed works not just for readers, but for social media too.
FAQ
Do I need a developer?
No. The RSS → webhook link is built visually in n8n, Make or Zapier — an RSS trigger plus an HTTP step.
Can I publish the entry's cover?
Yes. If the RSS has an image, it can be passed in the payload — the cover will be attached to the post.
How do I avoid duplicates?
Pass an idempotency_key (for example, the entry ID) — re-processing one entry won't create a duplicate.
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.