How oxapavan/ioc-extraction-through-n8n-automation works
Project type and purpose
• This is an event-driven integration/automation pipeline built on n8n.
• Its goal is to periodically fetch cyber threat articles via RSS, extract IOCs (domains, hashes, IPs, CVEs) using a third-party API, reformat them, and send them into a SIEM for automated threat detection.
“file_tree” and README
• Only two top-level entries: README.md (detailed workflow description) and assets/IOC.png (example flowchart).
• No code directories—this is a pure n8n workflow definition.
• All logic lives as individual n8n nodes configured via the UI or JSON.
Main components
a. n8n Server / Workflow Engine (logical container)
b. Cron Trigger Node (scheduler)
c. RSS Fetch Nodes (threatpost, bleepingcomputer, Krebs, TheHackerNews, SecurityWeek)
d. Split-In-Batches Nodes (one per feed)
e. Code Nodes (JavaScript snippets to extract URLs)
f. Combine & Aggregate URLs Nodes
g. Loop / Iterator Node (to process each URL)
h. Format URL Payload Node
i. IOC Parser API Node (HTTP Request to external parsing service)
j. Format IOC Output Node (structure results for SIEM)
k. SIEM Integration Node (HTTP Request or Syslog to Splunk/ELK/QRadar)
l. External Services:
• RSS feed providers (public threat-intel sites)
• IOC Parser API endpoint
• SIEM ingestion API endpoint
Relationships and data flow
• Cron Trigger → each RSS Fetch → corresponding Split Node → Code Node → Combine URLs
• Combined URLs → Aggregate → Loop → Format Payload → IOC Parser API → Format IOC Output → SIEM
• External RSS feeds as upstream data sources feeding into the n8n “RSS Fetch” components
• Two downstream external services (IOC Parser API, SIEM)
Architectural patterns and design principles
• ETL / data-pipeline pattern: extract (RSS), transform (split, code, format), load (SIEM)
• Event-driven scheduling via Cron
• Micro-service calls via HTTP (to IOC Parser API and SIEM)
• Modular, extensible node-based design: easy to add new RSS feeds or output targets
Technologies and frameworks
• n8n workflow engine (Node.js-based)
• Cron scheduling (built-in n8n trigger)
• JavaScript (for Code nodes)
• HTTP Request nodes (for external API calls)
• SIEM ingestion protocols (HTTP HEC for Splunk, REST for ELK, syslog for QRadar)
Detail level
• Every distinct node or logical group of nodes
• Retry or error-handling patterns if configured (e.g., n8n error‐trigger nodes)