Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs on Github events (repository). Along the way it connects GitHub, Google Sheets, Notion and Slack.
How it runs
Trigger: On Github events (repository).
- GitHub: get many (release)
- Edit Fields (Edit Fields (Set)): sets 9 fields: SDK Name, Release Tag, Release Title…
- Google Sheets: append
- Notion: get many (database page)
- Merge: merges the data from its input branches
- Function Compute Drift (Code): runs custom JavaScript code
- Google Sheets: append
- Filter Overdue SDKs (If): checks a condition and branches into true / false
- Slack: uses Slack
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Github Trigger
n8n-nodes-base.githubTrigger - GitHub
n8n-nodes-base.github - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets - Notion
n8n-nodes-base.notion - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack
From the author
📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift…