Automating WeChat Articles: How WorkBuddy Pushes Posts to Drafts

If you run a WeChat official account, you know the grind: write 3,000 words, spend an hour wrestling the editor's formatting, then another hour fixing broken styles after pasting. A few weeks ago, I decided to see if AI could take over that whole pipeline—write, format, and push the final HTML straight into the draft box. After a few days of tinkering, I got it working with WorkBuddy. This article was written and formatted by it, and then pushed to my drafts automatically. I only reviewed. Here's how it works, from the API keys to the style training.

The Two Real Problems

AI writes fast—give it a pile of your old articles, and it'll mimic your tone and structure in minutes. But the output often smells like AI: no opinions, no judgment, no personality. Readers scroll past. And even if the content is decent, the formatting fight is real. WeChat's editor mangles most HTML, so you lose an hour just making it look right.

So I focused on two fixes: kill the AI smell, and make formatting a non-issue by pushing finished HTML to drafts.

Getting the Keys and Whitelisting the IP

WeChat provides two official APIs: media/upload for image assets and draft/add for creating drafts. To call them, you need an AppID and an AppSecret. As of December 1, 2025, WeChat moved these settings from the old backend to the WeChat Developer Platform. You'll find them under My Business → Development Keys.

Here's the six-step setup:

1. Log in at developers.weixin.qq.com/platform/ with your admin WeChat.
2. Scroll to My Business and select your Official Account.
3. Click the Development Keys area to see AppID, AppSecret, and API IP whitelist.
4. Copy the AppID. For AppSecret, click Enable or Reset, confirm with your admin WeChat, and copy the newly generated secret (it shows only once).
5. In WorkBuddy, tell it: "I want you to push my finished articles to the WeChat draft box. Here are my AppID and AppSecret."
6. WorkBuddy will give you an IP address. Add that to the API IP whitelist in the same Development Keys area.

That's it. Once the keys are in and the IP is whitelisted, the plumbing is done. WorkBuddy can now call the APIs on your behalf.

Training the Style: From 3–5 Articles to a Skill

The formatting problem is solved, but content still needs to sound like you. The fix is to feed your writing style to WorkBuddy. Here's a four-step path that goes from quick-and-dirty to fully automatic.

Step 1: Feed 3–5 of Your Best Articles

Pick a few posts you're proud of, paste them in, and say: "Learn my tone, sentence rhythm, heading style, and opening hooks." You'll get an 80% match right away—your colloquialisms, your number-heavy titles, your paragraph pacing. This is the lowest-effort start.

Step 2: Let It Learn Everything (Tencent Perk)

WorkBuddy is a Tencent product, so it can access your entire Official Account history if you give it the account name. I had it read all my past articles, and it picked up my favorite phrases, my hook patterns, even how I structure sections. The difference is noticeable.

Step 3: Build a Style Library Document

Don't keep that knowledge in a chat session. Ask WorkBuddy to turn its findings into a Writing Style Guide document. Include your preferred transition words, banned words (like "firstly, secondly, finally"), paragraph length (max 4 lines), title format (numbers + pain point), image rules, and punchy quote guidelines. Before each writing session, have WorkBuddy read that doc.

Step 4: Turn It Into a Skill

A style library is just a reference—you have to remember to feed it. A Skill is an automated workflow. WorkBuddy lets you package the style guide, formatting templates, and even the push script into a single Skill file (SKILL.md). Then you just say "write an article," and it loads everything automatically. The difference: style library = a manual you have to remember; Skill = a self-loading system.

I now use both. The style library holds the content guidelines; the Skill bundles them with the formatting rules and the push logic.

WeChat Formatting: The Table Hack

WeChat's editor is picky. Standard HTML like <section> and <p> with inline styles often breaks. The only reliable approach is to use <table> as the structural skeleton, put styles directly on <td> elements, and place your content inside <p>. This is the same trick email developers use—it maximizes compatibility.

Stick to basic CSS: color, background-color, font-size, font-weight, padding, margin, border, text-align, line-height. Avoid border-radius, position, linear-gradient, and pseudo-elements—they'll break when pushed. Once I encoded these rules into the Skill, drafts came out pixel-perfect, no manual cleanup needed.

The Human Review: 5 Checks Before You Hit Publish

Even with all this automation, you still need human judgment. Here's my checklist, refined over dozens of articles:

• Content direction: Is the topic what you actually wanted? Does the structure make sense? AI has a talent for writing confidently off-topic. If something feels off, don't rewrite it yourself—tell WorkBuddy what to fix.
• AI smell: Read for telltale signs: "firstly," "moreover," "empower," "one-click," overused parallel structures. The opening is the worst offender. When you spot a line that doesn't sound like you, rewrite it manually and add that as feedback.
• Title: Numbers and a promise. My first draft title was flat: "This article was written by WorkBuddy: full record of WeChat integration, one-click push to drafts + style solidification." I changed it to "Tested WorkBuddy WeChat Integration: Articles Auto-Push to Drafts, 10x Efficiency!" Note WeChat's limits: titles over 64 bytes and summaries over 120 bytes get rejected (error codes 45003/45004). Chinese characters count as 3 bytes each.
• Formatting: AI loves adding boxes and colored blocks everywhere. My first attempt came out looking like a ransom note. Instead, pick one of your best previous articles and tell WorkBuddy to mimic its exact source code—gold numbering, beige intro card, restrained callouts.
• Screenshots: For tutorial-style posts, real screenshots are non-negotiable. AI-generated illustrations are useless. Replace any concept art with actual screen captures of each step.

Feedback Loop: Make It Better Every Time

After the review, the most important step: feed your changes back into the system. For each article, I do 4–5 rounds of refinement: first draft free, second tighten language, third restructure sections, fourth polish details. Each round focuses on one dimension. Then I summarize the feedback and update the style library or Skill.

For example, WorkBuddy used to generate flashy AI images that had nothing to do with the content. I told it once: "Only use real screenshots; if you can't find one, leave a placeholder." It added that as an "image red line" in the style guide. Now every post either uses a real screenshot or leaves a spot for me to fill.

This article reads like me because I've trained it over a dozen posts. Each feedback loop makes it a bit more human.

What I Learned

The biggest win isn't just time savings—though that's huge. A 3,000-word tutorial used to take 5 hours: writing, formatting, checking. Now it's 30 minutes, and I only review. The pipeline is repeatable: I pick a topic, feed in materials, and let WorkBuddy handle the rest.

But here's the thing: AI does 95% of the work, but that last 5%—the judgment, the taste, the personal experience—is what makes it yours. Tools will keep getting better, but your judgment is the moat. Build the pipeline now, and tomorrow you'll have a zero-cost content team.