This n8n workflow automates the process of monitoring new data breaches listed on haveibeenpwned.com and sends alerts when a new breach is detected. It periodically requests the latest breach data via a scheduled trigger, compares it with previous records stored locally, and then triggers alerts if a new breach is identified. The workflow also includes caching mechanisms and notifications to ensure efficient and timely updates.

Detailed steps include:

– A schedule trigger initiates the workflow every 15 minutes.

– It makes an HTTP request to haveibeenpwned.com API for the latest breaches.

– The breach data is converted from JSON and split for processing.

– The latest breach name is read from a local cache file. If the cache is empty, it initializes with a default value.

– The current latest breach is compared with the cached breach to identify whether it is new.

– If a new breach is detected, the name is stored in the cache, and an alert (via a NoOp node placeholder) is triggered.

– If the breach is recognized as previously seen, the workflow notes this and skips the alert.

– After processing, the cache is cleaned up by resetting the cache file.

– Additionally, sticky notes serve as documentation or instructions within the workflow to aid understanding and usage.

This workflow is ideal for cybersecurity teams, data breach monitoring services, or individuals keen on maintaining awareness of data security incidents for proactive responses.

Node Count	>20 Nodes
Nodes Used	convertToFile, extractFromFile, httpRequest, if, manualTrigger, merge, noOp, readWriteFile, scheduleTrigger, set, splitOut, stickyNote