ReadGZH WeChat Article to Markdown n8n Workflow (Manual)
ReadGZH WeChat Article to Markdown n8n Workflow (Manual)
Regular price
£75.99
Regular price
£75.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
âš¡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
ReadGZH WeChat Article to Markdown n8n Workflow (Manual)
Regular price
£75.99
Regular price
£75.99
Sale price
Unit price
/
per
Turn any public WeChat article into a downloadable Markdown file—instantly in n8n
This `ReadGZH WeChat Article to Markdown (Manual)` workflow lets you paste a public WeChat Official Account URL, fetch the article via the ReadGZH API, validate it as Markdown, and output a UTF-8 .md file you can download directly from your n8n run.
What this workflow does
- Runs manually from n8n (Manual Trigger).
- Accepts an articleUrl input in workflow settings—either a public https://mp.weixin.qq.com/s/... link or a https://readgzh.site/s/... share URL.
- Validates the URL format to ensure it matches the expected pattern.
- Calls api.readgzh.site to retrieve the article content as Markdown text.
- Verifies the API response looks like valid Markdown, extracts the article title, and generates a safe file name.
- Converts the Markdown into a UTF-8 Markdown file and exposes it as binary output for download.
Use cases
- Convert WeChat Official Account posts into Markdown for documentation, archiving, or content review.
- SaaS operations teams: quickly store article snapshots in a format that’s easy to index or process downstream.
- Automation engineers: build a repeatable ingestion step in an n8n pipeline that stores outputs as .md files.
Technical details
- Nodes used: set, code, sticky note, http request, convert to file, manual trigger.
- API integration: HTTP Request to api.readgzh.site to fetch Markdown.
- Optional auth for higher quotas: use Generic Credential Type → Header Auth on the HTTP Request node with Header name Authorization and value Bearer {YourReadGZHApiKey}.
- Requirements/notes: your n8n instance must have outbound HTTPS access; anonymous requests share IP-based quota, and extraction may consume ReadGZH credits. Images remain remote links, and deleted/restricted articles may not extract.
