Send end-of-life software alerts using NocoDB, endoflife.date, and Slack
Ready for 3.0What this workflow does
This workflow has 29 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects NocoDB and Slack.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- NocoDB Config (Edit Fields (Set)): sets 2 fields: Base ID, NocoDB Url
- Config (Edit Fields (Set)): sets 1 field: Days before EOL
- Create NocoDB EOL Software Table (HTTP Request): calls an HTTP API (POST)
- Get software to check (NocoDB): get many
- Create NocoDB EOL Dates Table (HTTP Request): calls an HTTP API (POST)
- Each Software Once (Loop Over Items (Split in Batches)): loops over the items in batches
- Create NocoDB EOL Projects Table (HTTP Request): calls an HTTP API (POST)
- Get EOLProjects (NocoDB): get many
- Get Current Rows (NocoDB): get many
- Get EOL data from endoflife.date (HTTP Request): calls an HTTP API
…plus 17 more steps. See the full node list below.
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 (13)
- Wait
n8n-nodes-base.wait - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Rename Keys
n8n-nodes-base.renameKeys - NocoDB
n8n-nodes-base.nocoDb - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Code
n8n-nodes-base.code - Filter
n8n-nodes-base.filter - Slack
n8n-nodes-base.slack - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Manual Trigger
n8n-nodes-base.manualTrigger
From the author
What Is This? This workflow is an automated system that tracks End-of-Life (EOL) dates for software and technologies used across your projects. It eliminates the need to manually monitor EOL dates in spreadsheets or calendars by automatically fetching the…