Skip to main content

Cross-platform content publisher: Telegram to WordPress, Facebook, X & LinkedIn

Workflow preview

Workflow preview
100%
Cross-platform content publisher: Telegram to WordPress, Facebook, X & LinkedIn preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

==Reason Of The Workflow== This n8n workflow automatically shares content from a Telegram Channel to multiple platforms like WordPress , Facebook , X/Twitter , and LinkedIn . It uses a Switch node ...

Best for

  • Social Media automation workflows
  • Multimodal AI automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.telegramtrigger, n8n-nodes-base.telegram, n8n-nodes-base.merge, n8n-nodes-base.noop, n8n-nodes-base.wordpress, n8n-nodes-base.editimage, n8n-nodes-base.httprequest, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by SpaGreen Creative.

Original n8n.io source

1.1 Workflow description

Title
Cross-platform content publisher: Telegram to WordPress, Facebook, X & LinkedIn
Workflow name
Cross-platform content publisher: Telegram to WordPress, Facebook, X & LinkedIn

==Reason Of The Workflow==

This n8n workflow automatically shares content from a Telegram Channel to multiple platforms like WordPress, Facebook, X/Twitter, and LinkedIn. It uses a Switch node to detect the type of content—text, image, video, audio, or document—and sends it to the right processing and publishing nodes for each platform.

Who Is This For?

This workflow is ideal for content creators, marketers, and organizations who use a Telegram Channel as their main content hub. It eliminates the need for manual, repetitive posting across different social media and blogging platforms by instantly detecting new posts in Telegram and distributing them according to their content type.

What This Workflow Does

The SocialVibe workflow is a sophisticated automation designed to handle diverse media types and publishing requirements:

  • Real-Time Triggering: It instantly activates upon the detection of a new message (channel_post event) in your configured Telegram Channel.
  • Intelligent Content Detection: It uses a Switch node and a Code node to analyze the Telegram payload and correctly identify the type of content posted (e.g., plain text, image, video, audio, or document).
  • Platform-Specific Publishing: It tailors the publishing action for each platform, ensuring images go to the WordPress media library, text becomes a Tweet, etc.
  • Caption-as-Text: The Telegram post's caption is automatically used as the post body, Tweet text, or blog post content/excerpt.

Key Features

  • Versatile Media Support: Handles over 9 different content types (Text, Photo, Video, Audio, Document, etc.).
  • Dedicated WordPress Integration:
    • Creates a new post/article.
    • Uses an Edit Imageautomatically resize images to optimize for web upload.
    • Uploads the image to the WordPress Media Library via HTTP Request.
    • Sets the uploaded image as the post's Featured Image.
  • Broad Social Media Reach: Supports cross-posting to X/Twitter, Facebook Page, LinkedIn Profile, and LinkedIn Page.
  • Customizable Settings: Easily adjust WordPress categories, post status, and platform-specific settings like LinkedIn target IDs.

Required Credentials & Accounts

  1. Telegram Bot Token: The bot must be an administrator in the source channel.
  2. WordPress API Credentials: For REST API access (username/password or application password).
  3. Facebook Graph API Credentials: With permissions to post to the target Page.
  4. LinkedIn OAuth2 Credentials: To post on a Profile and/or Company Page.
  5. Twitter/X OAuth2 Credentials: For publishing tweets.

How to Use — Step-by-Step Setup

  1. Set Up All Credentials:
    • Configure all necessary API credentials (Telegram, WordPress, Facebook, LinkedIn, Twitter) within your n8n instance.
  2. Configure Telegram Trigger:
    • Ensure the Telegram Trigger node is set to listen for the channel_post update type.
  3. Customize WordPress Nodes:
    • Update the Create WordPress Post node with your desired Category ID (currently set to 1) and ensure the Status is set to publish (or draft for safety testing).
    • In the HTTP Request nodes (used for WordPress media upload), replace the placeholder URL (e.g., https://yourdomain.myshopify.com/) with your actual WordPress site domain.
  4. Update Social Media Target IDs:
    • LinkedIn: Update the Person ID (e.g., PghXXXXnRg) and Organization ID (e.g., 109XXX908) in the respective LinkedIn nodes to match your profile and company page.
    • Telegram Send/Repost: Update the chatId (e.g., -10025XXXX5258) in the sending Telegram nodes to match the channel or group you want to cross-post to.

Support & Help

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Telegram Trigger

Type / Role
n8n-nodes-base.telegramTrigger - telegramTrigger
Config choices
Version 1.2

Block 2 - Download audio

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 3 - Download document

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 4 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 5 - do nothing

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

Block 6 - Download file

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 7 - Create WordPress Post

Type / Role
n8n-nodes-base.wordpress - wordpress
Config choices
Version 1

Block 8 - Edit Image

Type / Role
n8n-nodes-base.editImage - editImage
Config choices
Version 1

Block 9 - upload media to wp

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 10 - upload image to meta data

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 11 - set featured image

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 12 - Download image

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 13 - Get a image

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 14 - Get facebook post image

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 15 - Get linkedIn profile post image

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 16 - Get linkedIn page post image

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 17 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Detect Message Type

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.3

Block 19 - Download voice

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 20 - send text post

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 21 - Create Tweet text

Type / Role
n8n-nodes-base.twitter - twitter
Config choices
Version 2

Block 22 - Create profile text post

Type / Role
n8n-nodes-base.linkedIn - linkedIn
Config choices
Version 1

Block 23 - Create page text post

Type / Role
n8n-nodes-base.linkedIn - linkedIn
Config choices
Version 1

Block 24 - Facebook text post

Type / Role
n8n-nodes-base.facebookGraphApi - facebookGraphApi
Config choices
Version 1

Showing the first 24 of 52 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Cross-platform content publisher: Telegram to WordPress, Facebook, X & LinkedIn
Complexity advanced
Nodes 52
Categories Social Media, Multimodal AI
Author SpaGreen Creative
Published 22 Nov 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/11127/11127.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Cross-platform content publisher: Telegram to WordPress, Facebook, X & LinkedIn do?

==Reason Of The Workflow== This n8n workflow automatically shares content from a Telegram Channel to multiple platforms like WordPress , Facebook , X/Twitter , and LinkedIn . It uses a Switch node ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Social Media, Multimodal AI use case.