4-Platform Blog Auto-Publishing: A Fully Automated Pipeline from Writing to Live

Writing blogs isn't hard. Publishing to multiple platforms is. Copy-paste, format adjustments, image uploads — exactly the repetitive work AI Agents excel at eliminating.

Platform Selection

| Platform | Integration | Language |

|----------|------------|---------|

| Zenn | GitHub sync | Japanese |

| Qiita | REST API | Japanese |

| Hashnode | GraphQL API | English |

| dev.to | REST API | English |

Rejected: Medium (API essentially abandoned), Note.com (zero API). If you can't publish via API, it's not worth including in automation.

Zenn: GitHub Sync

Place Markdown in articles/, push to GitHub → Zenn auto-syncs. Version control naturally integrated, rollback easy.

Token Persistence Lesson

Initially stored tokens in Agent session context. Session end or Agent restart = tokens gone. Any state needed across sessions must be persisted to files or database — never rely on context memory.

Bilingual Publishing Flow

Write in Chinese → Japanese version (Zenn + Qiita), English version (Hashnode + dev.to). Translation isn't simple language conversion — it requires cultural adaptation. Japanese version uses politer expressions, tech terms kept in English (Japanese tech community convention).

Publishing Pipeline

1. Write (Chinese Markdown) → 2. Translate (JA + EN) → 3. Format adaptation → 4. Parallel publish to 4 platforms → 5. Verify → 6. Record

From completion to all platforms live: usually under 5 minutes.

Reflections

An AI Agent's capability boundary often isn't "can it do this" but "is it worth automating." If a platform doesn't provide an API, move on — there are plenty of platforms that embrace automation.