Telegram to LinkedIn, posts drafted and published
Posting on LinkedIn is easy to “mean to do” and weirdly hard to actually do. You have the idea, but then it’s formatting, rephrasing, finding an image, second-guessing the hook, and suddenly you’ve burned an hour and published nothing.
Marketing managers feel it when content gets pushed to “tomorrow.” Busy founders feel it between meetings. Consultants do too, because consistency is how you stay top-of-mind. This Telegram LinkedIn automation turns a quick voice note or text into a finished post that goes live.
You’ll learn what this workflow does, what you need to connect, and how to make it match your voice so it doesn’t sound like everyone else on the feed.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Telegram to LinkedIn, posts drafted and published
flowchart LR
subgraph sg0["Telegram Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Telegram Trigger"]
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set 'Text'", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Switch", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Download File"]
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/linkedin.svg' width='40' height='40' /></div><br/>Create a post"]
n5@{ icon: "mdi:robot", form: "rounded", label: "Transcribe Audio", pos: "b", h: 48 }
n6@{ icon: "mdi:robot", form: "rounded", label: "Create Image", pos: "b", h: 48 }
n7@{ icon: "mdi:robot", form: "rounded", label: "LinkedIn Post Text", pos: "b", h: 48 }
n8@{ icon: "mdi:robot", form: "rounded", label: "Image Prompt", pos: "b", h: 48 }
n2 --> n3
n2 --> n1
n1 --> n7
n6 --> n4
n8 --> n6
n3 --> n5
n0 --> n2
n5 --> n7
n7 --> n8
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n5,n6,n7,n8 ai
class n2 decision
classDef customIcon fill:none,stroke:none
class n0,n3,n4 customIcon
Why This Matters: LinkedIn Consistency Gets Derailed by Friction
Most LinkedIn posting problems aren’t “lack of ideas.” They’re tiny bits of friction that stack up. You write something raw, then rewrite it to sound less messy. You remember LinkedIn hates giant walls of text, so you add spacing. Then you go hunting for a visual (or you post without one and hope it performs). If you’re doing voice notes, you still have to transcribe, clean it up, and make it readable. By the time it’s ready, the moment has passed and the draft sits in limbo.
It adds up fast. Here’s where it breaks down.
- You lose about 30–60 minutes per post to “polish work” that doesn’t actually create new ideas.
- Voice notes are great for capturing thoughts, but transcription and cleanup can become a whole separate task.
- Design is a bottleneck, so you either skip visuals or recycle the same template until it stops working.
- When posting requires opening LinkedIn, drafts often die in the last mile because you get distracted.
What You’ll Build: Telegram In, LinkedIn Post Out (With an AI Image)
This workflow turns Telegram into your “capture and publish” lane for LinkedIn. You send either a text message or a voice note to a Telegram bot. If it’s voice, the workflow fetches the audio file and uses OpenAI to transcribe it into usable text. That text is then rewritten into a LinkedIn-ready post with a clean structure, a solid hook, and formatting that fits typical character limits. Next, the workflow generates an image prompt based on what you wrote, produces a relevant AI image, and publishes the finished package to LinkedIn automatically. You get consistency without babysitting every draft.
The workflow starts in Telegram, then routes your input down the right path (text or voice). OpenAI handles the heavy lifting for both writing and visuals. Finally, the LinkedIn node publishes the update so you don’t have to log in and manually post.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Let’s say you post 4 times per week. Manually, a typical “quick” LinkedIn post can still take about 45 minutes: write, format, find an image, then publish. That’s roughly 3 hours a week. With this workflow, you can send a 2-minute voice note (or a short text), then let transcription, rewriting, image creation, and publishing run in the background. Most teams get those 3 hours back and still post the same week.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Telegram for sending text or voice notes.
- OpenAI to transcribe audio and generate content.
- LinkedIn app OAuth credentials (get them from developer.linkedin.com)
Skill level: Intermediate. You won’t write code, but you will connect accounts and handle OAuth credentials.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
Telegram message kicks things off. You send a text message or voice note to your Telegram bot, and the Telegram Trigger starts the workflow immediately.
The workflow routes voice vs. text. A routing step checks the message type. Text gets assigned to a clean “post input” field, while voice messages trigger a file fetch from Telegram so the audio can be processed.
OpenAI turns raw input into a real post. Voice notes are transcribed first, then the workflow composes LinkedIn copy using a prompt that enforces structure, tone, and practical character limits. This is where your content goes from “brain dump” to publishable.
An image gets generated and attached. The workflow creates an image prompt based on the final post, produces an AI image, and then publishes the LinkedIn update with both text and visual.
You can easily modify the writing prompt to match your style, or change the image settings for a different look. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Telegram Trigger
This workflow starts when a Telegram message arrives, so configure the trigger to listen for messages.
- Add and open Telegram Message Trigger.
- Set Updates to
message. - Credential Required: Connect your telegramApi credentials.
Step 2: Route Text vs. Voice Messages
Incoming messages are routed based on whether they contain text or a voice file.
- Open Route Message Types and confirm the Voice rule checks
{{ $json.message.voice.file_id }}with the exists operator. - Confirm the Text rule checks
{{ $json.message.text }}with the exists operator. - Verify the execution flow: Telegram Message Trigger → Route Message Types, then voice messages go to Fetch Voice File and text messages go to Assign Text Field.
Step 3: Prepare Text Input for AI Processing
Text messages and voice transcripts are normalized into a single text field used by the AI copywriter.
- In Assign Text Field, add an assignment with Name
textand Value{{ $json.message.text }}. - Open Fetch Voice File and set Resource to
file. - Set File ID to
{{ $json.message.voice.file_id }}. - Credential Required: Connect your telegramApi credentials in Fetch Voice File.
Step 4: Configure AI Generation for Copy and Images
The workflow transcribes voice input, composes LinkedIn copy, generates an image prompt, and produces an AI image.
- In Audio Transcription, set Resource to
audioand Operation totranscribe. - Credential Required: Connect your openAiApi credentials in Audio Transcription.
- In Compose LinkedIn Copy, keep the provided prompt content and ensure it references
{{ $json.text }}in the message. - Credential Required: Connect your openAiApi credentials in Compose LinkedIn Copy.
- In Generate Image Prompt, ensure the prompt uses
{{ $json.message.content }}from the LinkedIn copy output. - Credential Required: Connect your openAiApi credentials in Generate Image Prompt.
- In Produce AI Image, set Resource to
image, Model togpt-image-1, and Prompt to{{ $json.message.content }}. - Credential Required: Connect your openAiApi credentials in Produce AI Image.
Step 5: Configure the LinkedIn Publishing Action
The final step publishes the AI-generated copy and image to LinkedIn.
- Open Publish LinkedIn Update and set Text to
{{ $('Compose LinkedIn Copy').item.json.message.content }}. - Set Person to your LinkedIn ID, replacing
[YOUR_ID]. - Set Share Media Category to
IMAGE. - Credential Required: Connect your linkedInOAuth2Api credentials.
Step 6: Test and Activate Your Workflow
Run a full test to ensure both text and voice inputs create a LinkedIn post with an AI image.
- Click Execute Workflow and send a text message to your Telegram bot to test the text path.
- Send a voice message to test the voice transcription path (Fetch Voice File → Audio Transcription → Compose LinkedIn Copy).
- Confirm that Publish LinkedIn Update posts the generated copy and image to LinkedIn.
- Once verified, toggle the workflow to Active for production use.
Troubleshooting Tips
- LinkedIn credentials can expire or need specific permissions. If things break, check your LinkedIn app OAuth settings and the connected credentials inside n8n first.
- If Telegram voice file downloads fail, it’s usually the bot token or file access. Re-check the BotFather token and confirm the workflow can fetch the voice message file.
- OpenAI outputs depend heavily on your prompts. Frankly, the default tone can sound generic, so add your brand voice and a few “do and don’t” examples early.
Quick Answers
About 30 minutes if you already have your API keys and LinkedIn app ready.
No. You’ll connect Telegram, OpenAI, and LinkedIn, then paste in credentials and approve access.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs, which are usually a few cents per post depending on the models you use.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. The fastest win is adjusting the “Compose LinkedIn Copy” prompt so it matches your tone (short sentences, more opinion, fewer emojis, whatever fits). You can also tweak the “Generate Image Prompt” and “Produce AI Image” steps to change the image style, size, or even disable images completely. If you want approvals, add a Google Sheets step before “Publish LinkedIn Update” and only publish rows marked Approved.
Usually it’s expired OAuth credentials or a mismatch between the LinkedIn app settings and what n8n expects. Regenerate your Client Secret, confirm the redirect URL is correct in your LinkedIn developer app, then re-authorize inside n8n. If it works once and then fails later, check token expiration and make sure the LinkedIn app is still in good standing. Rate limits can also show up as failures if you try to post too frequently.
Practically, it can handle daily posting without stress. On n8n Cloud Starter you’re limited by monthly executions, and on self-hosted you’re limited by your server resources. LinkedIn’s API rate limits are the bigger constraint, so avoid bulk backfilling a month of posts in one afternoon.
It depends on how much control you want. n8n is strong when you need branching logic (voice vs. text), multiple AI steps, and the ability to self-host if volumes grow. It’s also easier to inspect and adjust prompts, retries, and edge cases without paying per premium feature. Zapier or Make can be simpler for very basic posting, but they get awkward once you add transcription plus image generation plus formatting. Talk to an automation expert if you want help choosing.
Once this is live, LinkedIn stops being a “when I have time” task. You capture the idea, the workflow does the packaging, and your consistency takes care of itself.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
