Project Details
Automated Content & Deployment Pipeline
Architecture, Automation & CI/CD
The content pipeline automates repetitive publishing work without giving up editorial or technical approval. n8n orchestrates the process while GitHub Actions enforces a controlled deployment contract.
Tech Stack
- n8n
- GitHub Actions
- Astro
- Telegram Bot
- AI APIs
- Docker
- Caddy
- Git
Project Links
From content automation to a real release pipeline
n8n coordinates topic and content steps, review loops, and Telegram communication. No article is published solely because an AI produced it; approvals remain explicit state transitions in the workflow.
Publishable changes land on a separate blog-publish branch. The deployment workflow accepts only the exact approved commit SHA and verifies that the delta contains allowed blog files only.
Staging, production, and rollback are part of the same process
Staging builds and deploys the exact approved blog commit. Only after final approval can that same commit be promoted to main and deployed live. The workflow fails if branches diverge or the approved SHA has moved.
A dedicated rollback workflow can reactivate the previous staging container slot, switch traffic back through Caddy, and safely reset the blog branch to main. The result is then reported back to n8n.