Automation library · Data collection

Track GitHub trending repositories with ScrapeOps

Started by a clock, and works across Google Sheets. 12 steps, 2 loops or waits: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
0Branches: places the flow splits
2Loops or waits
1Service it connects to

The flow

Starts it 1Logic 7Service 4

The steps in the order they run, from what starts it.

  1. 1Cron (daily/weekly)Schedule triggerStarts it
  2. 2Set InputsSetLogic
  3. 3Build URLsCodeLogic
  4. 4Read raw (for weekly)Google SheetsService
  5. 5Split URLs (loop)Split In BatchesLogic
  6. 6Generate WeeklyCodeLogic
  7. 7ScrapeOps: Fetch HTMLScrape OpsService
  8. 8Write to Google Sheets (weekly tab)Google SheetsService
  9. 9Polite DelayWaitLogic
  10. 10Extract Trending ReposCodeLogic
  11. 11Normalize + Enrich-from-pageCodeLogic
  12. 12Write to Google Sheets (raw tab)Google SheetsService

How it's built

Starts on
A clock
Steps
12, 2 loops or waits
Size
Medium: a working afternoon
Connects to
Google Sheets
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Sheets account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 12 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 12 steps before you point it at anything that matters.