GitHub Commit Velocity Tracker
Configured with HTTP Request, Respond To Webhook, Schedule Trigger, Supabase, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Code
- Web / API
- Transform
- Data store
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Cron Trigger | Trigger | Schedule Trigger | See node parameters |
| Manual Pipeline Webhook | Trigger | Webhook | See node parameters |
| Fetch Watchlist | Code | Code | See node parameters |
| Fetch NVIDIA GitHub | Web / API | HTTP Request | See node parameters |
| Fetch AMD GitHub | Web / API | HTTP Request | See node parameters |
| Fetch Intel GitHub | Web / API | HTTP Request | See node parameters |
| Fetch Google GitHub | Web / API | HTTP Request | See node parameters |
| Fetch Apple GitHub | Web / API | HTTP Request | See node parameters |
| Fetch Microsoft GitHub | Web / API | HTTP Request | See node parameters |
| Fetch Meta GitHub | Web / API | HTTP Request | See node parameters |
| Merge GitHub Results | Transform | Merge | See node parameters |
| Parse & Calculate Velocity | Code | Code | See node parameters |
| Load Previous Run from Supabase | Code | Code | See node parameters |
| Calculate Week-over-Week Delta | Code | Code | See node parameters |
| Aggregate for Groq | Code | Code | See node parameters |
| Groq: Activity Classifier | Web / API | HTTP Request | POST |
| Parse Groq Response | Code | Code | See node parameters |
| Signal Assembler | Code | Code | See node parameters |
| Upsert to Supabase | Data store | Supabase | upsert |
| Generate Report | Code | Code | See node parameters |
| Store Report in Supabase | Data store | Supabase | insert |
| Pipeline Response | Web / API | Respond To Webhook | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
GitHub Commit Velocity Tracker
GitHub Commit Velocity Tracker
Purpose and structure
This folder contains the GitHub Commit Velocity Tracker workflow. Its executable nodes use code, httpRequest, merge, respondToWebhook, scheduleTrigger, supabase, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Cron Trigger, Manual Pipeline Webhook
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
Nik Bear Brown; rights confirmed 2026-10-19 MIT; preserve source notices.