Back to case studies
2025Live2 weeks · Nov 2025

Content Channel

Automated content pipeline — one Obsidian note goes live across Telegram, LinkedIn and Instagram on schedule. Zero copy-paste.

Role
Content ops automation · we eat our own dogfood
Open project ↗

By the numbers

3
Platforms auto-published
daily
Publishing cadence held
2 weeks
Idea → live pipeline
live
Running in production since Nov 2025

Stack

  • Node.js
  • Grammy (Telegram)
  • Claude
  • n8n
  • Cron
  • Express
  • Obsidian sync

Process receipts

The pipeline of agents that built it, the count of commits and deploys, and the wall-clock time from spec to production. No decks — just the audit trail.

2 weeks
Shipped in
80
Commits
4
Deploys
4
Agents in pipeline
Agent pipeline
  1. architect
  2. telegram-bot-expert
  3. prompt-engineer
  4. developer

Context

Cross-platform content duplication is the #1 reason content pipelines die. We needed one writing surface (Obsidian) and automated downstream publishing to Telegram, LinkedIn and Instagram. We built it for ourselves first — now we ship the same pipeline to studios, solo creators and small teams who want content ops without the copy-paste tax.

Approach

Obsidian stays the authoring layer — that is where work actually happens. A Node service watches the vault, extracts publish-ready markdown, uses Claude to adapt tone per platform (short Telegram post, structured LinkedIn with hook, Instagram caption with hashtags), and schedules delivery through Grammy + platform APIs. n8n orchestrates retries and batches.

Outcome

Our public channel @btw_aitech runs on this pipeline daily since November 2025. Two weeks from idea to live, held daily cadence since. The service offering: same setup adapted to your vault and your platforms in two weeks. You write once, we handle the rest.

Have a similar project?

We reply within 24 hours. Usually faster.

Start a project →Telegram → @btw_aitech