See llms.txt for all machine-readable content.
Blog posts that turn into social packs a human still signs off on. This workflow takes article links from Telegram, blocks duplicate work with a stable content key, quality-checks the LinkedIn, X, newsletter, hook, and pull-quote copy, and queues every pack for review before the hourly sender delivers it.
Last updated: September 2026.
This workflow turns Telegram article links into quality-checked social packs, prevents duplicate work with a stable content key, queues every new pack for human review, and supports scheduled delivery plus a weekly Telegram digest. It uses gpt-6-luna, Google Sheets, and Telegram to make repurposing auditable instead of a one-off AI response.
How are duplicate links handled?
The URL is normalized to remove tracking parameters and fragments, then turned into a stable content_key. If that key is already in the Packs tab, the previous status and timestamp come back instead of another pack being generated.
What happens if the article fetch fails?
It retries once after 60 seconds for 408, 429, and 5xx errors. Other failures are logged to the Errors tab and reported in Telegram.
What if the AI copy misses a channel limit?
Every generated field is parsed and checked against the required fields and channel limits, and a failed quality check gets one AI repair pass before being logged as failed.
How does a pack get published?
Valid packs land in the Packs tab as pending_review with a scheduled time and reviewer notes. An hourly run delivers approved packs whose scheduled_at is due and marks them delivered.
Is there a weekly report?
Every Sunday the Packs and Errors data is combined into weekly pack, failure, approval, delivery, per-day, and per-channel metrics and sent as an AI-written Telegram digest.
Built with n8n. Need an assessment on your business? Feel free to reach out at https://khmuhtadin.com/consultation/