Daily GitHub Trending AI Briefing to DingTalk via n8n HTML Hosting

Get a daily “AI-enhanced GitHub Trending” report and publish it to DingTalk—automatically

This n8n workflow runs every day to scrape GitHub Trending, optionally enrich each repo with cleaned README excerpts, generates a Simplified Chinese AI briefing via an OpenAI-compatible Chat Completions API, and publishes a single-file HTML report hosted on HTML Hoster—then posts the link to DingTalk and/or Feishu.

What this workflow does

• Runs on a daily cron schedule to keep your team up to date with the latest GitHub Trending (daily) repositories.
• Scrapes the GitHub Trending HTML page and extracts the top N repositories, including stars, forks, language, and “stars today”.
• Fetches and cleans README content from raw.githubusercontent.com, using fallback branches when needed, then merges excerpts into the dataset.
• Calls an OpenAI-compatible Chat Completions endpoint to produce a structured JSON briefing in Simplified Chinese.
• Renders a styled single-file HTML report (index.html) that combines GitHub facts with the AI briefing, and gracefully falls back to a “no AI analysis” report if the AI response is invalid.
• Uploads the report to HTML Hoster using the HTML Hoster Agent API and retrieves a public entryUrl.
• Posts a signed DingTalk/Feishu message containing the summary and hosted report link via configured group webhooks (if enabled).

Use cases

• Daily product/engineering briefs: track new open-source momentum from GitHub Trending and share it with your team.
• SaaS operator monitoring: quickly spot high-signal repos and summarize them in Chinese for stakeholders.
• Automation engineers: a practical n8n template combining scraping, LLM summarization, HTML publishing, and chat distribution.

Technical details

• n8n nodes mentioned in this workflow: schedule trigger, http request, set, code, and sticky note.
• Integrations: GitHub Trending scraping, raw.githubusercontent.com README fetching, OpenAI-compatible Chat Completions API (with Authorization: Bearer <API_KEY>), and HTML Hoster (Agent API upload + public entryUrl).
• Distribution: DingTalk and/or Feishu group webhooks with signed bot messages.

Setup highlights

• Add a Header Auth (Generic Credential) for your OpenAI-compatible provider: Authorization: Bearer <API_KEY>.
• Configure the AI API base URL and model in the workflow.