{"product_id":"have-i-been-pwned-breach-monitoring-n8n-workflow-15-min","title":"Have I Been Pwned Breach Monitoring n8n Workflow (15-min)","description":"\u003ch3\u003eStay ahead of data breaches with automated Have I Been Pwned monitoring every 15 minutes\u003c\/h3\u003e\n\u003cp\u003eThis n8n workflow checks the \u003cstrong\u003eHave I Been Pwned\u003c\/strong\u003e (HIBP) API every \u003cstrong\u003e15 minutes\u003c\/strong\u003e for new breaches, compares the latest results to what you’ve already seen, and triggers alerts only when something changes—complete with a simple \u003cstrong\u003ecache mechanism\u003c\/strong\u003e using \u003ccode\u003ecache.json\u003c\/code\u003e.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003ePolls the HIBP API every 15 minutes\u003c\/strong\u003e to retrieve the latest breach information.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eCompares current breach data\u003c\/strong\u003e against the previously notified breach.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eReads from a cache\u003c\/strong\u003e by retrieving the last known breach stored in \u003ccode\u003ecache.json\u003c\/code\u003e to avoid redundant notifications.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eDetects a new breach\u003c\/strong\u003e by checking whether the newly fetched breach differs from the cached one.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eUpdates the cache\u003c\/strong\u003e with the latest breach data when a change is detected.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSends alerts\u003c\/strong\u003e via a “New breach” node—so you can plug in your preferred notification steps.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eProactive identity protection:\u003c\/strong\u003e automate monitoring so you can respond quickly when new breaches appear.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSecurity awareness and reporting:\u003c\/strong\u003e let security professionals and developers track breach events without manual checking.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eDemonstrate cache behavior in n8n:\u003c\/strong\u003e a practical example of preventing duplicate alerts using \u003ccode\u003ecache.json\u003c\/code\u003e.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eNo API key required:\u003c\/strong\u003e the HIBP endpoint used in this workflow does not require an API key.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eCache logic:\u003c\/strong\u003e reads from \u003ccode\u003ecache.json\u003c\/code\u003e, compares the latest breach vs cached data, and updates the cache when new activity is detected.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003en8n nodes used:\u003c\/strong\u003e \u003ccode\u003eif\u003c\/code\u003e, \u003ccode\u003eset\u003c\/code\u003e, \u003ccode\u003eno op\u003c\/code\u003e, \u003ccode\u003emerge\u003c\/code\u003e, \u003ccode\u003esplit out\u003c\/code\u003e, plus a \u003ccode\u003esticky note\u003c\/code\u003e for guidance.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003cp\u003e\u003cstrong\u003eSetup tip:\u003c\/strong\u003e Add your alert mechanism in the red box after the \u003cstrong\u003eNew breach\u003c\/strong\u003e node—this node includes the breach data so your downstream notification is straightforward to build.\u003c\/p\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":45732303044787,"sku":"N8N-3205","price":14.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/o6vxd9vwRoa82S8ICVD4v_84gIu9U9.png?v=1785143409","url":"https:\/\/buyflowscripts.com\/products\/have-i-been-pwned-breach-monitoring-n8n-workflow-15-min","provider":"N8N Commerce","version":"1.0","type":"link"}