Send a daily GitHub Trending digest to Telegram using Google Gemini

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Daily GitHub Trending AI Digest to Telegram This workflow generates a daily AI powered GitHub Trending digest and sends it to Telegram using GitHub Trending, GitHub README data, and Google Gemini. ...

Best for

Market Research automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.splitout, @n8n/n8n-nodes-langchain.outputparserstructured, @n8n/n8n-nodes-langchain.lmchatgooglegemini, n8n-nodes-base.telegram, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.html

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Atha Ahsan Xavier Haris.

Original n8n.io source

1.1 Workflow description

Title: Send a daily GitHub Trending digest to Telegram using Google Gemini
Workflow name: Send a daily GitHub Trending digest to Telegram using Google Gemini

Daily GitHub Trending AI Digest to Telegram

This workflow generates a daily AI-powered GitHub Trending digest and sends it to Telegram using GitHub Trending, GitHub README data, and Google Gemini.

It fetches trending repositories from GitHub, extracts the top repository links, retrieves each repository README through the GitHub API, builds a structured AI payload, asks Gemini to summarize the repositories, and delivers the result as a clean Telegram digest.

It is useful for developers, builders, researchers, and tech enthusiasts who want to discover interesting open-source projects without manually browsing GitHub Trending every day.

Common use cases:

Send a daily GitHub Trending digest to your Telegram
Discover useful open-source repositories automatically
Monitor new developer tools, AI projects, frameworks, and libraries
Build a personal open-source discovery assistant
Learn how to combine web extraction, GitHub API data, LLM summarization, and Telegram in n8n

How it works

Starts from a Schedule Trigger, which you can customize
Sets the number of repositories to include in the digest
Fetches the GitHub Trending page
Extracts trending repository links from the page
Splits the repository links into individual items
Builds GitHub repository URLs and GitHub README API URLs
Limits the workflow to the configured number of repositories
Fetches each repository README using the GitHub API
Decodes README content from base64
Builds one structured AI payload containing all selected repositories
Sends the payload to Google Gemini
Parses Gemini’s response into structured JSON
Formats the result into a Telegram message
Sends the AI-generated digest to Telegram

Setup steps

Set the number of repositories in the Set Digest Config node
Connect your Google Gemini credentials
Connect your Telegram credentials
Set your Telegram chat ID in the Telegram node
Adjust the Schedule Trigger if you want a different run time
Test the workflow manually
Activate the workflow

Notes

This workflow uses GitHub Trending page data and GitHub public README API data. GitHub does not provide an official Trending API endpoint, so the workflow extracts repository links from the GitHub Trending page.

The AI summaries are generated only from the provided repository URLs and README excerpts. If a README is missing or unclear, the summary quality may be limited.

Need Help?

Have questions or want to connect? Reach me on LinkedIn.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Schedule Trigger

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.3

Block 2 - Split Repository Links

Type / Role: n8n-nodes-base.splitOut - splitOut
Config choices: Version 1

Block 3 - Structured Output Parser

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.3

Block 4 - Google Gemini Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatGoogleGemini - lmChatGoogleGemini
Config choices: Version 1

Block 5 - Send a text message

Type / Role: n8n-nodes-base.telegram - telegram
Config choices: Version 1.2

Block 6 - Set Digest Config

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 7 - Fetch GitHub Trending Page

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 8 - Extract Trending Repository Links

Type / Role: n8n-nodes-base.html - html
Config choices: Version 1.2

Block 9 - Build Repository URLs

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 10 - Limit Repositories

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 11 - Fetch Repository README

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 12 - Build AI Digest Payload

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 13 - Generate AI Repository Digest

Type / Role: @n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices: Version 1.9

Block 14 - Format Telegram Message

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 15 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 16 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 17 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 18 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 19 - Sticky Note4

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 20 - Sticky Note5

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Send a daily GitHub Trending digest to Telegram using Google Gemini
Complexity	advanced
Nodes	20
Categories	Market Research, AI Summarization
Author	Atha Ahsan Xavier Haris
Published	08 May 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/15555/15555.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Market Research workflows AI Summarization workflows

Frequently asked questions

What does Send a daily GitHub Trending digest to Telegram using Google Gemini do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Market Research, AI Summarization use case.

Atha Ahsan Xavier Haris

3 workflows

Nodes

n8n-nodes-base.scheduletrigger n8n-nodes-base.splitout @n8n/n8n-nodes-langchain.outputparserstructured @n8n/n8n-nodes-langchain.lmchatgooglegemini n8n-nodes-base.telegram n8n-nodes-base.set n8n-nodes-base.httprequest n8n-nodes-base.html

Complexity

advanced

Published 08 May 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/15555/15555.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Answer BigQuery questions in Microsoft Teams with Claude 3.5 dual agents

## Quick overview Turn Microsoft Teams into a natural language BI tool. This dual-agent Claude workflow intelligently classifies user questions, generates safe BigQuery SQL, executes the query, and returns a plain-English summary alongside a data preview directly to your Teams channel. ## How it works 1. The workflow listens for new messages in a designated Microsoft Teams channel or chat. 2. It checks a 24-hour static data cache for your BigQuery schema. If the cache is missing or expired, it automatically fetches the latest INFORMATION_SCHEMA metadata. 3. A main Claude 3.5 Sonnet agent classifies the user's intent (analytical, conversational, or unsafe) and identifies the relevant database tables. 4. If the intent is analytical, a specialized Claude SQL sub-agent generates a read-only SELECT query tailored exactly to your schema. 5. The workflow executes the query against BigQuery (safely constrained to a maximum of 100 rows). 6. A final Claude agent translates the raw query results into a concise, plain-English summary. 7. The answer is posted back to Teams as an Adaptive Card, complete with a formatted data preview and the generated SQL code. 8. Non-analytical questions or pipeline errors are intelligently routed to receive standard conversational replies in Teams. ## Setup 1. CRITICAL SECURITY: Restrict your Google Cloud Service Account IAM roles to BigQuery Data Viewer and BigQuery Job User ONLY. Do not use a highly privileged account. 2. Configure your Microsoft Teams trigger and posting credentials, specifying the target team and channel for the bot to operate in. 3. Configure your Google BigQuery credentials to allow reading metadata and executing queries. 4. Configure your Anthropic credentials for the three Claude LangChain nodes. 5. Update the "Configure Variables" node with your specific GCP Project ID and BigQuery Dataset ID. ## Requirements - A Google Cloud project with BigQuery enabled and existing structured datasets. - An Anthropic API key with access to the Claude 3.5 Sonnet model. - Microsoft Teams administrator access to authorize the n8n integration. ## Customization - Distributed Environments: If you are running n8n with multiple worker nodes (Queue Mode), you must swap the $getWorkflowStaticData() schema cache logic to read/write from a dedicated Key-Value store (like Redis or Supabase) to ensure state synchronization. - UI Layout: Modify the Create Teams Adaptive Card node to add corporate branding, custom colors, or alter the FactSet data preview structure. ## Additional info This architecture features built-in pipeline protections, including strict 40,000-character payload limits to prevent LLM context window blowouts, and fallback handling for "zero-row" query results to ensure users are never left without a response.

View

Evaluate LinkedIn profiles with Apify and Groq Llama chat model

## Quick overview This workflow collects a LinkedIn profile URL via an n8n form, scrapes the public profile data using the Apify LinkedIn Profile Scraper actor, analyzes the results with a Groq-hosted Llama model, and displays an HTML-formatted evaluation back to the user. ## How it works 1. Receives a LinkedIn Profile URL when a user submits the n8n form. 2. Prepares the LinkedIn URL along with the Apify API token and Groq API key used for downstream requests. 3. Sends the profile URL to the Apify `harvestapi/linkedin-profile-scraper` actor and retrieves the scraped dataset items. 4. Passes the scraped profile JSON to a Groq chat model via an LLM chain to generate an HTML evaluation with a score and recommendations. 5. Displays the generated HTML evaluation to the user as the form completion message. ## Setup 1. Add a valid Apify API token and ensure the Apify actor endpoint (`harvestapi/linkedin-profile-scraper`) is accessible for your account. 2. Add Groq API credentials in n8n and confirm the selected model (meta-llama/llama-4-scout-17b-16e-instruct) is available to your Groq account. 3. Replace the placeholder API key values in the workflow (or move them to n8n credentials/environment variables) and verify the form field label matches `LinkedIn Profile URL`.

View

Validate startup ideas with Google Gemini, Groq, and Gmail

## Quick overview This workflow collects a startup idea via an n8n form, uses Google Gemini to generate a SWOT-style analysis, assigns a viability score, uses Groq to turn the results into a structured validation report, and emails the final report through Gmail. ## How it works 1. Receives a startup idea, industry, and target audience from an n8n Form trigger. 2. Sends the submission to Google Gemini to generate a professional analysis covering the problem, business model, and SWOT factors. 3. Generates a startup viability score (currently a random value from 80–100) and packages it with the Gemini analysis. 4. Sends the score and analysis to Groq (Llama 3.3 70B) to compile a full validation report with an executive summary, market potential, recommendations, and final verdict. 5. Emails the generated validation report to the configured recipient using Gmail. ## Setup 1. Add credentials for Google Gemini (PaLM) API, Groq API, and a Gmail OAuth2 connection. 2. Replace the placeholder recipient address in the Gmail step ("[email protected]") with your target email address before activating the workflow. 3. Publish the n8n form, then share the form URL with the users who should submit their startup ideas for validation.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Send a daily GitHub Trending digest to Telegram using Google Gemini

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Daily GitHub Trending AI Digest to Telegram

Common use cases:

How it works

Setup steps

Notes

Need Help?

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Schedule Trigger

Block 2 - Split Repository Links

Block 3 - Structured Output Parser

Block 4 - Google Gemini Chat Model

Block 5 - Send a text message

Block 6 - Set Digest Config

Block 7 - Fetch GitHub Trending Page

Block 8 - Extract Trending Repository Links

Block 9 - Build Repository URLs

Block 10 - Limit Repositories

Block 11 - Fetch Repository README

Block 12 - Build AI Digest Payload

Block 13 - Generate AI Repository Digest

Block 14 - Format Telegram Message

Block 15 - Sticky Note

Block 16 - Sticky Note1

Block 17 - Sticky Note2

Block 18 - Sticky Note3

Block 19 - Sticky Note4

Block 20 - Sticky Note5

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions