January 22, 2026

Telegram to LinkedIn, approve posts then publish

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Last-minute LinkedIn writing is a quiet productivity killer. You either ship something rushed, or you skip posting, then spend the week “meaning to get back to it.”

Marketing managers feel it when content calendars slip. A founder feels it when visibility drops. And consultants trying to stay top-of-mind get hit hardest. This Telegram LinkedIn automation creates drafts for you, sends them for approval, then publishes at a smart time so you stay consistent without losing control.

You’ll learn what the workflow does, what you need to run it, and how the approval-and-publish loop works end-to-end.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Telegram to LinkedIn, approve posts then publish

Click to explore

flowchart LR

    subgraph sg0["Scheduled Run Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Run Trigger", pos: "b", h: 48 }
        n1@{ icon: "mdi:play-circle", form: "rounded", label: "Manual Execution Start", 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/code.svg' width='40' height='40' /></div><br/>Compute Run Day"]
        n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Validate Run Day", pos: "b", h: 48 }
        n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Draft Prompt Set", 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/>Select Random Prompt"]
        n6@{ icon: "mdi:robot", form: "rounded", label: "Generate AI Draft", 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/code.svg' width='40' height='40' /></div><br/>Pick Posting Time"]
        n8["<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 Draft for Approval"]
        n9@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Approval Gate", pos: "b", h: 48 }
        n10@{ icon: "mdi:cog", form: "rounded", label: "Delay Until Scheduled", pos: "b", h: 48 }
        n11["<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/>Publish LinkedIn Post"]
        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/>Notify Post Live"]
        n2 --> n3
        n4 --> n5
        n3 --> n4
        n7 --> n8
        n11 --> n12
        n5 --> n6
        n6 --> n7
        n0 --> n2
        n9 --> n10
        n10 --> n11
        n8 --> n9
        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 n0,n1 trigger
    class n6 ai
    class n3,n9 decision
    class n2,n5,n7 code
    classDef customIcon fill:none,stroke:none
    class n2,n5,n7,n8,n11,n12 customIcon

Why This Matters: LinkedIn Consistency Without Daily Writing

LinkedIn rewards consistency, but consistency is hard when every post starts from a blank page. You open a doc, stare at it, and suddenly it’s 30 minutes later and you’ve written two sentences you don’t even like. Then the day gets busy. You tell yourself you’ll post tomorrow, and “tomorrow” turns into next week. Even when you do write, you still have to decide when to publish, copy it into LinkedIn, and hope you didn’t leave in a weird formatting glitch or unfinished thought.

It adds up fast. Here’s where it breaks down in real life.

Writing one decent post can easily take about 45 minutes when you include topic choice, drafting, and edits.
Posts get skipped because you don’t trust an auto-publisher without a final human check.
When you do publish, timing becomes guesswork, so you end up posting whenever you remember.
Repetitive prompts create repetitive posts, which is how your content starts sounding like everyone else.

What You’ll Build: Draft, Approve in Telegram, Then Publish on LinkedIn

This workflow turns LinkedIn posting into a simple approval routine. It starts on a schedule (or manually) and checks what day it is, so you can automatically avoid posting Friday through Sunday if that fits your strategy. Next, it pulls from a set of pre-written prompts you keep inside the workflow, then randomly selects one so the content doesn’t feel copy-pasted. That prompt goes to OpenAI, which generates a clean LinkedIn draft. The draft gets delivered to you in Telegram for review, where you approve or reject it. If you approve, the workflow picks a randomized posting time, waits until that slot, publishes to your LinkedIn account, and then messages you again to confirm the post is live.

The flow is simple: schedule triggers creation, OpenAI drafts the post, Telegram acts as your control panel, and LinkedIn is the final destination. You stay in charge, but you’re no longer doing the busywork every day.

What You’re Building

What Gets Automated

What You’ll Achieve

Scheduled or manual runs that skip weekends automatically.
Rotation of multiple prompts so drafts don’t look repetitive.
OpenAI draft generation that outputs ready-to-post text.
Telegram approval, followed by delayed publishing to LinkedIn.

Cut “write + format + post” from about 45 minutes to roughly 5 minutes of review.
Fewer missed posts because approval happens where you already live (Telegram).
More consistent publishing times, without setting a rigid calendar.
Cleaner brand voice over time because prompts become a reusable asset.
Peace of mind: nothing posts unless you approve it.

Expected Results

Say you post 4 times per week. Manually, if each post takes about 45 minutes to draft, polish, and publish, that’s roughly 3 hours a week just to keep the habit alive. With this workflow, you’ll spend a couple minutes approving each Telegram message, so maybe 10 minutes total, while the automation handles drafting, timing, and publishing. That’s close to 3 hours back in a normal week, and your posting stays steady.

Before You Start

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Telegram for approval messages and notifications.
LinkedIn to publish posts to your profile or page.
OpenAI API key (get it from the OpenAI Platform API keys page).

Skill level: Beginner. You will connect accounts, paste an API key, and edit a few prompts.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A scheduled (or manual) run kicks things off. The workflow can run from a Schedule Trigger, or you can fire it manually when you want a fresh draft on demand.

It checks the day and decides if it should post. A small logic step figures out the day of the week, then an “allowed?” check can skip Friday through Sunday so you don’t accidentally publish on days you’ve chosen to avoid.

Prompts are prepared, then one gets picked at random. You keep a set of prompt templates inside the workflow, and a random selection step rotates them. This is a big deal for consistency because it helps your AI drafts feel less like they came from the same mold.

OpenAI generates a draft, then Telegram asks you to approve it. You’ll receive the proposed LinkedIn post in Telegram, where you can approve or reject. If you approve, the workflow chooses a posting time, waits until then, publishes via the LinkedIn integration, and finally pings you that it went live.

You can easily modify the prompt set to match your niche, or change the “no posting” days based on your audience. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the schedule trigger

Set up the automated schedule and manual start options that kick off the workflow.

Add and configure Scheduled Run Trigger with a cron rule.
Set the Expression to 0 8 * * 1-4 to run at 08:00 UTC Monday–Thursday.
Add Manual Execution Start to enable on-demand testing and manual runs.
Connect both Scheduled Run Trigger and Manual Execution Start to Compute Run Day.

Tip: Keep Manual Execution Start connected during setup so you can run tests without waiting for the schedule.

Step 2: Configure day validation and prompt selection

Use a date check to skip unwanted days and select a randomized prompt for the AI draft.

In Compute Run Day, keep the JavaScript as provided to calculate skipToday based on Central Time.
In Validate Run Day, set the Boolean condition to ={{$json["skipToday"]}} with operator True.
Connect the false output of Validate Run Day to Draft Prompt Set so posting continues only when allowed.
In Draft Prompt Set, confirm all prompt fields (prompt1–prompt6) are present and match your desired content themes.
In Select Random Prompt, keep the code that selects a random prompt from the six options.

⚠️ Common Pitfall: If Validate Run Day is wired from the true output by mistake, the workflow will only run on days you intended to skip.

Step 3: Set up AI draft generation

Generate the LinkedIn post text using OpenAI with the selected prompt.

Open Generate AI Draft and select the model chatgpt-4o-latest.
Set the message content to ={{ $('Select Random Prompt').item.json.selectedPrompt }}.
Credential Required: Connect your openAiApi credentials.
Connect Select Random Prompt → Generate AI Draft.

Step 4: Configure scheduling and approval workflow

Pick a randomized posting time, send the draft for Telegram approval, and pause until the scheduled time.

In Pick Posting Time, keep the JavaScript that selects from ['09:00', '11:00', '15:00'] and outputs postTimeUTC_ISO.
Connect Generate AI Draft → Pick Posting Time → Send Draft for Approval.
In Send Draft for Approval, set Operation to sendAndWait and keep the message template with {{ $('Generate AI Draft').item.json.message.content }} and {{ $json.postTimeCentral }}.
Credential Required: Connect your telegramApi credentials.
In Approval Gate, set the boolean condition to ={{ $json.data.approved }} with operator True.
In Delay Until Scheduled, set Resume to specificTime and Date & Time to ={{ $('Pick Posting Time').item.json.postTimeUTC_ISO }}.

Tip: Ensure the Telegram approval prompt is sent to a valid chatId so the approval flow can continue.

Step 5: Configure LinkedIn publishing and notifications

Post the approved draft to LinkedIn and notify the team when it goes live.

In Publish LinkedIn Post, set Text to ={{ $('Generate AI Draft').item.json.message.content }}.
Set Person to your LinkedIn profile ID (replace [YOUR_ID]).
Credential Required: Connect your linkedInOAuth2Api credentials.
Connect Delay Until Scheduled → Publish LinkedIn Post → Notify Post Live.
In Notify Post Live, set Text to Personal LinkedIn Post Active and chatId to your Telegram ID.
Credential Required: Connect your telegramApi credentials.

Step 6: Test and Activate Your Workflow

Validate end-to-end behavior and enable the scheduled automation.

Click Execute Workflow on Manual Execution Start to run a test without waiting for the schedule.
Confirm that Send Draft for Approval delivers a Telegram message containing the draft and scheduled time.
Approve the draft to ensure Approval Gate passes and Delay Until Scheduled holds until the computed time.
Verify that Publish LinkedIn Post posts successfully and Notify Post Live sends the confirmation message.
Toggle the workflow to Active so Scheduled Run Trigger runs on the cron schedule.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

LinkedIn credentials can expire or require the right permissions. If publishing fails, check the LinkedIn credential in n8n first, then confirm the connected account still has posting access.
If you’re using Wait nodes or external timing logic, 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.

Quick Answers

What’s the setup time for this Telegram LinkedIn automation?

About 30 minutes if your accounts are ready.

Is coding required for this Telegram LinkedIn automation?

No. You’ll mostly connect accounts and edit prompts, and the included logic already handles day checks and timing.

Is n8n free to use for this Telegram LinkedIn 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 OpenAI API costs (often a few cents per draft, depending on model and length).

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 modify this Telegram LinkedIn automation workflow for different use cases?

Yes, and you should. The quickest win is editing the prompts in the “Draft Prompt Set” step and keeping 10–20 variations so the “Select Random Prompt” step has real variety. You can also change the day filter in the “Validate Run Day” check to match your posting rules, then adjust the “Pick Posting Time” logic if you want a fixed time instead of a random slot. If you’d rather approve in Slack, swap the Telegram approval message for a Slack approval flow and keep the rest.

Why is my Telegram connection failing in this workflow?

Usually it’s the bot setup, not n8n. Confirm your Telegram bot token is correct, the bot has been started (you sent it a message), and you’re using the right chat ID or user ID in the Telegram node. If it worked once and stopped, rotate the token in BotFather and update the credential in n8n. Rarely, it’s simply that the workflow is sending to a different chat than the one you’re watching.

What volume can this Telegram LinkedIn automation workflow process?

Plenty for typical LinkedIn cadence.

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

Often, yes, because approvals plus timing logic get clunky fast in simpler tools. n8n is better when you want branching (approve vs. reject), day-based rules (skip weekends), and custom logic for picking prompts or post times without paying extra for every “path.” It also gives you the option to self-host, which matters if you want lots of runs without worrying about task limits. Zapier or Make can still be fine if you only want a basic “generate draft → send to me” setup. Talk to an automation expert if you’re not sure which fits.

Once this is running, LinkedIn stops being a daily scramble and becomes a quick approval habit. Set it up once, then get back to work that actually moves the needle.

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": "",
"meta": {
"instanceId": "d97c20dfca28c6dac534de3279b5ac7f967bbeeb7b9206e34dff14fc157de827"
},
"name": "Automated LinkedIn Posting System",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-6451",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1125,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "c75ea360-ed01-4aee-bbce-d44889c1105b",
"name": "Scheduled Run Trigger",
"type": "n8n-nodes-base.scheduleTrigger",
"position": [
20,
270
],
"parameters": {
"rule": {
"interval": [
{
"field": "cronExpression",
"expression": "0 8 * * 1-4"
}
]
}
},
"typeVersion": 1.2
},
{
"id": "c770a05a-41bf-4934-89d5-490cb0636d37",
"name": "Manual Execution Start",
"type": "n8n-nodes-base.manualTrigger",
"position": [
5,
120
],
"parameters": [],
"typeVersion": 1
},
{
"id": "f78ec2b0-8a6d-471b-8e34-21c9ddd3112f",
"name": "Compute Run Day",
"type": "n8n-nodes-base.code",
"position": [
155,
235
],
"parameters": {
"jsCode": "const now = new Date();\nconst utcDay = now.getUTCDay(); // Sunday = 0, Saturday = 6\n\n// Convert UTC day to Central time (-5 hours)\nconst utcHour = now.getUTCHours();\nconst centralHour = utcHour - 5;\n\n// If converting to previous day (before midnight Central)\nlet centralDay = utcDay;\nif (centralHour < 0) {\n  centralDay = utcDay - 1;\n  if (centralDay < 0) centralDay = 6; // Wrap Sunday (0) back to Saturday (6)\n}\n\nconst skipDays = [0, 5, 6]; // Sunday, Friday, Saturday\nconsole.log('UTC Day:', utcDay);\nconsole.log('Central Day:', centralDay);\nreturn [{ json: { skipToday: skipDays.includes(centralDay) } }];\n"
},
"typeVersion": 2
},
{
"id": "6231c53d-97df-4f81-8a2f-7a3cf1709fc5",
"name": "Validate Run Day",
"type": "n8n-nodes-base.if",
"position": [
420,
175
],
"parameters": {
"options": [],
"conditions": {
"options": {
"version": 2,
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"id": "a347036c-523f-44a1-ba1b-01b5fa002018",
"operator": {
"type": "boolean",
"operation": "true",
"singleValue": true
},
"leftValue": "={{$json[\"skipToday\"]}}",
"rightValue": ""
}
]
}
},
"typeVersion": 2.2
},
{
"id": "b839fc4f-66db-48dc-ad14-61a28b245753",
"name": "Draft Prompt Set",
"type": "n8n-nodes-base.set",
"position": [
580,
220
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"id": "5a22e09b-59ba-4c9d-98a4-1558025fe417",
"name": "prompt1",
"type": "string",
"value": "Create engaging, thought-provoking LinkedIn posts that drive engagement, increase followers, and establish authority in UCaaS, AI, Contact Center, and tech business spaces.\n\nTone & Style:\n- Conversational, but professional\n- Human\u2014not robotic or overly polished\n- Incorporates strategic questions to drive comments\n- Uses emojis thoughtfully to add personality, not clutter\n- Mixes storytelling, insights, trends, and opinions\n- Do not use Markdown or any formatting symbols (such as ** for bold or _ for italics). Write plain text only.\n- Don't summarize the type of post; this is going straight to LinkedIn, and I won't be editing it. Don't add \"post format\", \"tone\", \"focus\", etc.\n- Remember prior articles and focus on not reusing similar topics frequently\n\n1.Start with a strong hook or bold statement\n2.Share insight, observation, or story (1-3 short paragraphs max)\n3.End with a question or call-to-engage\n4.Rotate between formats: POV, predictions, lessons, thought-starters, fun/engagement posts\n\nContextual Guidance:\n-Emphasize trends shaping the industry (AI, CX, UCaaS)\n-Show awareness of how AI is changing work but balance hype with practicality\n-Encourage industry peers to comment by asking reflective or polarizing questions\n\nAvoid sounding AI-generated or generic\u2014write like someone who\u2019s been in the meetings, in the trenches.\nIncorporate emojis to keep it visually engaging but not juvenile.\n\nThe post should feel like it's written by a tech-savvy executive or thought leader who understands current trends in AI, contact centers, and unified communications.\n\nWrite a thought leadership post about the future of AI in CX. Keep it under 150 words."
},
{
"id": "5e4a38a3-9ab6-4eaa-a670-e0403d1f5593",
"name": "prompt2",
"type": "string",
"value": "Create engaging, thought-provoking LinkedIn posts that drive engagement, increase followers, and establish authority in UCaaS, AI, Contact Center, and tech business spaces.\n\nTone & Style:\n- Conversational, but professional\n- Human\u2014not robotic or overly polished\n- Incorporates strategic questions to drive comments\n- Uses emojis thoughtfully to add personality, not clutter\n- Mixes storytelling, insights, trends, and opinions\n- Do not use Markdown or any formatting symbols (such as ** for bold or _ for italics). Write plain text only.\n- Don't summarize the type of post; this is going straight to LinkedIn, and I won't be editing it. Don't add \"post format\", \"tone\", \"focus\", etc.\n- Remember prior articles and focus on not reusing similar topics frequently\n\n1.Start with a strong hook or bold statement\n2.Share insight, observation, or story (1-3 short paragraphs max)\n3.End with a question or call-to-engage\n4.Rotate between formats: POV, predictions, lessons, thought-starters, fun/engagement posts\n\nContextual Guidance:\n-Emphasize trends shaping the industry (AI, CX, UCaaS)\n-Show awareness of how AI is changing work but balance hype with practicality\n-Encourage industry peers to comment by asking reflective or polarizing questions\n\nAvoid sounding AI-generated or generic\u2014write like someone who\u2019s been in the meetings, in the trenches.\nIncorporate emojis to keep it visually engaging but not juvenile.\n\nThe post should feel like it's written by a tech-savvy executive or thought leader who understands current trends in AI, contact centers, and unified communications.\n\nCreate a LinkedIn post about how AI is transforming customer support. Make it conversational."
},
{
"id": "26a18c26-dd92-4288-90ba-2b6c0ec239a0",
"name": "prompt3",
"type": "string",
"value": "Create engaging, thought-provoking LinkedIn posts that drive engagement, increase followers, and establish authority in UCaaS, AI, Contact Center, and tech business spaces.\n\nTone & Style:\n- Conversational, but professional\n- Human\u2014not robotic or overly polished\n- Incorporates strategic questions to drive comments\n- Uses emojis thoughtfully to add personality, not clutter\n- Mixes storytelling, insights, trends, and opinions\n- Don't summarize the type of post; this is going straight to LinkedIn, and I won't be editing it. Don't add \"post format\", \"tone\", \"focus\", etc.\n- Remember prior articles and focus on not reusing similar topics frequently\n\n1.Start with a strong hook or bold statement\n2.Share insight, observation, or story (1-3 short paragraphs max)\n3.End with a question or call-to-engage\n4.Rotate between formats: POV, predictions, lessons, thought-starters, fun/engagement posts\n\nContextual Guidance:\n-Emphasize trends shaping the industry (AI, CX, UCaaS)\n-Show awareness of how AI is changing work but balance hype with practicality\n-Encourage industry peers to comment by asking reflective or polarizing questions\n\nAvoid sounding AI-generated or generic\u2014write like someone who\u2019s been in the meetings, in the trenches.\nIncorporate emojis to keep it visually engaging but not juvenile.\n\nThe post should feel like it's written by a tech-savvy executive or thought leader who understands current trends in AI, contact centers, and unified communications.\n\nDraft a short, engaging post about the importance of integrating AI platforms for better CX insights."
},
{
"id": "f1f1c721-2e48-4243-9094-3b9b264ed680",
"name": "prompt4",
"type": "string",
"value": "Create engaging, thought-provoking LinkedIn posts that drive engagement, increase followers, and establish authority in UCaaS, AI, Contact Center, and tech business spaces.\n\nTone & Style:\n- Conversational, but professional\n- Human\u2014not robotic or overly polished\n- Incorporates strategic questions to drive comments\n- Uses emojis thoughtfully to add personality, not clutter\n- Mixes storytelling, insights, trends, and opinions\n- Do not use Markdown or any formatting symbols (such as ** for bold or _ for italics). Write plain text only.\n- Don't summarize the type of post; this is going straight to LinkedIn, and I won't be editing it. Don't add \"post format\", \"tone\", \"focus\", etc.\n- Remember prior articles and focus on not reusing similar topics frequently\n\n1.Start with a strong hook or bold statement\n2.Share insight, observation, or story (1-3 short paragraphs max)\n3.End with a question or call-to-engage\n4.Rotate between formats: POV, predictions, lessons, thought-starters, fun/engagement posts\n\nContextual Guidance:\n-Emphasize trends shaping the industry (AI, CX, UCaaS)\n-Show awareness of how AI is changing work but balance hype with practicality\n-Encourage industry peers to comment by asking reflective or polarizing questions\n\nAvoid sounding AI-generated or generic\u2014write like someone who\u2019s been in the meetings, in the trenches.\nIncorporate emojis to keep it visually engaging but not juvenile.\n\nThe post should feel like it's written by a tech-savvy executive or thought leader who understands current trends in AI, contact centers, and unified communications.\n\nWrite a professional yet informal post about AI trends for customer engagement."
},
{
"id": "3f5c12e4-769b-4be7-ba32-a88f9f714325",
"name": "prompt5",
"type": "string",
"value": "Create engaging, thought-provoking LinkedIn posts that drive engagement, increase followers, and establish authority in UCaaS, AI, Contact Center, and tech business spaces.\n\nTone & Style:\n- Conversational, but professional\n- Human\u2014not robotic or overly polished\n- Incorporates strategic questions to drive comments\n- Uses emojis thoughtfully to add personality, not clutter\n- Mixes storytelling, insights, trends, and opinions\n- Do not use Markdown or any formatting symbols (such as ** for bold or _ for italics). Write plain text only.\n- Don't summarize the type of post; this is going straight to LinkedIn, and I won't be editing it. Don't add \"post format\", \"tone\", \"focus\", etc.\n- Remember prior articles and focus on not reusing similar topics frequently\n\n1.Start with a strong hook or bold statement\n2.Share insight, observation, or story (1-3 short paragraphs max)\n3.End with a question or call-to-engage\n4.Rotate between formats: POV, predictions, lessons, thought-starters, fun/engagement posts\n\nContextual Guidance:\n-Emphasize trends shaping the industry (AI, CX, UCaaS)\n-Show awareness of how AI is changing work but balance hype with practicality\n-Encourage industry peers to comment by asking reflective or polarizing questions\n\nAvoid sounding AI-generated or generic\u2014write like someone who\u2019s been in the meetings, in the trenches.\nIncorporate emojis to keep it visually engaging but not juvenile.\n\nThe post should feel like it's written by a tech-savvy executive or thought leader who understands current trends in AI, contact centers, and unified communications.\n\nShare insights on why AI-driven data is becoming critical for CX leaders in 2025."
},
{
"id": "0d689205-46d9-46de-b296-056c7c5832f0",
"name": "prompt6",
"type": "string",
"value": "Create engaging, thought-provoking LinkedIn posts that drive engagement, increase followers, and establish authority in UCaaS, AI, Contact Center, and tech business spaces.\n\nTone & Style:\n- Conversational, but professional\n- Human\u2014not robotic or overly polished\n- Incorporates strategic questions to drive comments\n- Uses emojis thoughtfully to add personality, not clutter\n- Mixes storytelling, insights, trends, and opinions\n- Do not use Markdown or any formatting symbols (such as ** for bold or _ for italics). Write plain text only.\n- Don't summarize the type of post; this is going straight to LinkedIn, and I won't be editing it. Don't add \"post format\", \"tone\", \"focus\", etc.\n- Remember prior articles and focus on not reusing similar topics frequently\n\n1.Start with a strong hook or bold statement\n2.Share insight, observation, or story (1-3 short paragraphs max)\n3.End with a question or call-to-engage\n4.Rotate between formats: POV, predictions, lessons, thought-starters, fun/engagement posts\n\nContextual Guidance:\n-Emphasize trends shaping the industry (AI, CX, UCaaS)\n-Show awareness of how AI is changing work but balance hype with practicality\n-Encourage industry peers to comment by asking reflective or polarizing questions\n\nAvoid sounding AI-generated or generic\u2014write like someone who\u2019s been in the meetings, in the trenches.\nIncorporate emojis to keep it visually engaging but not juvenile.\n\nThe post should feel like it's written by a tech-savvy executive or thought leader who understands current trends in AI, contact centers, and unified communications.\n\nWrite a post around the CX, CX AI, and UCaaS industry from a business perspective. Use knowledge from the web to stay up to date."
}
]
}
},
"typeVersion": 3.4
},
{
"id": "b1949530-230f-4fad-9c51-cd0e300ad1f5",
"name": "Select Random Prompt",
"type": "n8n-nodes-base.code",
"position": [
875,
190
],
"parameters": {
"jsCode": "const prompts = [\n  $json.prompt1,\n  $json.prompt2,\n  $json.prompt3,\n  $json.prompt4,\n  $json.prompt5,\n  $json.prompt6\n];\nconst randomIndex = Math.floor(Math.random() * prompts.length);\nreturn [{ json: { selectedPrompt: prompts[randomIndex] } }];"
},
"typeVersion": 2
},
{
"id": "3a95e7c1-471d-46a9-8c96-71e83ce06499",
"name": "Generate AI Draft",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
1025,
230
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "chatgpt-4o-latest",
"cachedResultName": "CHATGPT-4O-LATEST"
},
"options": [],
"messages": {
"values": [
{
"content": "={{ $('Select Random Prompt').item.json.selectedPrompt }}"
}
]
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.8
},
{
"id": "2acda2bb-4a00-453a-8b17-b2ea1777b0c9",
"name": "Pick Posting Time",
"type": "n8n-nodes-base.code",
"position": [
1010,
520
],
"parameters": {
"jsCode": "const times = ['09:00', '11:00', '15:00']; // Central Time Options\nconst selectedTime = times[Math.floor(Math.random() * times.length)];\n\n// Extract hours and minutes\nconst [hour, minute] = selectedTime.split(':').map(Number);\n\n// Get current date\nconst now = new Date();\n\n// Create a UTC Date corresponding to selected Central Time\n// Central is UTC-5\nconst postDateUTC = new Date(Date.UTC(\n    now.getFullYear(),\n    now.getMonth(),\n    now.getDate(),\n    hour + 5, // Convert from Central to UTC\n    minute,\n    0,\n    0\n));\n\nreturn [{\n    json: {\n        postTimeCentral: selectedTime,\n        postTimeUTC_ISO: postDateUTC.toISOString()\n    }\n}];"
},
"typeVersion": 2
},
{
"id": "cb914251-dc4a-48b5-af92-6b91e2259304",
"name": "Send Draft for Approval",
"type": "n8n-nodes-base.telegram",
"position": [
855,
565
],
"webhookId": "404b51a4-af26-4d98-aacf-01969d2000ec",
"parameters": {
"chatId": "",
"message": "=Here is your AI-generated LinkedIn post draft:\n\n{{ $('Generate AI Draft').item.json.message.content }}\n\nScheduled Post Time (Central Time): {{ $json.postTimeCentral }}\n\nApprove?\n",
"options": [],
"operation": "sendAndWait",
"approvalOptions": {
"values": {
"approvalType": "double"
}
}
},
"credentials": {
"telegramApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.2
},
{
"id": "62715d75-82de-47b9-96fd-663cdc52558f",
"name": "Approval Gate",
"type": "n8n-nodes-base.if",
"position": [
590,
505
],
"parameters": {
"options": [],
"conditions": {
"options": {
"version": 2,
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"id": "c668e57a-7239-4ba5-94e3-b988ba801a5e",
"operator": {
"type": "boolean",
"operation": "true",
"singleValue": true
},
"leftValue": "={{ $json.data.approved }}",
"rightValue": ""
}
]
}
},
"typeVersion": 2.2
},
{
"id": "ca54dec2-58cd-4d29-a18a-6300eeccc367",
"name": "Delay Until Scheduled",
"type": "n8n-nodes-base.wait",
"position": [
430,
555
],
"webhookId": "50f8954c-e21e-4a44-a465-4ec02919a65b",
"parameters": {
"resume": "specificTime",
"dateTime": "={{ $('Pick Posting Time').item.json.postTimeUTC_ISO }}"
},
"typeVersion": 1.1
},
{
"id": "f132e39a-d6e8-43ab-a476-41a0b1c7bba4",
"name": "Publish LinkedIn Post",
"type": "n8n-nodes-base.linkedIn",
"position": [
135,
515
],
"parameters": {
"text": "={{ $('Generate AI Draft').item.json.message.content }}",
"person": "[YOUR_ID]",
"additionalFields": []
},
"credentials": {
"linkedInOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "acec4d48-7d0b-4867-b0ed-a59128b1184a",
"name": "Notify Post Live",
"type": "n8n-nodes-base.telegram",
"position": [
0,
525
],
"webhookId": "7522fe51-a9dd-4e86-aa56-1cfda7d01ee4",
"parameters": {
"text": "Personal LinkedIn Post Active",
"chatId": "[YOUR_ID]",
"additionalFields": []
},
"credentials": {
"telegramApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.2
}
],
"active": true,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"versionId": "",
"connections": {
"Compute Run Day": {
"main": [
[
{
"node": "Validate Run Day",
"type": "main",
"index": 0
}
]
]
},
"Draft Prompt Set": {
"main": [
[
{
"node": "Select Random Prompt",
"type": "main",
"index": 0
}
]
]
},
"Validate Run Day": {
"main": [
[],
[
{
"node": "Draft Prompt Set",
"type": "main",
"index": 0
}
]
]
},
"Pick Posting Time": {
"main": [
[
{
"node": "Send Draft for Approval",
"type": "main",
"index": 0
}
]
]
},
"Publish LinkedIn Post": {
"main": [
[
{
"node": "Notify Post Live",
"type": "main",
"index": 0
}
]
]
},
"Select Random Prompt": {
"main": [
[
{
"node": "Generate AI Draft",
"type": "main",
"index": 0
}
]
]
},
"Generate AI Draft": {
"main": [
[
{
"node": "Pick Posting Time",
"type": "main",
"index": 0
}
]
]
},
"Scheduled Run Trigger": {
"main": [
[
{
"node": "Compute Run Day",
"type": "main",
"index": 0
}
]
]
},
"Approval Gate": {
"main": [
[
{
"node": "Delay Until Scheduled",
"type": "main",
"index": 0
}
],
[]
]
},
"Delay Until Scheduled": {
"main": [
[
{
"node": "Publish LinkedIn Post",
"type": "main",
"index": 0
}
]
]
},
"Send Draft for Approval": {
"main": [
[
{
"node": "Approval Gate",
"type": "main",
"index": 0
}
]
]
},
"Manual Execution Start": {
"main": [
[
{
"node": "Compute Run Day",
"type": "main",
"index": 0
}
]
]
}
}
}