January 22, 2026

Telegram to Upload-Post, approved posts go live

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Your social posting process probably isn’t “hard.” It’s just endless. Drafts in one place, approvals in another, final posts stuck in a scheduler, and somehow you still miss a day.

This Telegram post automation hits marketers first, because consistency is part of the job. But small business owners and agency leads feel the same friction when approvals drag and content quality slips.

This workflow keeps everything in one loop: generate a post, review it in Telegram, approve it, then publish through Upload-Post. You’ll see how it works, what you need, and where teams usually trip up.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Telegram to Upload-Post, approved posts go live

Click to explore

flowchart LR

    subgraph sg0["Wait for User Topic Reply Flow"]
        direction LR
        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/>Wait for User Topic Reply"]
        n4@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Validate Reply Format", pos: "b", h: 48 }
        n5["<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/code.svg' width='40' height='40' /></div><br/>Parse User Input"]
        n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Input Validation Check", pos: "b", h: 48 }
        n7["<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 Input Error Message"]
        n8@{ icon: "mdi:robot", form: "rounded", label: "AI Content Generator", pos: "b", h: 48 }
        n9@{ icon: "mdi:robot", form: "rounded", label: "Structure AI Output", pos: "b", h: 48 }
        n10["<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/code.svg' width='40' height='40' /></div><br/>Validate Generated Content"]
        n11@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Content Quality Gate", 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 Generation Error"]
        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/code.svg' width='40' height='40' /></div><br/>Format Content Preview"]
        n14["<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 Preview & Await Approval"]
        n15@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check User Approval", pos: "b", h: 48 }
        n16["<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 Cancellation Notice"]
        n17@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Posts for Publishing", pos: "b", h: 48 }
        n18@{ icon: "mdi:cog", form: "rounded", label: "Web Research Tool (Optional)", pos: "b", h: 48 }
        n19@{ icon: "mdi:brain", form: "rounded", label: "AI Language Model", pos: "b", h: 48 }
        n20["<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/merge.svg' width='40' height='40' /></div><br/>Merge Approval Data"]
        n21["<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 Success Notification"]
        n22@{ icon: "mdi:cog", form: "rounded", label: "Publish to Social Platforms", pos: "b", h: 48 }
        n5 --> n6
        n19 -.-> n8
        n15 --> n17
        n15 --> n16
        n20 --> n15
        n9 -.-> n8
        n8 --> n10
        n11 --> n13
        n11 --> n12
        n4 --> n5
        n13 --> n14
        n13 --> n20
        n6 --> n8
        n6 --> n7
        n3 --> n4
        n17 --> n22
        n10 --> n11
        n22 --> n21
        n18 -.-> n8
        n14 --> n20
    end

    subgraph sg1["Schedule Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
        n1["<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/code.svg' width='40' height='40' /></div><br/>Create Schedule Timestamp"]
        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/telegram.svg' width='40' height='40' /></div><br/>Request Content Topic via Te.."]
        n0 --> n1
        n1 --> n2
    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 n3,n0 trigger
    class n8,n9 ai
    class n19 aiModel
    class n4,n6,n11,n15 decision
    class n5,n10,n13,n1 code
    classDef customIcon fill:none,stroke:none
    class n3,n5,n7,n10,n12,n13,n14,n16,n20,n21,n1,n2 customIcon

The Problem: Social posts die in the approval gap

Most teams don’t fail at social because they can’t write. They fail because the writing, checking, approving, and publishing happen in different places, at different times, with different people. A draft gets written, then sits in a doc. Someone requests tweaks in a chat. You copy the final text into a tool, reformat it, and hope you didn’t accidentally remove a link or break the character limit. Multiply that by daily posting and multiple channels, and you’ve created a tiny recurring tax on your business.

It adds up fast. And the worst part is you never feel “done,” because there’s always one more approval, one more paste, one more check.

Approvals happen in scattered threads, so you waste time chasing the latest “final” version.
Character limits get checked too late, which means last-minute rewrites and weaker hooks.
Posting to multiple platforms becomes repetitive admin work, not marketing.
When you’re busy, the process breaks, and consistency disappears for a week.

The Solution: Generate, validate, approve in Telegram, then publish

This workflow turns Telegram into your simple “content command center.” It can start on a schedule, send a prompt request to Telegram, and wait for your reply with the topic or angle you want. From there, it uses an AI model (via OpenRouter, so you can choose GPT-4, Claude, and others) to draft the post. Before you ever see it, the workflow audits the output for format, checks quality against a pass threshold, and enforces a tight character range (240–265) so you’re not posting bloated drafts. Then it sends you a clean preview in Telegram. Reply “approve,” and it publishes through Upload-Post to the platforms you’ve connected. Reply “reject,” and it can retry generation (up to three attempts) or cancel cleanly.

The flow starts with a scheduled trigger and a Telegram message. AI writes the draft and the workflow validates it. Finally, a simple Telegram approval decides whether Upload-Post publishes it or the workflow loops back to improve the draft.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Prompts your team in Telegram and waits for a valid reply.
Generates social copy with your chosen model through OpenRouter.
Audits drafts for length, format, and quality before anyone approves them.
Publishes approved posts to multiple channels using Upload-Post.

Turn a daily “write + chase approvals” loop into about 10 minutes of review.
Fewer last-minute rewrites because bad drafts get caught automatically.
Cleaner collaboration, since approvals live in one Telegram thread.
More consistent posting, even on weeks when you’re slammed.
Less brand drift, because the workflow enforces structure every time.

Example: What This Looks Like

Say you publish one post per day to five channels (LinkedIn, X, Facebook, Instagram, and another community platform). Manually, you might spend about 10 minutes drafting, then another 10 minutes formatting and posting per platform, plus a few minutes chasing an approval. That’s roughly an hour a day. With this workflow, you send a topic in Telegram, wait for the draft, then spend about 5–10 minutes approving (or rejecting). Upload-Post handles the rest, so you’re usually done in under 15 minutes.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Telegram for approvals and notifications.
Upload-Post to publish to your social channels.
OpenRouter API key (get it from your OpenRouter dashboard).

Skill level: Intermediate. You’ll connect a few accounts, paste API keys, and test the approval loop end-to-end.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A schedule (or a message) kicks things off. The workflow can run on a set cadence, generate a timestamp for tracking, and then prompt you in Telegram to send a topic or content request.

Your Telegram reply gets checked before anything else happens. If the message format is off, you’ll get an immediate “input error” response so you’re not wondering why nothing posted.

AI drafts the post and the workflow audits it. Using OpenRouter, the content is generated, then shaped into a structured format. A validation pass checks character length (240–265), basic formatting, and a quality threshold so weak drafts don’t sneak through.

You approve or reject in Telegram, then publishing happens automatically. Approved posts can be split into multiple parts if you’re doing threads, then Upload-Post publishes to the channels you’ve connected and confirms success back in Telegram.

You can easily modify the character limits to match a platform’s best practices based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Scheduled Trigger

Set the workflow cadence so it starts content sessions on a predictable schedule.

Add and open Scheduled Launch Trigger.
Set the Rule to trigger every 5 days at 9 AM using the interval settings shown in the node.
Connect Scheduled Launch Trigger to Generate Run Timestamp.

If you want a daily schedule, adjust daysInterval and triggerAtHour accordingly in Scheduled Launch Trigger.

Step 2: Connect Telegram for Topic Intake and Validation

These nodes collect the topic, validate it, and route valid input into the AI flow. There are 6 Telegram-related nodes—connect the same Telegram credentials to all of them.

Open Telegram Topic Request and set Text to the provided multi-line prompt. Keep the expression for schedule name in place: {{ $json.scheduleName }}.
Set Chat ID to {{ $credentials.telegramChatId }} in Telegram Topic Request.
Add Await Telegram Reply and ensure it listens for updates = message.
Configure Verify Reply Format to check that {{ $json.message.reply_to_message }} exists and {{ $json.message.text }} is not empty.
Keep the parsing logic in Interpret User Message to output topic, format_type, and validation_status.
In Route Valid Input, ensure the condition checks {{ $json.validation_status }} equals passed, then connect success to AI Post Composer and failure to Notify Input Error.
In Notify Input Error, keep Chat ID as ={{ $json.chat_id }} so errors return to the right user.

Credential Required: Connect your Telegram credentials to all Telegram nodes (Telegram Topic Request, Await Telegram Reply, Notify Input Error, Send Preview for Approval, Send Cancellation Update, Send Publish Confirmation).

Step 3: Set Up AI Generation and Structured Output

This step generates social content and ensures a structured JSON response for downstream processing.

Open AI Post Composer and set Text to =Create social media content about: {{ $json.topic }} Format type: {{ $json.format_type }}.
Keep the long System Message in AI Post Composer to enforce character and style rules.
Connect Primary Language Model to AI Post Composer as the language model; set Model to openai/gpt-4o.
Attach Shape AI Response to AI Post Composer as the output parser and leave the manual schema as provided.
If you want web lookup, connect Optional Web Research to AI Post Composer and keep Query as ={{ $fromAI('Query', '', 'string') }}.

Credential Required: Connect your OpenRouter credentials in Primary Language Model. Shape AI Response and Optional Web Research are AI sub-nodes—add credentials to the parent AI Post Composer, not the sub-nodes. If using web research, also connect your Tavily credentials on AI Post Composer.

Step 4: Configure Quality Checks and Preview Creation

Validate the AI output, then build a user-friendly preview for approval.

Verify Audit Generated Content keeps the quality checks and outputs validation_status and tweets_array.
In Quality Approval Gate, confirm the condition checks {{ $json.validation_status }} equals passed to route valid output to Build Preview Text.
Keep Build Preview Text as-is to generate preview_text that includes topic, format, and post count.
Note the parallel flow: Build Preview Text outputs to both Send Preview for Approval and Combine Approval Data in parallel.

⚠️ Common Pitfall: If Audit Generated Content fails often, adjust your topic prompt or the character limits inside the system message of AI Post Composer.

Step 5: Configure Approval Routing and Publishing

Route user approval, split posts for release, and publish to social channels with confirmation.

In Send Preview for Approval, set Chat ID to {{ $node['Interpret User Message'].json.chat_id }} and Message to ={{ $json.preview_text }} with Operation = sendAndWait.
Ensure Combine Approval Data is in mode = combine and combineBy = combineByPosition.
In Evaluate Approval Choice, check {{ $json.data.approved }} is true to send approved content to Split Posts for Release, and rejected content to Send Cancellation Update.
In Split Posts for Release, set Field To Split Out to tweets_array.
Configure Publish to Social Channels with User = {{ $credentials.username }}, Title = ={{ $json.post }}, Operation = uploadText, Platform = x and linkedin, and X Reply Settings = everyone.
Set Send Publish Confirmation to message the same user using {{ $node['Interpret User Message'].json.chat_id }}.

Credential Required: Connect your upload-post platform credentials for Publish to Social Channels. Also confirm Telegram credentials are connected for Send Preview for Approval, Send Cancellation Update, and Send Publish Confirmation.

Step 6: Test and Activate Your Workflow

Validate the full execution from scheduled trigger to approval and publishing.

Manually execute the workflow from Scheduled Launch Trigger and confirm Telegram Topic Request sends the prompt.
Reply in Telegram using a valid format like “sustainable living tips - single” and verify Interpret User Message outputs validation_status = passed.
Confirm the AI path runs from AI Post Composer → Audit Generated Content → Quality Approval Gate and that the preview is sent.
Approve with ✅ and ensure posts publish via Publish to Social Channels and a final message arrives from Send Publish Confirmation.
Activate the workflow by toggling it to Active once tests succeed.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Telegram credentials can expire or the bot can lose webhook access. If things break, check your bot token and webhook URL configuration in Telegram/@BotFather and your 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

How long does it take to set up this Telegram post automation?

About an hour if your API keys and social accounts are ready.

Do I need coding skills to automate Telegram post approvals?

No. You’ll mostly connect accounts and paste credentials. The “logic” is already built into the workflow.

Is n8n free to use for this Telegram post automation workflow?

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 OpenRouter usage (often a few cents per post, depending on model and retries).

Where can I host n8n to run this automation?

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.

Can I customize this Telegram post automation workflow for threads and different tones?

Yes, and it’s one of the best reasons to use this template. You can switch between single posts and 3–6 post threads by adjusting the AI prompt and keeping the “Split Posts for Release” logic enabled. Tone changes usually live in the AI Post Composer instructions (for example: educational, founder voice, playful, or technical). If you want current events, turn on the optional Tavily web research tool so the model has fresh context.

Why is my Telegram connection failing in this workflow?

Usually it’s the bot token or webhook URL being wrong after a change to your n8n domain. Regenerate the Telegram bot token if needed, then update the Telegram credentials in n8n. Also check that your n8n instance can receive inbound webhooks (common issue on locked-down firewalls), because the approval replies depend on it. If failures happen only sometimes, rate limits or a slow instance can cause Telegram triggers to arrive late.

How many posts can this Telegram post automation handle?

A lot.

Is this Telegram post automation better than using Zapier or Make?

For an approval-driven workflow, n8n is usually a better fit because you can add branching, retries, validation checks, and multi-step logic without turning it into an expensive pile of tasks. It also supports self-hosting, which matters once you’re generating and posting every day across multiple brands. Zapier and Make can still work if you only need a basic “send draft, get yes/no, post” flow, but you’ll hit limits faster when you add quality gates and threads. If you’re unsure, map out the must-haves (approval, retries, character enforcement, multi-platform publishing) and compare costs. Talk to an automation expert if you want a quick second opinion.

Once this is running, “posting daily” stops being a daily project. You approve in Telegram, Upload-Post publishes, and you move on to work that actually grows the business.

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.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": null,
"meta": {
"instanceId": "62a5a3c6d9061fc6d0a3944aa6417a7a2a77dcb3d93cd88aafaca67fbfc8889a",
"templateId": null,
"templateCredsSetupCompleted": null
},
"name": "Automated Social Content Generation Flow",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-5773",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1620,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "c6047198-7450-4cb5-bceb-4e2b73358d84",
"name": "Scheduled Launch Trigger",
"type": "n8n-nodes-base.scheduleTrigger",
"position": [
1240,
150
],
"parameters": {
"rule": {
"interval": [
{
"description": "Triggers the workflow every 5 days at 9 AM. You can adjust the frequency and time based on your content posting schedule.",
"daysInterval": 5,
"triggerAtHour": 9
}
]
}
},
"description": "This node triggers your content generation workflow on a schedule. Default is every 5 days at 9 AM, but you can adjust this to daily, weekly, or any custom schedule that fits your content strategy. The workflow will start automatically at the specified time.",
"typeVersion": 1.2
},
{
"id": "ec142ab7-8ce7-4184-b5a7-a2dc017cf204",
"name": "Generate Run Timestamp",
"type": "n8n-nodes-base.code",
"position": [
1010,
190
],
"parameters": {
"jsCode": "// This node creates a human-readable timestamp for the current schedule run\n// It helps track when each content generation session was initiated\n\nconst today = new Date();\nconst days = ['Sunday', 'Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday', 'Saturday'];\nconst scheduleName = `${days[today.getDay()]} ${today.getHours()}:00`;\n\nreturn [{\n  json: {\n    scheduleName: scheduleName,\n    timestamp: new Date().toISOString(),\n    workflowId: $workflow.id\n  }\n}];"
},
"description": "Creates a human-readable timestamp and schedule name for tracking purposes. This helps you identify which schedule triggered the content generation, especially useful if you have multiple schedules running.",
"typeVersion": 2
},
{
"id": "f042b594-63ee-4f6f-8c8c-5c279b3e9725",
"name": "Telegram Topic Request",
"type": "n8n-nodes-base.telegram",
"position": [
790,
150
],
"webhookId": "3c293ac0-62b9-4fe3-b9f8-e3ce7b26e906",
"parameters": {
"text": "\ud83d\ude80 **Content Generation Time!**\n\nIt's time for your {{ $json.scheduleName }} content creation session.\n\nPlease reply with:\n- Your topic or theme\n- Type 'single' for one post or 'thread' for multiple connected posts\n\nExample responses:\n- 'sustainable living tips - single'\n- 'how to start a podcast - thread'\n- 'morning motivation - single'",
"chatId": "{{ $credentials.telegramChatId }}",
"additionalFields": []
},
"description": "Sends a message to your Telegram chat asking for the content topic and format. The message will appear in the Telegram chat/channel you've configured in the credentials. Make sure to set up your Telegram bot and add the chat ID in the credentials.",
"typeVersion": 1.2
},
{
"id": "14f2252b-731d-45a3-9fca-2042986054a7",
"name": "Await Telegram Reply",
"type": "n8n-nodes-base.telegramTrigger",
"position": [
560,
210
],
"webhookId": "telegram-topic-reply-webhook",
"parameters": {
"updates": [
"message"
],
"additionalFields": []
},
"description": "This webhook listens for your reply in Telegram. When you send a message in response to the topic request, this node captures it and passes it to the next step. Make sure the webhook is properly configured in your Telegram bot settings.",
"typeVersion": 1.1
},
{
"id": "423bd47a-2512-492e-933a-ece6eafd82d2",
"name": "Verify Reply Format",
"type": "n8n-nodes-base.if",
"position": [
340,
360
],
"parameters": {
"options": [],
"conditions": {
"options": {
"version": 1,
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"id": "486d068f-b5cb-4af4-aee8-beb09dd02802",
"operator": {
"type": "any",
"operation": "exists"
},
"leftValue": "={{ $json.message.reply_to_message }}"
},
{
"id": "9b8ba1b0-008e-4749-b808-9b9cfd8480ae",
"operator": {
"type": "string",
"operation": "isNotEmpty"
},
"leftValue": "={{ $json.message.text }}"
}
]
}
},
"description": "Checks if the Telegram message is a valid reply to the bot's request. It ensures the message is not empty and is actually a reply to the bot's prompt. This prevents the workflow from processing random messages in the chat.",
"typeVersion": 2
},
{
"id": "848c5396-8b1b-458c-ae14-b32314d0cdac",
"name": "Interpret User Message",
"type": "n8n-nodes-base.code",
"position": [
570,
390
],
"parameters": {
"jsCode": "// This node parses the user input and validates the format\n// Expected format: 'topic - format' where format is 'single' or 'thread'\n// If no format is specified, it defaults to 'auto'\n\ntry {\n  const userInput = $json.message.text;\n  let topic, formatType;\n  \n  if (userInput.includes(' - ')) {\n    const parts = userInput.split(' - ');\n    topic = parts[0].trim();\n    formatType = parts[1].trim().toLowerCase();\n  } else {\n    // If no format specified, default to auto\n    topic = userInput.trim();\n    formatType = \"auto\";\n  }\n  \n  // Validate format type\n  const validFormats = ['single', 'thread', 'auto'];\n  if (!validFormats.includes(formatType)) {\n    throw new Error(`Invalid format type: ${formatType}. Use 'single', 'thread', or 'auto'`);\n  }\n  \n  // Validate topic length\n  if (topic.length < 3) {\n    throw new Error('Topic too short. Please provide a more detailed topic.');\n  }\n  \n  return [{\n    json: {\n      topic: topic,\n      format_type: formatType,\n      chat_id: $json.message.chat.id,\n      username: $json.message.from.username,\n      original_message: userInput,\n      validation_status: 'passed'\n    }\n  }];\n} catch (error) {\n  return [{\n    json: {\n      error: error.message,\n      validation_status: 'failed',\n      chat_id: $json.message.chat.id\n    }\n  }];\n}"
},
"description": "Extracts the topic and format from the user's message. Supports three formats: 'single' (one post), 'thread' (multiple connected posts), or 'auto' (let AI decide). The topic must be at least 3 characters long. If format is not specified, defaults to 'auto'.",
"typeVersion": 2
},
{
"id": "c82ea174-70e4-4fa1-89df-1809d6a7beb1",
"name": "Route Valid Input",
"type": "n8n-nodes-base.if",
"position": [
820,
360
],
"parameters": {
"options": [],
"conditions": {
"options": [],
"combinator": "and",
"conditions": [
{
"operator": {
"type": "string",
"operation": "equals"
},
"leftValue": "={{ $json.validation_status }}",
"rightValue": "passed"
}
]
}
},
"description": "Routes the workflow based on validation results. If the input passes validation, it proceeds to content generation. If validation fails, it sends an error message back to the user with instructions on the correct format.",
"typeVersion": 2
},
{
"id": "d4b44f05-a404-4024-9a9d-c4a7ea968269",
"name": "Notify Input Error",
"type": "n8n-nodes-base.telegram",
"position": [
820,
640
],
"webhookId": "32b0496e-9b72-4806-a961-9a1a9a61670e",
"parameters": {
"text": "\u274c **Input Error**\n\n{{ $json.error }}\n\nPlease try again with the correct format:\n'your topic - single' or 'your topic - thread'\n\nExamples:\n- 'productivity tips - single'\n- 'beginner's guide to investing - thread'\n- 'motivational quote' (defaults to auto)",
"chatId": "={{ $json.chat_id }}",
"additionalFields": []
},
"description": "Sends an error message to the user if their input format is incorrect. Provides clear examples of the expected format to help users correct their input.",
"typeVersion": 1.2
},
{
"id": "6a2eda85-388f-46a8-96db-8c1dea1893ec",
"name": "AI Post Composer",
"type": "@n8n/n8n-nodes-langchain.agent",
"maxTries": 3,
"position": [
1050,
330
],
"parameters": {
"text": "=Create social media content about: {{ $json.topic }}\nFormat type: {{ $json.format_type }}",
"options": {
"systemMessage": "=You are a professional social media content creator. Your task is to generate engaging, high-quality content for Twitter/X and LinkedIn.\n\nCONTENT REQUIREMENTS:\n\nCHARACTER COUNT:\n- EVERY tweet/post MUST be between 240-265 characters\n- Count characters before finalizing\n- Rewrite if outside this range\n\nFORMAT GUIDELINES:\n- For 'single': Create one standalone post\n- For 'thread': Create 3-6 connected posts that tell a complete story\n- For 'auto': Decide based on topic complexity (simple topics = single, complex = thread)\n\nWRITING STYLE:\n- Clear, conversational tone\n- Use simple language\n- Include 1-2 relevant hashtags\n- Be engaging and value-driven\n- Professional but approachable\n- NO numbered lists in the beginning of posts (avoid \"1/\", \"2/\" etc.)\n\nCONTENT STRUCTURE:\n- Hook: Start with an attention-grabbing statement\n- Value: Provide useful information or insights\n- Call-to-action: Encourage engagement (questions, thoughts, actions)\n\nADAPT TO TOPIC:\n- Business topics: Professional, data-driven\n- Creative topics: Inspiring, imaginative\n- Educational topics: Clear, structured\n- Personal topics: Authentic, relatable\n- Technical topics: Simple explanations, practical examples\n\nREMEMBER:\n- Quality over quantity\n- Each post should provide value\n- Maintain consistency in tone throughout threads\n- Use line breaks for readability\n- End threads with a summary or key takeaway"
},
"promptType": "define",
"hasOutputParser": true
},
"description": "The AI agent that generates your social media content. It uses the topic and format you provided to create posts optimized for engagement. The system prompt ensures consistent quality and character count. Configure retry attempts (default: 3) for reliability.",
"retryOnFail": true,
"typeVersion": 1.7
},
{
"id": "fba80a7f-9426-433d-af64-033effba9a06",
"name": "Shape AI Response",
"type": "@n8n/n8n-nodes-langchain.outputParserStructured",
"position": [
1200,
230
],
"parameters": {
"schemaType": "manual",
"inputSchema": "{\n  \"type\": \"object\",\n  \"properties\": {\n    \"event_name\": {\n      \"type\": \"string\",\n      \"description\": \"Name or title for this content batch\"\n    },\n    \"event_description\": {\n      \"type\": \"string\",\n      \"description\": \"Brief description of the content theme\"\n    },\n    \"content_type\": {\n      \"type\": \"string\",\n      \"description\": \"Either 'single' or 'thread'\"\n    },\n    \"platform_posts\": {\n      \"type\": \"object\",\n      \"properties\": {\n        \"Twitter\": {\n          \"type\": \"object\",\n          \"properties\": {\n            \"thread\": {\n              \"type\": \"array\",\n              \"items\": {\n                \"type\": \"object\",\n                \"properties\": {\n                  \"tweet_number\": {\n                    \"type\": \"integer\",\n                    \"description\": \"Order number in thread\"\n                  },\n                  \"post\": {\n                    \"type\": \"string\",\n                    \"description\": \"The actual tweet content\"\n                  },\n                  \"character_count\": {\n                    \"type\": \"integer\",\n                    \"description\": \"Character count for validation\"\n                  }\n                }\n              }\n            },\n            \"single_post\": {\n              \"type\": \"string\",\n              \"description\": \"Content for single post format\"\n            },\n            \"hashtags\": {\n              \"type\": \"array\",\n              \"items\": {\n                \"type\": \"string\"\n              },\n              \"description\": \"List of hashtags used\"\n            },\n            \"thread_length\": {\n              \"type\": \"integer\",\n              \"description\": \"Number of posts in thread\"\n            }\n          }\n        }\n      }\n    },\n    \"additional_notes\": {\n      \"type\": \"string\",\n      \"description\": \"Any additional context or notes\"\n    }\n  }\n}"
},
"description": "Defines the expected JSON structure for the AI's output. This ensures the AI returns content in a consistent format that can be processed by subsequent nodes. The schema includes fields for both single posts and threads.",
"typeVersion": 1.2
},
{
"id": "09b580d2-71bc-44ab-ba69-96da0fc4bd2a",
"name": "Audit Generated Content",
"type": "n8n-nodes-base.code",
"position": [
1260,
370
],
"parameters": {
"jsCode": "// This node validates the AI-generated content to ensure quality standards\n// It checks character counts, structure, and content formatting\n\ntry {\n  const aiOutput = $json.output || $json;\n  \n  // Validate AI output structure\n  if (!aiOutput.platform_posts?.Twitter) {\n    throw new Error('Invalid AI output: Missing Twitter platform data');\n  }\n  \n  const twitterData = aiOutput.platform_posts.Twitter;\n  let tweets = [];\n  let contentType = 'unknown';\n  \n  // Handle thread content\n  if (twitterData.thread && Array.isArray(twitterData.thread)) {\n    tweets = twitterData.thread;\n    contentType = 'thread';\n    console.log('Processing thread with ' + tweets.length + ' tweets');\n  }\n  // Handle single tweet content\n  else if (twitterData.single_post) {\n    tweets = [{\n      tweet_number: 1,\n      post: twitterData.single_post,\n      character_count: twitterData.single_post.length\n    }];\n    contentType = 'single';\n    console.log('Processing single tweet');\n  } else {\n    throw new Error('No valid tweet content found in AI output');\n  }\n  \n  // Validate each tweet\n  const validatedTweets = [];\n  const warnings = [];\n  let criticalErrors = 0;\n  \n  tweets.forEach((tweet, index) => {\n    const tweetNumber = index + 1;\n    const content = tweet.post || '';\n    const charCount = content.length;\n    let tweetHasIssues = false;\n    \n    // Character count validation\n    if (charCount < 240 || charCount > 265) {\n      warnings.push('Tweet ' + tweetNumber + ': ' + charCount + ' characters (recommended 240-265)');\n      // Only count as critical error if severely outside range\n      if (charCount < 216 || charCount > 291) {\n        criticalErrors++;\n        tweetHasIssues = true;\n      }\n    }\n    \n    // Check for numbered format at start (e.g., \"1/\", \"2/\")\n    if (/^\\d+[\\.\\/]/.test(content.trim())) {\n      warnings.push('Tweet ' + tweetNumber + ': Starts with numbering (not recommended)');\n    }\n    \n    validatedTweets.push({\n      ...tweet,\n      tweet_number: tweetNumber,\n      character_count: charCount,\n      has_issues: tweetHasIssues,\n      validation_passed: !tweetHasIssues\n    });\n    \n    console.log('Tweet ' + tweetNumber + ': ' + charCount + ' chars - \"' + content.substring(0, 50) + '...\"');\n  });\n  \n  // Calculate error percentage\n  const errorPercentage = (criticalErrors / tweets.length) * 100;\n  const shouldPass = errorPercentage <= 30; // Pass if 30% or fewer critical errors\n  \n  console.log('Validation summary: ' + criticalErrors + '/' + tweets.length + ' critical errors (' + errorPercentage.toFixed(1) + '%)');\n  console.log('Warnings: ' + warnings.length + ' total warnings');\n  \n  // Only fail if critical errors exceed 30%\n  if (!shouldPass) {\n    throw new Error('Critical validation failed: ' + errorPercentage.toFixed(1) + '% error rate exceeds 30% threshold');\n  }\n  \n  return [{\n    json: {\n      ...aiOutput,\n      content_type: contentType,\n      tweet_count: validatedTweets.length,\n      tweets_array: validatedTweets,\n      validation_summary: {\n        critical_errors: criticalErrors,\n        error_percentage: Math.round(errorPercentage * 10) / 10,\n        warnings: warnings.length,\n        passed_threshold: shouldPass,\n        warning_details: warnings\n      },\n      validation_status: 'passed',\n      processed_at: new Date().toISOString()\n    }\n  }];\n  \n} catch (error) {\n  console.error('Content validation error:', error.message);\n  return [{\n    json: {\n      error: error.message,\n      validation_status: 'failed',\n      processed_at: new Date().toISOString()\n    }\n  }];\n}"
},
"description": "Performs quality checks on AI-generated content: character count validation (240-265 chars), format checking, and structure validation. Allows up to 30% error rate for flexibility. Logs detailed validation results for debugging.",
"typeVersion": 2
},
{
"id": "48628c73-df64-4929-a6a8-55f2f12c3508",
"name": "Quality Approval Gate",
"type": "n8n-nodes-base.if",
"position": [
1480,
340
],
"parameters": {
"options": [],
"conditions": {
"options": {
"version": 1,
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"id": "96348250-726c-457a-8958-955c37e8d52f",
"operator": {
"type": "string",
"operation": "equals"
},
"leftValue": "={{ $json.validation_status }}",
"rightValue": "passed"
}
]
}
},
"description": "Final quality check before sending content for approval. Routes to preview creation if validation passed, or to error handling if content doesn't meet quality standards.",
"typeVersion": 2
},
{
"id": "44b0da94-d647-450c-854a-1b8ba0806b55",
"name": "Alert Generation Failure",
"type": "n8n-nodes-base.telegram",
"position": [
1520,
520
],
"webhookId": "4004b700-3e42-4abd-a1db-d43979a62ffa",
"parameters": {
"text": "\u274c **Content Generation Failed**\n\n{{ $json.error }}\n\nThe AI couldn't generate content that meets quality requirements. This usually happens with very complex or unclear topics.\n\nTips:\n- Try simplifying your topic\n- Be more specific about what you want\n- Try a different format (single vs thread)\n\nPlease try again with a different topic or approach.",
"chatId": "{{ $node['Interpret User Message'].json.chat_id }}",
"additionalFields": []
},
"description": "Notifies the user if content generation fails. Provides helpful tips on how to improve their topic or format choice for better results.",
"typeVersion": 1.2
},
{
"id": "30276c5b-ea66-4447-9421-fc16c2bfef5d",
"name": "Build Preview Text",
"type": "n8n-nodes-base.code",
"position": [
1290,
560
],
"parameters": {
"jsCode": "// Create a formatted preview of the generated content for user approval\nconst tweets = $json.tweets_array;\nconst contentType = $json.content_type;\n\nlet previewText = `\ud83d\udcdd **Generated ${contentType.toUpperCase()} Content**\\n\\n`;\npreviewText += `**Topic:** ${$node['Interpret User Message'].json.topic}\\n`;\npreviewText += `**Format:** ${contentType}\\n`;\npreviewText += `**Post Count:** ${tweets.length}\\n\\n`;\n\n// Add each tweet to the preview\ntweets.forEach((tweet, index) => {\n  const tweetNum = index + 1;\n  previewText += `**Post ${tweetNum}** (${tweet.character_count} chars):\\n`;\n  previewText += `${tweet.post}\\n\\n`;\n});\n\npreviewText += `---\\n**Ready to post?**\\nClick \u2705 to approve or \u274c to cancel`;\n\nreturn [{\n  json: {\n    ...($json),\n    preview_text: previewText\n  }\n}];"
},
"description": "Creates a readable preview of all generated content for user review. Shows the topic, format, character count for each post, and the full content. This allows users to review before posting.",
"typeVersion": 2
},
{
"id": "4ba432c8-9200-4dcb-959e-d6d096cba3fa",
"name": "Send Preview for Approval",
"type": "n8n-nodes-base.telegram",
"position": [
1040,
550
],
"webhookId": "78b25471-88dc-40d2-9d17-c4ba616a359b",
"parameters": {
"chatId": "{{ $node['Interpret User Message'].json.chat_id }}",
"message": "={{ $json.preview_text }}",
"options": {
"appendAttribution": false
},
"operation": "sendAndWait",
"approvalOptions": {
"values": {
"approvalType": "double"
}
}
},
"description": "Sends the content preview to Telegram and waits for user approval. Users can click \u2705 to approve and post the content, or \u274c to cancel. The workflow pauses here until a response is received.",
"typeVersion": 1.2
},
{
"id": "c40d3bc1-e247-4e8c-964a-9a7a7287fcb6",
"name": "Evaluate Approval Choice",
"type": "n8n-nodes-base.if",
"position": [
600,
560
],
"parameters": {
"options": [],
"conditions": {
"options": [],
"combinator": "and",
"conditions": [
{
"operator": {
"type": "boolean",
"operation": "true"
},
"leftValue": "={{ $json.data.approved }}",
"rightValue": true
}
]
}
},
"description": "Routes the workflow based on user's approval decision. If approved (\u2705), proceeds to post the content. If rejected (\u274c), sends a cancellation message.",
"typeVersion": 2
},
{
"id": "ea61caeb-b22e-4169-a2e1-a6922f5b335e",
"name": "Send Cancellation Update",
"type": "n8n-nodes-base.telegram",
"position": [
600,
720
],
"webhookId": "3065fcb6-a88b-4903-bbc2-de83237e3294",
"parameters": {
"text": "\u274c **Content Cancelled**\n\nThe content has been cancelled as requested.\n\nYou can start over by sending a new topic anytime.",
"chatId": "={{ $node['Interpret User Message'].json.chat_id }}",
"additionalFields": []
},
"description": "Confirms to the user that their content has been cancelled and won't be posted. Encourages them to try again with a new topic.",
"typeVersion": 1.2
},
{
"id": "6a425708-64be-4784-9222-1bf4baeeee0d",
"name": "Split Posts for Release",
"type": "n8n-nodes-base.splitOut",
"position": [
380,
540
],
"parameters": {
"options": [],
"fieldToSplitOut": "tweets_array"
},
"description": "Separates the array of posts into individual items for sequential posting. This is essential for threads, as each post needs to be published separately and linked together.",
"typeVersion": 1
},
{
"id": "591278b0-cbaa-4b19-9f21-b9cea1bf496d",
"name": "Optional Web Research",
"type": "@tavily/n8n-nodes-tavily.tavilyTool",
"position": [
1160,
150
],
"parameters": {
"query": "={{ $fromAI('Query', '', 'string') }}",
"options": []
},
"description": "Optional research tool that the AI can use to gather current information about the topic. Useful for trending topics, news, or fact-checking. Requires Tavily API credentials.",
"typeVersion": 1
},
{
"id": "7aaa1b89-a52e-4629-9a1f-298c1ff5b5f8",
"name": "Primary Language Model",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenRouter",
"position": [
930,
120
],
"parameters": {
"model": "openai/gpt-4o",
"options": []
},
"description": "The AI model used for content generation. Default is GPT-4 via OpenRouter. You can change this to other models like Claude, Gemini, or any model supported by OpenRouter. Model choice affects content quality and style.",
"typeVersion": 1
},
{
"id": "ecbaf1e6-f852-4faa-ad06-231748c335b0",
"name": "Combine Approval Data",
"type": "n8n-nodes-base.merge",
"position": [
820,
600
],
"parameters": {
"mode": "combine",
"options": [],
"combineBy": "combineByPosition"
},
"description": "Combines the content data with the approval response to pass all necessary information to the next steps.",
"typeVersion": 3.2
},
{
"id": "622b3d5c-b200-4f06-927b-5b1364227c57",
"name": "Send Publish Confirmation",
"type": "n8n-nodes-base.telegram",
"position": [
0,
610
],
"webhookId": "49374cd3-483f-4934-ab49-a33e2750beed",
"parameters": {
"text": "\u2705 **Content Published Successfully!**\n\nLinkedIn: {{ $json.results.linkedin.success ? 'Posted' : 'Failed' }}\nTwitter/X: {{ $json.results.x.success ? 'Posted' : 'Failed' }}\n\nYour content is now live on the selected platforms. Check your accounts to see the posts and monitor engagement.",
"chatId": "{{ $node['Interpret User Message'].json.chat_id }}",
"additionalFields": {
"appendAttribution": false
}
},
"description": "Sends a final confirmation message showing which platforms successfully received the content. Helps you track posting status and troubleshoot any platform-specific issues.",
"typeVersion": 1.2
},
{
"id": "125aba9a-b320-4349-b5d0-21fb4099941a",
"name": "Publish to Social Channels",
"type": "n8n-nodes-upload-post.uploadPost",
"position": [
180,
570
],
"parameters": {
"user": "{{ $credentials.username }}",
"title": "={{ $json.post }}",
"platform": [
"x",
"linkedin"
],
"operation": "uploadText",
"xReplySettings": "everyone"
},
"description": "Posts the content to Twitter/X and LinkedIn. Configure which platforms to use in the parameters. For threads, posts are published sequentially with proper reply chains on Twitter/X.",
"typeVersion": 1
}
],
"active": false,
"pinData": [],
"settings": {
"callerPolicy": "workflowsFromSameOwner",
"executionOrder": "v1"
},
"versionId": null,
"connections": {
"Interpret User Message": {
"main": [
[
{
"node": "Route Valid Input",
"type": "main",
"index": 0
}
]
]
},
"Scheduled Launch Trigger": {
"main": [
[
{
"node": "Generate Run Timestamp",
"type": "main",
"index": 0
}
]
]
},
"Primary Language Model": {
"ai_languageModel": [
[
{
"node": "AI Post Composer",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Evaluate Approval Choice": {
"main": [
[
{
"node": "Split Posts for Release",
"type": "main",
"index": 0
}
],
[
{
"node": "Send Cancellation Update",
"type": "main",
"index": 0
}
]
]
},
"Combine Approval Data": {
"main": [
[
{
"node": "Evaluate Approval Choice",
"type": "main",
"index": 0
}
]
]
},
"Shape AI Response": {
"ai_outputParser": [
[
{
"node": "AI Post Composer",
"type": "ai_outputParser",
"index": 0
}
]
]
},
"AI Post Composer": {
"main": [
[
{
"node": "Audit Generated Content",
"type": "main",
"index": 0
}
]
]
},
"Quality Approval Gate": {
"main": [
[
{
"node": "Build Preview Text",
"type": "main",
"index": 0
}
],
[
{
"node": "Alert Generation Failure",
"type": "main",
"index": 0
}
]
]
},
"Verify Reply Format": {
"main": [
[],
[
{
"node": "Interpret User Message",
"type": "main",
"index": 0
}
]
]
},
"Build Preview Text": {
"main": [
[
{
"node": "Send Preview for Approval",
"type": "main",
"index": 0
},
{
"node": "Combine Approval Data",
"type": "main",
"index": 0
}
]
]
},
"Route Valid Input": {
"main": [
[
{
"node": "AI Post Composer",
"type": "main",
"index": 0
}
],
[
{
"node": "Notify Input Error",
"type": "main",
"index": 0
}
]
]
},
"Generate Run Timestamp": {
"main": [
[
{
"node": "Telegram Topic Request",
"type": "main",
"index": 0
}
]
]
},
"Send Publish Confirmation": {
"main": [
[]
]
},
"Await Telegram Reply": {
"main": [
[
{
"node": "Verify Reply Format",
"type": "main",
"index": 0
}
]
]
},
"Split Posts for Release": {
"main": [
[
{
"node": "Publish to Social Channels",
"type": "main",
"index": 0
}
]
]
},
"Audit Generated Content": {
"main": [
[
{
"node": "Quality Approval Gate",
"type": "main",
"index": 0
}
]
]
},
"Publish to Social Channels": {
"main": [
[
{
"node": "Send Publish Confirmation",
"type": "main",
"index": 0
}
]
]
},
"Optional Web Research": {
"ai_tool": [
[
{
"node": "AI Post Composer",
"type": "ai_tool",
"index": 0
}
]
]
},
"Send Preview for Approval": {
"main": [
[
{
"node": "Combine Approval Data",
"type": "main",
"index": 1
}
]
]
}
}
}