✨🩷Automated Social Media Content Publishing Factory + System Prompt Composition — AI Product | Success.
✨🩷Automated Social Media Content Publishing Factory + System Prompt Composition ✨🩷Automated Social Media Content Publishing Factory + System Prompt Composition — free, ready-to-import n8n workflow (100 nodes, Telegram).
AI Product Reusable license
from $0
Understand this workflow before you use it.
Structure unavailable No issues found by static checks Health 96/100 Workflow structure could not be fully reconstructed from the source file The source file lists the steps but not how they connect. Steps, integrations and security checks are analyzed; execution order and structure-based checks are not. This is a limitation of the file, not necessarily a problem with the workflow.
This workflow starts from Execute Workflow Trigger and works with chat messaging, content publishing, custom code, documents, email and files.
Sale models Live demo Payments run through a deterministic mock provider in this environment — no real money moves.
**✨🩷Automated Social Media Content Publishing Factory + System Prompt Composition**
Category: Telegram · 100 nodes
Nodes/integrations used: executeWorkflowTrigger, extractFromFile, facebookGraphApi, gmail, googleDocs, googleDrive, httpRequest, linkedIn
How to use: download the JSON below, then in n8n choose Import from File (or open the demo link, copy the JSON, and paste with Ctrl+V into the n8n canvas). Add your own credentials and activate.
Source: Zie619/n8n-workflows (MIT). Credentials were removed and files modified for redistribution — see the library's ATTRIBUTION_AND_LICENSES.md for full license text.
✨🩷Automated Social Media Content Publishing Factory + System Prompt Composition
from $0
Sign in to buy
Steps 57
Integrations 7
Connections Unavailable
Complexity Expert
Technical health 96/100
Security None found Facebook Gmail Google Docs Google Drive LinkedIn Telegram Twitter Workflow structure Steps and detected references (no diagram) Execution order can't be reliably reconstructed from this file, so no diagram is shown. Here is what the workflow contains.
36 × Logic 4 × Other 4 × HTTP 4 × Messaging 3 × Storage 2 × Code 2 × App 1 × File 1 × Flow control When chat message received · No-Op X-Twiter · No-Op Instagram · No-Op Window Buffer Memory · No-Op When Executed by Another Workflow · Execute Workflow Trigger Facebook · No-Op LinkedIn · No-Op Short · No-Op YouTube Short · No-Op pollinations.ai1 · HTTP Request Save Image to imgbb.com · HTTP Request Gmail · Gmail + 17 more steps
Detected references These steps name another step whose data they read. That shows a data dependency, not the order the steps run in.
X-Twiter reads data from When chat message received Instagram reads data from When chat message received Facebook reads data from When chat message received LinkedIn reads data from When chat message received Short reads data from When chat message received YouTube Short reads data from When chat message received Gmail reads data from Social Content Instragram Post reads data from Social Media Publishing Router Gmail User for Approval reads data from Extract as JSON Schema reads data from When Executed by Another Workflow Social Post JSON reads data from When Executed by Another Workflow Social Post JSON reads data from Merge Social Post JSON reads data from Security Nothing to review 0 Critical0 High0 Medium0 Low0 InfoStatic checks found nothing that needs review. This is not a guarantee of safety.
Health How the technical score is made up Overall 96/100 .
Technical hygiene signals detected statically from the workflow file. Not a guarantee of correctness or fitness for a particular use.
Execution profile What one run touches Starts from: Execute Workflow Trigger
HTTP requests 4
File storage operations 3
Messages sent 4
Custom code steps 2 Loops and branching can't be measured without the workflow's connections.
Documentation Generated from the workflow's structure What it does This workflow starts from Execute Workflow Trigger and works with chat messaging, content publishing, custom code, documents, email and files.
Services involved: Facebook Graph Api, Gmail, Google Docs, Google Drive, Linked In, Telegram and Twitter.
This description is generated from the workflow's node types and wiring. It does not interpret each node's configuration.
Inputs Data enters through the trigger(s) below.
When Executed by Another Workflow (Execute Workflow Trigger) Main flow This file does not contain its real connections, so the execution order cannot be documented.
It contains: 36 × logic, 4 × generic, 4 × http, 4 × messaging, 3 × storage, 2 × code, 2 × productivity, 1 × file, 1 × flow.
Some steps name another step whose data they read. This shows data dependencies only, not the order steps run in:
X-Twiter (No-Op) reads data from When chat message received (No-Op) Instagram (No-Op) reads data from When chat message received (No-Op) Facebook (No-Op) reads data from When chat message received (No-Op) LinkedIn (No-Op) reads data from When chat message received (No-Op) Short (No-Op) reads data from When chat message received (No-Op) YouTube Short (No-Op) reads data from When chat message received (No-Op) Gmail reads data from Social Content (Set) Instragram Post (Facebook Graph Api) reads data from Social Media Publishing Router (Switch) Gmail User for Approval (Gmail) reads data from Extract as JSON (Extract From File) Schema (Set) reads data from When Executed by Another Workflow (Execute Workflow Trigger) Outputs Without connection data, final outputs can't be identified precisely. These nodes write to external services:
Gmail Social Media Schema (Google Docs) Social Media System Prompt (Google Docs) Gmail User for Approval (Gmail) Save Image to Google Drive (Google Drive) Save Social Post to Google Drive (Google Drive) Telegram Success Message (Optional) (Telegram) Telegram Error Message (Optional) (Telegram) Get Social Post from Google Drive (Google Drive) Requirements No credentials are attached in this file. You will need your own n8n credentials for each service below.
Gmail Google Docs Twitter Facebook Graph Api Linked In Google Drive Telegram Setup Import the JSON file into n8n (Workflows → Import from File). Create credentials for each service and select them on the matching nodes. Set environment variable(s): API_BASE_URL, BASE_URL, IMGBB_API_KEY, TELEGRAM_CHAT_ID, WEBHOOK_URL. Reconnect the nodes in the n8n editor: this file's original connections are missing. Run it once manually with test data before activating. Important considerations 7 node(s) retry or continue on failure.
There is no Error Trigger in this workflow.
Some external calls have no retry or fallback Generated automatically from the workflow's structure. Verify behaviour in n8n before relying on it.
Optimization ideas Advisory suggestions Potential optimization · high confidence
No-op placeholder nodes
19 "No Operation" nodes do nothing at runtime.
Possible impact: Cleaner graph; no runtime change.
No-op nodes are sometimes kept deliberately as visual end markers.
Automated static analysis (engine 1.1.0). Nothing was executed. Not a guarantee of correctness or safety.
The seller has not attached downloadable files yet.
Uploaded by the seller and security-scanned before any buyer can download them.
Documentation
LeadBot 24h — WhatsApp AI Lead Qualification Bot — free, ready-to-import n8n workflow (6 nodes, WhatsApp).
AI Product Reusable
Social Media Schema
· Google Docs
Social Media System Prompt · Google Docs
gpt-40-mini · No-Op
Instagram Image · HTTP Request
X Post · Twitter
Instragram Post · Facebook Graph Api
Facebook Post · Facebook Graph Api
LinkedIn Post · Linked In
Gmail User for Approval · Gmail
Get Social Post Image · HTTP Request
gpt-40-mini1 · No-Op
gpt-4o-mini · No-Op
Schema · Set
System Prompt · Set
Parse Schema · Code
Parse System Prompt · Code
Compose Prompt & Schema · Set
Social Media Content Creator · No-Op
Merge Prompts and Schema · Merge
Social Content · Set
Save Image to Google Drive · Google Drive
Merge · Merge
Save Social Post to Google Drive · Google Drive
Google Drive Image Meta · Set
Social Post JSON · Set
Respond with Google Drive Id · Set
Telegram Success Message (Optional) · Telegram
Telegram Error Message (Optional) · Telegram Social Content
X Response reads data from Social Media Publishing Router
Instagram Response reads data from Social Media Publishing Router Be the first to review this product.
