Telegram to LinkedIn, ready posts with AI images
You get a solid LinkedIn idea… then it dies in drafts. Not because you’re lazy, but because turning a raw thought into a polished post (plus an image that actually fits) takes a weird amount of time and decision-making.
Marketing managers feel it when they need consistent posting without losing half a day. Founders hit it when they’re juggling sales calls and still want a personal brand. And consultants? Same problem, different calendar. This Telegram LinkedIn automation turns one message into a ready-to-use post with an AI image.
Below you’ll see what the workflow does, what you get out of it, and the practical setup details that keep it reliable.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Telegram to LinkedIn, ready posts with AI images
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: "Split Out", pos: "b", h: 48 }
n2["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>generate_img"]
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/httprequest.dark.svg' width='40' height='40' /></div><br/>download_img"]
n4@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "tavily", pos: "b", h: 48 }
n6@{ icon: "mdi:robot", form: "rounded", label: "expert_algo", pos: "b", h: 48 }
n7@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
n8@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser1", pos: "b", h: 48 }
n9@{ icon: "mdi:robot", form: "rounded", label: "Community Manager", pos: "b", h: 48 }
n10@{ icon: "mdi:robot", form: "rounded", label: "CM Junior", pos: "b", h: 48 }
n11@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser2", pos: "b", h: 48 }
n12["<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/>Send a photo message"]
n13["<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/>Send a text message"]
n5 -.-> n6
n5 -.-> n9
n10 --> n9
n1 --> n3
n6 --> n10
n6 --> n2
n3 --> n12
n2 --> n1
n0 --> n6
n9 --> n13
n4 -.-> n6
n4 -.-> n10
n4 -.-> n9
n7 -.-> n6
n8 -.-> n10
n11 -.-> n9
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 n6,n7,n8,n9,n10,n11 ai
class n4 aiModel
class n2,n3 api
classDef customIcon fill:none,stroke:none
class n0,n2,n3,n12,n13 customIcon
The Problem: LinkedIn Ideas Don’t Turn Into Posts
Writing for LinkedIn is deceptively slow. You start with a point, then you second-guess the hook, then you rewrite the middle so it doesn’t sound like a brochure. After that, you still need a visual, which means hunting for an image, giving up, or posting without one. The real cost isn’t just the time. It’s the mental drag of restarting every time, plus the inconsistency that makes your content feel random week to week.
The friction compounds. Here’s where things usually break down.
- You rewrite the same idea three times because you don’t have a repeatable structure.
- Trend research gets skipped, so posts end up “fine” but forgettable.
- Images take longer than the writing, especially when you want something on-brand.
- By the time the draft is “ready,” the moment (and motivation) is gone.
The Solution: Telegram Prompt → Post + AI Image
This workflow starts with a simple Telegram message: your idea, a rough bullet list, or even a messy voice-note transcript you paste in. n8n captures that prompt, then uses AI to research what’s currently working on LinkedIn and shapes your idea into a proven content framework. Next, it drafts multiple post options in a consistent style, evaluates which one is most likely to perform, and selects the best version. In parallel, it creates a custom image prompt, generates an AI image through an image generator API, downloads the file, and sends both the image and the final post back to you in Telegram. No doc-hopping. No “where did I save that draft?”
The workflow kicks off in Telegram, then runs trend research and structured drafting with OpenAI + Tavily. It finishes by delivering a polished LinkedIn post and an AI-generated image right back to your chat so you can post immediately or tweak it.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you publish three LinkedIn posts per week. Manually, a typical cycle might be about 60 minutes writing, 20 minutes researching, and another 20 minutes finding or making an image, so roughly 2 hours per post (about 6 hours weekly). With this workflow, you spend maybe 2 minutes sending a Telegram prompt and 5 minutes reviewing the best draft and swapping a line or two. The AI does the research, drafting, and image generation in the background. You get most of that block of time back, and frankly, your content pipeline stops feeling fragile.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Telegram to send prompts and receive results
- OpenAI for drafting, parsing, and selection
- Tavily API key (get it from your Tavily dashboard)
- RapidAPI key (get it from your RapidAPI account)
Skill level: Intermediate. You’ll connect credentials, paste a few IDs/keys, and do light prompt editing to match your brand voice.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Telegram message triggers everything. You send a prompt to your bot in a specific chat, and n8n grabs the text immediately.
Trend research and a content framework get built. Tavily searches what’s performing on LinkedIn right now, then an AI agent turns those findings into a framework and an image concept that fits your topic.
Drafting happens in options, not guesses. OpenAI generates multiple post drafts in your style, then a “senior editor” style agent reviews them and picks the one most likely to land well.
Your image is generated and delivered with the post. The workflow calls an image generator via HTTP request, downloads the result, and sends you both the image and the final post back in Telegram.
You can easily modify the writing style rules to match your tone, or change the image style to fit your brand visuals. 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 is received, so set up the trigger first.
- Add the Telegram Intake Trigger node to your canvas.
- Credential Required: Connect your telegramApi credentials.
- In Updates, confirm
messageis selected. - Ensure the node is connected to LinkedIn Insight Agent as the next step.
Step 2: Connect the AI Research and Insight Layer
These nodes analyze the Telegram request, search for LinkedIn insights, and structure the response.
- Open LinkedIn Insight Agent and set Text to
={{ $json.message.text }}. - Verify LinkedIn Insight Agent has Has Output Parser enabled and is connected to Framework Output Parser.
- Open Framework Output Parser and set JSON Schema Example to
{ "framework": "string", "img_prompt": "string" }. - Open Tavily Search Tool and set Query to
={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Query', ``, 'string') }}. - Credential Required: Connect your tavilyApi credentials in Tavily Search Tool.
- Open OpenAI Chat Engine and set Model to
gpt-5-nano. - Credential Required: Connect your openAiApi credentials in OpenAI Chat Engine.
LinkedIn Insight Agent uses OpenAI Chat Engine as its language model and Tavily Search Tool as its tool—ensure credentials are added to those parent nodes, not the agent.
Step 3: Set Up Draft Generation and Selection
This section generates three post options and selects the strongest one using a senior CM agent.
- Configure Draft Post Writer with Text set to
=Voici le framework à utiliser : {{ $json.output.framework }}. - Ensure Draft Post Writer has Has Output Parser enabled and is connected to Post Options Parser.
- In Post Options Parser, set JSON Schema Example to
{ "post_1": "string", "post_2": "string", "post_3": "string" }. - Configure Senior CM Selector with Text set to
=Voici les 3 proposition de post : 1 : {{ $json.output.post_1 }} 2 : {{ $json.output.post_2 }} 3 : {{ $json.output.post_3 }}. - Ensure Senior CM Selector has Has Output Parser enabled and is connected to Chosen Post Parser.
- In Chosen Post Parser, set JSON Schema Example to
{ "post": "string" }.
OpenAI Chat Engine is connected as the language model for Draft Post Writer and Senior CM Selector—ensure credentials are added to OpenAI Chat Engine, not the agent nodes.
Step 4: Configure Image Generation and Fetching
This path generates a visual based on the AI output and retrieves the image file for delivery.
- In Image Generator API, set URL to
https://ai-text-to-image-generator-flux-free-api.p.rapidapi.com/aaaaaaaaaaaaaaaaaiimagegenerator/quick.php. - Set Method to
POSTand enable Send Body and Send Headers. - Under Body Parameters, add prompt with value
={{ $json.output.img_prompt }}, style_id set to4, and size set to1-1. - Under Header Parameters, set x-rapidapi-host to
ai-text-to-image-generator-flux-free-api.p.rapidapi.comand x-rapidapi-key to[CONFIGURE_YOUR_API_KEY]. - In Expand Results List, set Field To Split Out to
result.data.results. - In Fetch Generated Image, set URL to
={{ $json.thumb }}.
LinkedIn Insight Agent outputs to both Draft Post Writer and Image Generator API in parallel, so confirm both branches are connected.
⚠️ Common Pitfall: Leaving the RapidAPI key as [CONFIGURE_YOUR_API_KEY] will cause the image request to fail.
Step 5: Configure Telegram Outputs
Send the selected post and generated image back to Telegram.
- In Telegram Photo Dispatch, set Operation to
sendPhotoand enable Binary Data. - Set Chat ID in Telegram Photo Dispatch to
=[YOUR_ID]. - Credential Required: Connect your telegramApi credentials in Telegram Photo Dispatch.
- In Telegram Text Dispatch, set Text to
={{ $json.output.post }}and Chat ID to=[YOUR_ID]. - Credential Required: Connect your telegramApi credentials in Telegram Text Dispatch.
⚠️ Common Pitfall: If the Chat ID is incorrect, messages will not be delivered even if the workflow succeeds.
Step 6: Test and Activate Your Workflow
Validate that both branches execute correctly and that Telegram receives the final outputs.
- Click Execute Workflow and send a test Telegram message to the bot linked in Telegram Intake Trigger.
- Confirm LinkedIn Insight Agent runs and triggers both Draft Post Writer and Image Generator API in parallel.
- Verify that Telegram Photo Dispatch sends an image and Telegram Text Dispatch sends the chosen post text.
- If successful, toggle the workflow to Active for production use.
Common Gotchas
- Telegram credentials can expire or your bot can be pointed at the wrong chat ID. If messages stop triggering, check your Telegram bot token and chat ID in n8n Credentials first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if you already have your API keys.
No. You’ll mostly connect accounts and paste API keys into n8n credentials. The only “technical” part is adjusting prompts if you want a very specific voice.
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 API usage for OpenAI, Tavily, and your RapidAPI image generator.
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. Update the prompt/rules inside the LinkedIn Insight Agent and the Draft Post Writer so it uses your hooks, formatting, and “do/don’t” list. For visuals, change the image prompt produced by the framework stage (or override it before the Image Generator API call) to match your typical look, like minimalist illustrations or product-first graphics. Many teams also add a simple rule like “always include one short story line,” plus a CTA style that matches how they sell.
Usually it’s the bot token or the chat ID. Double-check the Telegram credentials in n8n and confirm the bot is actually allowed to read that chat. If it works sometimes and then fails, rate limits or revoked permissions can be involved, especially in shared group chats. Also make sure you didn’t rotate the token in BotFather and forget to update it in n8n.
If you self-host n8n, there’s no execution limit (it depends on your server). On n8n Cloud, limits depend on your plan, but most small teams can run dozens of prompts a day without thinking about it. Practically, the bottleneck is API rate limits from OpenAI/Tavily/RapidAPI, not n8n itself.
Often, yes, because this flow isn’t a simple two-step zap. You’re doing research, structured parsing, multiple drafts, selection logic, and file handling for the image. n8n is built for that kind of branching without every extra step becoming a pricing problem. Zapier or Make can still work if you simplify the workflow (for example, one draft only and no image generation). If you want help deciding, Talk to an automation expert and explain your posting volume and review process.
This is the kind of workflow you set up once and then lean on every week. Your ideas keep moving, and the “blank page” problem stops running your schedule.
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.
