Automate GitHub trending data collection with FireCrawl, GPT and Supabase
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 11 nodes and runs on a schedule (every day) (plus 2 other triggers). Along the way it connects Supabase, OpenAI Chat Model and Firecrawl (community).
How it runs
Trigger: On a schedule (every day) (plus 2 other triggers).
- B (Edit Fields (Set)): sets 1 field: type
- B (Edit Fields (Set)): sets 1 field: type
- B (Edit Fields (Set)): sets 1 field: type
- B_ALL (Edit Fields (Set)): sets 1 field: type
- Firecrawl: scrape
- AI Agent: runs an AI agent, with model: OpenAI Chat Model; 1 tool (Create a row in Supabase)
Services it uses
Uses Firecrawl. New users get 10% off with our link.
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @mendable/n8n-nodes-firecrawl is verified or supports 3.0 (used in firecrawl).
Nodes used (6)
- AI Agent
@n8n/n8n-nodes-langchain.agent - Supabase Tool
n8n-nodes-base.supabaseTool - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Firecrawl
@mendable/n8n-nodes-firecrawl.firecrawl - Edit Fields (Set)
n8n-nodes-base.set
From the author
GitHub Trending to Supabase (Daily, Weekly, Monthly) Who is this for? This workflow is for developers, researchers, founders, and data analysts who want a historical dataset of GitHub Trending repositories without manual scraping. It’s ideal for building…