Track GitHub trending repos automatically into a Supabase database

Scrapes GitHub's trending page daily, weekly, and monthly, and stores clean results in a database.

How the work actually flows

A straight line. Runs once per one per timeframe view daily weekly monthly.

Pattern: Sequence (1) ยท Multiple Instances without Synchronization (12)

flowchart TD trig(["runs on a daily schedule"]):::trigtime s0[["open trending page per timeframe"]]:::mi s1["extract project details with AI"]:::svc s2["tag results by timeframe"]:::task s3[("save records to database")]:::store trig --> s0 s0 --> s1 s1 --> s2 s2 --> s3 out[/"growing history of trending projects"/]:::out pay{{"track project popularity over time"}}:::pay s3 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepAn outside serviceRuns once per itemA record or sheetResultPayoff
Build size
Standard

A mid-size build with several tools working together.

Business functions
AI Agents & Autonomous SystemsEmail AutomationSpreadsheet & Database OpsReporting & AnalyticsWeb Scraping & Data CollectionResearch & Market Intelligence
Connects
FireCrawlOpenAISupabase

The problem it solves

You want to track which projects are gaining traction, but checking a trending page by hand every day is tedious and easy to forget. Without a saved history, you can't tell how a project's popularity changed over time or spot trends early.

Who it fits

A developer, founder, or analyst who tracks software trends and wants historical data instead of a one-time snapshot.

How it works

  1. On a schedule, the automation opens the trending page for daily, weekly, and monthly views
  2. It scrapes the page and an AI model extracts each project's name, link, description, language, and stars
  3. Each result is tagged by timeframe
  4. The structured records are saved to a Supabase database
  5. You get a growing history of trending projects ready to query
What you get

Trend history you can query anytime

You get a growing, searchable history of GitHub's trending repositories, tracked daily, weekly, and monthly.

What you get

A continuously growing Supabase table of trending projects you can query or build dashboards from.

What you need

A web scraping account, an OpenAI API key, and a Supabase account.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook