Lazy Editor: One-Click WeChat Publishing

Problem

WeChat content production is often split across multiple tools: write Markdown, paste it into the WeChat editor, fix style compatibility, create cover images, and then rewrite posts for Xiaohongshu, Jike, Moments, or podcasts. This skill turns that workflow into an API-driven pipeline, focusing on the engineering problem of taking content from raw material to a publishable WeChat draft.

How It Works

• Two pipeline paths: Path A moves from material collection, AI drafting, and rendering to cover generation and multi-platform copy; Path B fetches a WeChat article, analyzes its structure, and converts it for other platforms.
• WeChat-compatible rendering: the render endpoint returns inline-CSS HTML, addressing the constraint that WeChat does not support <style> tags; the materials emphasize preferring custom templates with isUserTemplate: true.
• Content production: supports tutorial, deep, and auto frameworks; it can also generate covers, Xiaohongshu carousel cards, and copy for xiaohongshu,jike,moments,podcast.
• Publishing and distribution: the publish endpoint accepts fields such as content, templateId, and coverImage, then pushes the article to a WeChat draft; multi-platform distribution supports WeChat L0 API direct push, while other platforms require CDP integration.

Boundaries

• Requires apiBaseUrl and apiKey, plus WeChat account authorization; custom templates must be created before relying on them.
• Publishing, covers, AI drafting, Xiaohongshu carousel cards, and multi-platform distribution consume quota; rendering and multi-platform copy are marked as free in the materials.
• Pipeline jobs return a jobId and require status polling; on failure, inspect required fields and errors such as 401, 403, and 429.