Real-time Data Breach Monitor with Have I Been Pwned

Monitors Have I Been Pwned API every 15 minutes for new breaches, uses simple cache to detect changes, and triggers customizable alerts for proactive security.

n8n
Real-time Data Breach Monitor with Have I Been Pwned

This workflow automates real-time monitoring of data breaches using the Have I Been Pwned (HIBP) API, polling every 15 minutes without needing an API key. It fetches the latest breach data, compares it against a cached version stored in a simple JSON file to identify new entries, and only proceeds with notifications for genuinely new breaches, preventing alert fatigue.

Key benefits include proactive identity protection for individuals and teams, automated awareness for security professionals and developers, and a demonstration of lightweight caching for stateful workflows. It's efficient, requiring minimal setup, and serves as a template for similar monitoring tasks.

Use cases span personal cybersecurity vigilance, enterprise security dashboards, DevOps breach tracking, and educational demos of n8n's caching patterns. Customize by adding nodes like Email, Slack, or Discord after the 'New breach' trigger for tailored notifications—all breach details are readily available.

Setup is straightforward: import the workflow, ensure file access for cache.json, and attach your preferred alert mechanism. The cache logic reads prior data, compares breach names or IDs, updates on changes, ensuring reliable, spam-free operation.

$12.99
Last updated October 3, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Data & Analytics workflows

More from Ravi Bakker

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.