GitHub NPM CVE Alerts to Slack with Apify (n8n Workflow)

Get Emergency Slack Alerts for NPM Vulnerabilities—Automatically

This n8n workflow pulls your package.json from GitHub, scans dependencies with the Apify NPM CVE Monitor, and posts an emergency alert to Slack only when high/critical vulnerabilities (or suspicious dependency patterns) are detected.

What this workflow does

• Runs on a schedule: Executes every Monday at 9am via an n8n Schedule trigger.
• Fetches your latest package.json from GitHub: Uses the GitHub Contents API (via HTTP Request) to retrieve package.json from your repository.
• Scans with Apify NPM CVE Monitor: Sends the package.json content to the Apify actor to check for medium-and-above vulnerabilities and suspicious dependency patterns.
• Organizes scan results: Groups findings into critical, high, medium, and suspicious buckets.
• Alerts only when it matters: If no critical or high issues are found, the workflow stops and does not spam Slack.
• Sends a detailed Slack message: Formats per-package CVE details and includes suggested fixes in the emergency alert, then posts to your configured Slack channel.

Use cases

• SaaS security monitoring: Catch dependency vulnerabilities in your Node.js projects before they become incidents.
• Release hygiene: Ensure newly declared dependencies remain free of high-risk CVEs.
• Automation engineering: Centralize GitHub + Apify vulnerability scanning and deliver actionable alerts to Slack.

Technical details (nodes & integrations)

• Schedule Trigger (runs Mondays at 9am)
• HTTP Request to GitHub Contents API (requires GitHub token read access)
• HTTP Request to Apify (requires Apify API token)
• Code for grouping/results handling
• if node to stop when no critical/high findings exist
• Slack node to post the emergency alert (configured with Slack OAuth2)
• Sticky Note for workflow guidance

Best for: n8n users, automation engineers, and SaaS operators who want reliable GitHub-to-Apify-to-Slack security alerts for NPM dependencies.