Can I add Telegram, Instagram or X as a fourth channel?

Telegram is a one-node addition: the Telegram node sends the same message to a channel your bot administers, and the guide shows where to wire it in. Instagram is out. Its publishing API takes image and video media only, not link posts, so we leave it out rather than fake it. X needs its own developer app with write access; the n8n X node posts once you have that.

What happens if LinkedIn or Facebook rejects the post?

That branch fails and the other two still run. n8n keeps the failed execution with the API's error text, and the guide lists the three usual causes: an expired LinkedIn token (they last 60 days), a Page token without pages_manage_posts, and a caption over the platform's length limit.

Does it announce Shorts as well?

By default, yes. The workflow fetches each video's duration, and a filter after that step lets you send Shorts to Discord only, skip them, or treat them like everything else. One field to change, and the guide shows it.

Will this run on Make or Zapier?

Yes. Zapier has a New Video in Channel trigger; on Make the trigger is the RSS module pointed at the channel's upload feed. Both have LinkedIn, Facebook Pages and Discord actions, and the package includes a blueprint for each. Error handling differs: Make can ignore a failed module and carry on, while on Zapier a failed step halts that run.

Do I need a paid n8n plan?

No. Every node here is in free self-hosted n8n and on the n8n Cloud Starter plan. On Cloud, each new video uses one execution; a self-hosted instance has no execution cap.

YTinfDcMade to order

Social media & community

YouTube upload → LinkedIn post + Facebook Page post + Discord announcement

Every new video announced on three channels within one polling interval.

Publish the video and the announcements write themselves. On the next 15-minute poll after YouTube lists a video in the channel feed, a post goes out on LinkedIn, one on the Facebook Page and one in Discord, each with the link and each in that channel's own wording. Made for channel owners and the marketing people who currently paste the link into three tabs. Three uploads on a launch day get three rounds of posts; an edited video gets none.

How it works

YT
Trigger
New public video appears in the channel's Atom upload feed (youtube.com/feeds/videos.xml?channel_id=…), polled by n8n's RSS Feed Trigger every 15 minutes
YouTube
if
Step 1
Drop videos already announced
Remove Duplicates compares each video ID with the IDs it kept from earlier runs; an edited or re-listed video gets no second round.
YT
Step 2
Fetch the video's title, description and thumbnail
One videos.list call returns the title, the description, the thumbnail URL and the duration, and the duration is what separates a Short from a full-length video.
if
Step 3
Write one announcement per channel
A Set node fills three templates from the video data: a long LinkedIn caption, a short Facebook line, a Discord message.
in
Step 4
Post on LinkedIn
The LinkedIn node posts as you or as the Company Page, with the caption as text and the video URL shared as an article, which LinkedIn renders as a link preview.
f
Step 5
Post on the Facebook Page
Facebook gets the message and the link through one Graph API call to the Page feed and builds the preview itself.
Dc
Step 6
Announce in the Discord channel
The webhook posts the caption and the link; Discord embeds the player.
if
Step 7
Keep going if one channel fails
Each posting node is set to continue on error, so an expired LinkedIn token stops nothing else, and the failure shows in the execution log.

What changes once it runs

LinkedIn, Facebook and Discord posts go out on the first poll after the video appears in the channel feed, with no one copying links between tabs.
Each channel gets its own wording from a template you edit once, not the same caption pasted three times.
A video edited or re-listed after publishing is not announced twice; the ID check catches it.
Shorts can go to Discord only, or be skipped, using the duration field the workflow already fetches.
One failed channel leaves the other two untouched, and the failure sits in n8n's execution list with the API's error text.

What you get

The n8n workflow export, tested end to end on a live channel before it ships
Setup guide covering the LinkedIn app, the Meta Page token and the Discord webhook, in the order that avoids redoing steps
Three caption templates (LinkedIn, Facebook, Discord) with the video fields already mapped
A recorded first run, from upload to the three live posts
Make and Zapier versions of the same flow for buyers who are not on n8n

Before you start

Google Cloud project with the YouTube Data API v3 enabled, plus your channel ID; the feed poll costs no quota and the video lookup costs one unit per video
LinkedIn developer app: Share on LinkedIn (w_member_social) to post from a profile, or the Community Management API approved to post as a Company Page
Meta developer app and a Page access token with pages_manage_posts and pages_read_engagement for the Facebook Page
Discord webhook URL for the announcements channel (Server Settings, Integrations, Webhooks)
n8n Cloud, or a self-hosted n8n from late 2024 or newer, so the Remove Duplicates node can remember IDs across runs

Built for

Questions before you buy

Can I add Telegram, Instagram or X as a fourth channel?: Telegram is a one-node addition: the Telegram node sends the same message to a channel your bot administers, and the guide shows where to wire it in. Instagram is out. Its publishing API takes image and video media only, not link posts, so we leave it out rather than fake it. X needs its own developer app with write access; the n8n X node posts once you have that.
What happens if LinkedIn or Facebook rejects the post?: That branch fails and the other two still run. n8n keeps the failed execution with the API's error text, and the guide lists the three usual causes: an expired LinkedIn token (they last 60 days), a Page token without pages_manage_posts, and a caption over the platform's length limit.
Does it announce Shorts as well?: By default, yes. The workflow fetches each video's duration, and a filter after that step lets you send Shorts to Discord only, skip them, or treat them like everything else. One field to change, and the guide shows it.
Will this run on Make or Zapier?: Yes. Zapier has a New Video in Channel trigger; on Make the trigger is the RSS module pointed at the channel's upload feed. Both have LinkedIn, Facebook Pages and Discord actions, and the package includes a blueprint for each. Error handling differs: Make can ignore a failed module and carry on, while on Zapier a failed step halts that run.
Do I need a paid n8n plan?: No. Every node here is in free self-hosted n8n and on the n8n Cloud Starter plan. On Cloud, each new video uses one execution; a self-hosted instance has no execution cap.

Nearby on the shelf

Whole catalog