Files
portfolio/docs/TELEGRAM_CMS_QUICKSTART.md
denshooter a36268302c feat: complete telegram cms system with workflows and deployment guide
- Add ULTIMATE-Telegram-CMS-COMPLETE.json with all commands
- Add Docker Event workflows with Gitea integration
- Add comprehensive deployment guide for fresh installs
- Add quick reference and testing checklist
- Include all n8n workflow exports

Commands:
/start, /list, /search, /stats, /preview, /publish, /delete, .review

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-04-02 12:10:07 +02:00

4.1 KiB

🚀 TELEGRAM CMS - QUICK START GUIDE

Installation (5 Minutes)

Step 1: Import Main Workflow

  1. Open n8n: https://n8n.dk0.dev
  2. Click "Workflows" → "Import from File"
  3. Select: n8n-workflows/ULTIMATE-Telegram-CMS-COMPLETE.json
  4. Workflow should auto-activate

Step 2: Verify Credentials

Check these credentials exist (should be auto-mapped):

  • Telegram: DK0_Server
  • Directus: Bearer token RF2Qytq...
  • OpenRouter: Bearer token sk-or-v1-...

Step 3: Test Commands

Open Telegram bot and type:

/start

You should see the dashboard! 🎉


📋 All Commands

Command Description Example
/start Main dashboard /start
/list projects Show draft projects /list projects
/list books Show pending reviews /list books
/search <term> Search everywhere /search nextjs
/stats Analytics dashboard /stats
/preview <ID> Preview item (EN+DE) /preview 42
/publish <ID> Publish to live site /publish 42
/delete <ID> Delete item /delete 42
/deletereview <ID> Delete book review /deletereview 3
.review <HC_ID> <RATING> <TEXT> Create book review .review427565 4 Great!

🔧 Companion Workflows (Auto-Import)

These workflows work together with the main CMS:

1. Docker Event Workflow

File: Docker Event.json (KEEP ACTIVE)

  • Auto-detects new container deployments
  • AI generates project descriptions
  • Creates drafts in Directus
  • Sends Telegram notification with buttons

2. Book Review Scheduler

File: Book Review.json (KEEP ACTIVE)

  • Runs daily at 7 PM
  • Checks for unreviewed books
  • Sends AI-generated questions
  • You reply with .review command

3. Finished Books Sync

File: finishedBooks.json (KEEP ACTIVE)

  • Runs daily at 6 AM
  • Syncs from Hardcover API
  • Adds new books to Directus

4. Portfolio Status API

File: portfolio-website.json (KEEP ACTIVE)

  • Real-time status endpoint
  • Aggregates: Spotify + Discord + WakaTime
  • Used by website for "Now" section

5. Currently Reading API

File: reading (1).json (KEEP ACTIVE)

  • Webhook endpoint
  • Fetches current books from Hardcover
  • Returns formatted JSON

🎯 Typical Workflows

Publishing a New Project:

  1. Deploy Docker container
  2. Get Telegram notification: "🚀 New Deploy: portfolio-dev"
  3. Click "🤖 Auto-generieren" button
  4. AI creates draft
  5. Get notification: "Draft created (ID: 42)"
  6. Type: /preview 42 to check translations
  7. Type: /publish 42 to go live

Adding a Book Review:

  1. Finish reading book on Hardcover
  2. Get Telegram prompt at 7 PM: "📚 Review this book?"
  3. Reply: .review427565 4 Great world-building but rushed ending
  4. AI generates EN + DE reviews
  5. Get notification: "Review draft created (ID: 3)"
  6. Type: /publish 3 to publish
  1. Type: /search suricata
  2. See all projects/books mentioning "suricata"
  3. Click action buttons to manage

🐛 Troubleshooting

"Command not recognized"

  • Check workflow is Active (toggle in n8n)
  • Verify Telegram Trigger credential is set

"Error fetching data"

"No button appears" (Docker workflow)

  • Check Docker Event - Callback Handler.json is active
  • Inline keyboard markup must be set correctly

"AI generation fails"

  • Check OpenRouter credit balance
  • Model openrouter/free might be rate-limited, switch to google/gemini-2.5-flash

📊 Monitoring

Check n8n Executions:

  • n8n → Left menu → "Executions"
  • Filter by workflow name
  • Red = Failed (click to see error details)
  • Green = Success

🚀 Next Steps

  1. Test all commands - Go through each one in Telegram
  2. Customize messages - Edit text in Telegram nodes
  3. Add your own commands - Extend the Switch node
  4. Set up monitoring - Add error alerts to Slack/Discord

📞 Support

If something breaks:

  1. Check n8n Execution logs
  2. Verify API credentials
  3. Test Directus API manually: curl https://cms.dk0.dev/items/projects

Your system is now LIVE! 🎉