Block 1 - Merge
- Type / Role
- n8n-nodes-base.merge - merge
- Config choices
- Version 3.1
This workflow is provided as-is. Please review and test before using in production.
Who it’s for Blue teamers, SOC operators, cyber analysts, and SME defenders who want to automatically enrich daily CVE/IOC threats by matching them to their internal asset database. Ideal for co...
n8n-nodes-base.merge, n8n-nodes-base.cron, n8n-nodes-base.function, n8n-nodes-base.googlesheets, n8n-nodes-base.emailsend, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Adnan Tariq.
Original n8n.io source👤 Who it’s for Blue teamers, SOC operators, cyber analysts, and SME defenders who want to automatically enrich daily CVE/IOC threats by matching them to their internal asset database. Ideal for compliance-driven teams (NIST CSF, Essential Eight) seeking automated enrichment and alert routing.
⚙️ How it works / What it does Loads current threat data from Sheet or Module 1 output
Loads internal asset database from Google Sheets
Merges based on matching IP fields
Calculates impact score (threat score × asset value)
Applies basic playbook logic to classify action
Sends summary emails for matched threats
Logs to archived and live threat monitoring sheets
Built with modular, no-code logic and alerting support
🛠️ How to set up Google Sheets: Authenticate your Google account (OAuth2) and set your Asset DB and Threats log sheet IDs.
Email: Add sender/recipient addresses and SMTP credentials.
Customize Matching Logic: Adjust enrichment rule in the “🧠 Match Threats to Assets” node.
Triggers: Add a Cron node or Webhook to schedule the enrichment job.
Review sticky notes: All steps are explained clearly within the workflow nodes.
📋 Requirements Google Sheets with asset inventory + threat log
Google account with Sheets API access
SMTP service (Gmail, Mailgun, SendGrid, etc.)
Optional: OpenAI for dynamic playbook scoring (if extending logic)
🧩 How to customize the workflow Replace Google Sheets with Supabase, Airtable, or Postgres
Extend enrichment rule to include hostname or UUID matching
Fine-tune scoring logic by severity, CVSS, or business unit
Route alerts via Slack, Discord, or n8n Webhook endpoints
Add conditional routing for alert suppression or review queues
📦 No sensitive data included. All credentials and sheet IDs are placeholders.
🔐 This module is part of the CYBERPULSEBlueOps Pro Pack. For full access to advanced Blue Team automations, visit cyberpulsesolutions.com/blueops
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | CYBERPULSE AI BlueOps: asset enrichment engine |
|---|---|
| Complexity | intermediate |
| Nodes | 10 |
| Categories | SecOps |
| Author | Adnan Tariq |
| Published | 25 Jul 2025 |
Use the JSON export at /data/workflows/6410/6410.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Who it’s for Blue teamers, SOC operators, cyber analysts, and SME defenders who want to automatically enrich daily CVE/IOC threats by matching them to their internal asset database. Ideal for co...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your SecOps use case.