Monitor vendor outages and breaches with Bright Data, GPT-5.6 and Slack
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 24 nodes and runs on a schedule (every day at 07:00) (plus 1 other trigger). Along the way it connects OpenAI Chat Model, Slack and Gmail. It also calls api.brightdata.com over HTTP.
How it runs
Trigger: On a schedule (every day at 07:00) (plus 1 other trigger).
- Settings (Edit Fields (Set)): sets 10 fields: your_site, also_watch, max_vendors…
- Read Your Site (HTTP Request): calls api.brightdata.com (POST)
- Map Your Vendor Stack (Code): runs custom JavaScript code
- Check Status Pages (HTTP Request): calls api.brightdata.com (POST)
- Only The Ones Worth Watching (Filter): keeps only the items that match a condition
- Read The Status Board (Code): runs custom JavaScript code
- Search Vendor News (HTTP Request): calls api.brightdata.com (POST)
- Combine Both Signals (Merge): merges the data from its input branches
- Read The Headlines (Code): runs custom JavaScript code
- Recall Last Check (Data table): get
…plus 9 more steps. See the full node list below.
Services it uses
HTTP calls to: api.brightdata.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (15)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - n8n Form Trigger
n8n-nodes-base.formTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Filter
n8n-nodes-base.filter - Merge
n8n-nodes-base.merge - Data table
n8n-nodes-base.dataTable - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Information Extractor
@n8n/n8n-nodes-langchain.informationExtractor - Switch
n8n-nodes-base.switch - Slack
n8n-nodes-base.slack - Gmail
n8n-nodes-base.gmail
From the author
Quick Overview This workflow monitors the third-party vendors your website depends on by fetching your homepage via Bright Data, checking each vendor’s Statuspage API and recent news, comparing results against a stored baseline, and sending change-based…