Automation library · Documents and files

Track SDK documentation drift with GitHub and Notion

Started by an event in a connected app, and works across GitHub, Google Sheets, Notion and Slack. 10 steps, 1 branch: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
4Services it connects to

The flow

Starts it 1Logic 4Service 5

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

  1. 1Github TriggerGithub triggerStarts it
  2. 2GitHub Fetch ReleasesGithubService
  3. 3Edit FieldsSetLogic
  4. 4Google Sheets Log Release DataGoogle SheetsService
  5. 5Notion Fetch FAQ DataNotionService
  6. 6MergeMergeLogic
  7. 7Function Compute DriftCodeLogic
  8. 8Google Sheets Update Drift StatusGoogle SheetsService
  9. 9Filter Overdue SDKsIfLogic
  10. 10Slack Post AlertsSlackService

How it's built

Starts on
An event in a connected app
Steps
10, with 1 branch
Size
Medium: a working afternoon
Connects to
GitHub, Google Sheets, Notion, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own GitHub, Google Sheets, Notion and Slack accounts. 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. 10 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 10 steps before you point it at anything that matters.