Automatically document and backup N8N workflows
Ready for 3.0What this workflow does
This AI workflow has 17 nodes and runs on a schedule (every week at 01:00). Along the way it connects Notion, Slack, OpenAI and GitHub. It also calls api.notion.com over HTTP.
How it runs
Trigger: On a schedule (every week at 01:00).
- Get active workflows with internal-infra tag (n8n): uses n8n
- Check if updated in last 7 days (If): checks a condition and branches into true / false
- Set fields (Edit Fields (Set)): sets 9 fields: active, url, errorWorkflow…
- Get notion page with workflow id (HTTP Request): calls api.notion.com (POST)
- Map fields (Edit Fields (Set)): sets 1 field: input
- Check that error workflow has been configured (If): checks a condition and branches into true / false
- Summarize what the Workflow does (OpenAI): uses OpenAI
- Upload changes to repo (GitHub): edit (file)
- Notify on workflow setup error (Slack): uses Slack
- Is this a new workflow (to Notion) ? (If): checks a condition and branches into true / false
…plus 6 more steps. See the full node list below.
Services it uses
HTTP calls to: api.notion.com
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)
- Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Notion
n8n-nodes-base.notion - Slack
n8n-nodes-base.slack - OpenAI
@n8n/n8n-nodes-langchain.openAi - GitHub
n8n-nodes-base.github - If
n8n-nodes-base.if - Schedule Trigger
n8n-nodes-base.scheduleTrigger - n8n
n8n-nodes-base.n8n
From the author
Automatically backs up your workflows to Github and generates documentation in a Notion database. - Weekly run, uses the "internal-infra" tag to look for new or recently modified workflows - Uses a Notion database page to hold the workflow summary, last…