Send Slack alerts for new npm or PyPI package releases with Apify
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
Community nodes
These come from third-party npm packages. In n8n 3.0 unverified community packages are off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
@apify/n8n-nodes-apify(Check the registry)
Nodes used (11)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Apify
@apify/n8n-nodes-apify.apify - Filter
n8n-nodes-base.filter - Remove Duplicates
n8n-nodes-base.removeDuplicates - Code
n8n-nodes-base.code - Slack
n8n-nodes-base.slack - Discord
n8n-nodes-base.discord - Gmail
n8n-nodes-base.gmail - Notion
n8n-nodes-base.notion - HTTP Request
n8n-nodes-base.httpRequest
What it does
Quick overview This workflow checks a list of npm packages every 12 hours using Apify’s Package Registry Scraper and posts a Slack message only when it detects a new package version. How it works 1. Runs every 12 hours on a schedule. 2. Defines the package registry (npm) and the list of package names to monitor. 3. Uses Apify (damistudio~package-registry-scraper actor) to fetch each package’s current version and metadata such as description, license, repository, URL, and downloads. 4. Filters out invalid lookups by keeping only results marked as successful. 5. Suppresses repeat alerts by deduplicating on package name plus version across workflow executions. 6. Posts a formatted release alert to a selected Slack channel for each newly detected version. Setup 1. Add an Apify API token credential to the Apify node and confirm the actor run settings (including the $1 max charge cap) fit your needs. 2. Add a Slack OAuth2 credential, select the target channel in the Slack node, and ensure the workflow has permission to post messages. 3. Update the package list (and optionally the registry and includeDownloads flag) in the “Packages to watch” step to match the dependencies you want to track.