Automation library · Data collection

Track GitHub node definitions and export to Google Sheets

Started by an event in a connected app, and works across Google Sheets. 11 steps, 2 loops or waits: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 5Service 5

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

  1. 1Manual TriggerManual triggerStarts it
  2. 2Clear Google SheetsGoogle SheetsService
  3. 3Get Repository ContentsHttp RequestService
  4. 4Process in BatchesSplit In BatchesLogic
  5. 5Get Directory ContentsHttp RequestService
  6. 6Filter Node FilesCodeLogic
  7. 7Download Node FileHttp RequestService
  8. 8Parse JSON DataCodeLogic
  9. 9Format DataSetLogic
  10. 10Append to Google SheetsGoogle SheetsService
  11. 11WaitWaitLogic

How it's built

Starts on
An event in a connected app
Steps
11, 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 an event in a connected app.

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. 11 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 11 steps before you point it at anything that matters.