ManualTrigger Automate

For n8n, automate alerts for new data breaches from haveibeenpwned.com every 15 minutes. This workflow checks for the latest breaches, compares them with previous alerts, and sends notifications for new breaches while caching data for efficient tracking.

7/8/2025
24 nodes
Complex
schedulecomplexconverttofilesplitoutschedule triggersticky notereadwritefileextractfromfilenoopautomationadvancedfilesstoragecronapiintegrationlogicconditional
Categories:
Schedule TriggeredComplex Workflow
Integrations:
ConvertToFileSplitOutSchedule TriggerSticky NoteReadWriteFileExtractFromFileNoOp

Target Audience

Target Audience


- Security Analysts: Professionals monitoring data breaches for organizations.
- IT Administrators: Individuals responsible for maintaining data security and user privacy.
- Developers: Those looking to automate alerts for new data breaches in applications.
- Small Business Owners: Entrepreneurs who want to stay informed about potential threats to their customer data.
- Tech Enthusiasts: Individuals interested in learning about automation and data protection workflows.

Problem Solved

Problem Solved


This workflow addresses the challenge of staying updated on data breaches that could affect users. By automating the monitoring of breaches from haveibeenpwned.com, it ensures that users receive timely alerts about new breaches, enabling them to take necessary actions to secure their data and protect their privacy.

Workflow Steps

Workflow Steps


1. Trigger: The workflow begins either manually via a Test workflow button or automatically on a 15-minute schedule.
2. Request Breaches: It sends an HTTP request to haveibeenpwned.com to retrieve the latest breaches.
3. Read Last Breach: The workflow reads the last notified breach from a local cache file (./cache.json).
4. Check for New Breach: It compares the latest breach with the last notified one:
- If it’s a new breach, it proceeds to set the breach name and send an alert.
- If it’s an old breach, it skips the alert.
5. Update Cache: The workflow updates the cache file with the new breach information if applicable.
6. File Operations: It handles JSON file conversions and writes the latest breach data to the cache file.
7. Alerts: If a new breach is detected, the workflow triggers alerts (e.g., via Slack or email).

Customization Guide

Customization Guide


- Change Alert Method: Modify the alerting mechanism to integrate with different platforms (e.g., Slack, Discord) by replacing the NoOp nodes with appropriate notification nodes.
- Adjust Schedule: Modify the Schedule Trigger settings to change the frequency of checks (e.g., every 30 minutes instead of 15).
- Customize Cache File Path: Update the file paths in the ReadWriteFile nodes to store cache data in a different location.
- Add Additional Processing: Insert additional nodes after the Request breaches node to process or filter breaches based on specific criteria (e.g., severity, type of data breached).