Telegram Content Pipeline
43 node publish engine with Telegram, Drive, Sheets and Make
From idea in Telegram to published post across channels. Draft, asset, approve and publish with a Sheets CMS.
A system that works while you are not looking
This pipeline turns a message in Telegram into a published social post with a proper editorial flow. You send an idea or a draft, the system generates copy, handles images through Drive, stores the post in Sheets as a simple CMS, waits for approval and then publishes through Make to multiple channels. It is ideal for teams that want to move fast but keep approval and tracking in one place instead of scattered chats and drives.
A single chat becomes a controlled publish queue with drafts, assets and status all visible in Sheets.
Outcome
Telegram messages are routed by a Switch. Text ideas go to an AI agent with Anthropic and OpenAI models and a memory window. The agent drafts post copy, checks Sheets for templates and brand guidance, and pulls or stores images via Google Drive. Each post is written to Sheets with status, copy and asset links. A second path handles approvals coming back from Telegram buttons or a Webhook from Make. When approved, a Make webhook is called to publish to the configured channels. Code nodes handle Drive file IDs and Sheet updates, and Telegram confirms each stage back to the editor.
Trigger
Inbound signal starts the flow
Orchestrate
Models, tools and branches run
Deliver
Result logged and returned
Who it is for
Creators, media teams and brands that repurpose one asset into many at scale.
What you save
Hours become minutes per task, handoffs stay consistent in Sheets or CRM, and the workflow file is yours to own. Import, add your keys and run.
More from portfolio