When should you use it?
- Ideas come to you on your phone
- You post visual explainers
- You want drafts fast
Not for: Breaking news without fact checks; Fully automatic publishing
What do you need, and what do you get?
You need
- Telegram bot
- Research tool
- Design or video generator
- Social accounts
You get
- Draft infographic or slideshow
- Approval message
- Published post
How does it work, step by step?
- Send the topicMessage the bot a topic and audience.
- ResearchCollect facts with sources.
- Pick formatChoose infographic or slideshow.
- Generate asynchronouslyCreate, wait, retrieve.
- Approve then publishReply approve in Telegram before posting.
The prompt
Our own prompt, inspired by u/Minute-Neck486 on r/n8n and written to work in n8n and ChatGPT. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Research {topic} for {audience}. Return 5 facts with source URLs, and choose INFOGRAPHIC or SLIDESHOW with a reason. Write slide or panel text using only those facts.
Inspired by u/Minute-Neck486 on r/n8n: I Built an AI Content Agent in n8n That Researches, Designs & Publishes for Me. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Generated visuals can misstate facts; check numbers.
- Async jobs fail silently; alert on timeouts.
Our take
The create, wait, retrieve pattern is the technical detail worth copying for any slow generation job. Change the end of the flow so publishing waits for a reply from you. Send the topic from Telegram, research, pick format, generate asynchronously, then approve before anything goes public. Confirmations back in chat are fine after publish, not instead of approval. Cap how many posts can queue per day. Fact-check captions that include numbers. Prefer brand-safe image styles. Keep Telegram bot tokens rotated. Do not grant the workflow direct access to every social password; use a scheduler with limited scopes. Review the first week of outputs for voice drift. Pause auto-publish entirely until quality is steady. Log failures of the async generation step so stuck jobs do not silently vanish. Require a source link in every research brief before any graphic is generated from it. Keep a reject button in Telegram that drops the draft without publishing and records why you rejected it.
Where the time goes back: An idea on your phone becomes a reviewed draft without opening a design tool.
FAQ
Why add approval?
Which networks?
Source and credit
Inspired by u/Minute-Neck486 on r/n8n. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I Built an AI Content Agent in n8n That Researches, Designs & Publishes for Me
- Creator
- u/Minute-Neck486 on r/n8n
- Published on
- Original date
- Feb 25, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- n8n
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.