Skip to main content

Automate SIEM alert enrichment with MITRE ATT&CK, Qdrant & Zendesk in n8n

Workflow preview

Workflow preview
100%
Automate SIEM alert enrichment with MITRE ATT&CK, Qdrant & Zendesk in n8n preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

n8n Workflow: Automate SIEM Alert Enrichment with MITRE ATT&CK & Qdrant Who is this for? This workflow is ideal for: Cybersecurity teams & SOC analysts who want to automate SIEM alert enrichment . ...

Best for

  • SecOps automation workflows
  • AI RAG automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

@n8n/n8n-nodes-langchain.chattrigger, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.splitout, @n8n/n8n-nodes-langchain.embeddingsopenai, @n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.textsplittertokensplitter, @n8n/n8n-nodes-langchain.memorybufferwindow

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Angel Menendez.

Original n8n.io source

1.1 Workflow description

Title
Automate SIEM alert enrichment with MITRE ATT&CK, Qdrant & Zendesk in n8n
Workflow name
Automate SIEM alert enrichment with MITRE ATT&CK, Qdrant & Zendesk in n8n

n8n Workflow: Automate SIEM Alert Enrichment with MITRE ATT&CK & Qdrant


Who is this for?

This workflow is ideal for:

  • Cybersecurity teams & SOC analysts who want to automate SIEM alert enrichment.
  • IT security professionals looking to integrate MITRE ATT&CK intelligence into their ticketing system.
  • Organizations using Zendesk for security incidents who need enhanced contextual threat data.
  • Anyone using n8n and Qdrant to build AI-powered security workflows.

What problem does this workflow solve?

Security teams receive large volumes of raw SIEM alerts that lack actionable context. Investigating every alert manually is time-consuming and can lead to delayed response times. This workflow solves this problem by:
Automatically enriching SIEM alerts with MITRE ATT&CK TTPs.
Tagging & classifying alerts based on known attack techniques.
Providing remediation steps to guide the response team.
Enhancing security tickets in Zendesk with relevant threat intelligence.


What this workflow does

1️⃣ Ingests SIEM alerts (via chatbot or ticketing system like Zendesk).
2️⃣ Queries a Qdrant vector store containing MITRE ATT&CK techniques.
3️⃣ Extracts relevant TTPs (Tactics, Techniques, & Procedures) from the alert.
4️⃣ Generates remediation steps using AI-powered enrichment.
5️⃣ Updates Zendesk tickets with threat intelligence & recommended actions.
6️⃣ Provides structured alert data for further automation or reporting.


Setup Guide

Prerequisites

Steps to Set Up

1️⃣ Embed MITRE ATT&CK data into Qdrant

  • This workflow pulls MITRE ATT&CK data from Google Drive and loads it into Qdrant.
  • The data is vectorized using OpenAI embeddings for fast retrieval.

2️⃣ Deploy the n8n Chatbot

  • The chatbot listens for SIEM alerts and sends them to the AI processing pipeline.
  • Alerts are analyzed using an AI agent trained on MITRE ATT&CK.

3️⃣ Enrich Zendesk Tickets

  • The workflow extracts MITRE ATT&CK techniques from alerts.
  • It updates Zendesk tickets with contextual threat intelligence.
  • The remediation steps are included as internal notes for SOC teams.

How to Customize This Workflow

🔧 Modify the chatbot trigger: Adapt the chatbot node to receive alerts from Slack, Microsoft Teams, or any other tool.

🔧 Change the SIEM input source: Connect your workflow to Splunk, Elastic SIEM, or Chronicle Security.

🔧 Customize remediation steps: Use a custom AI model to tailor remediation responses based on organization-specific security policies.

🔧 Extend ticketing integration: Modify the Zendesk node to also work with Jira, ServiceNow, or another ITSM platform.


Why This Workflow is Powerful

Saves time: Automates alert triage & classification.
Improves security posture: Helps SOC teams act faster on threats.
Leverages AI & vector search: Uses LLM-powered enrichment for real-time context.
Works across platforms: Supports n8n Cloud, Self-hosted, and Qdrant.


🚀 Get Started Now!

📖 Watch the Setup Video
💬 Have Questions? Join the Discussion in the YouTube Comments!

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - When chat message received

Type / Role
@n8n/n8n-nodes-langchain.chatTrigger - chatTrigger
Config choices
Version 1.1

Block 2 - AI Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 1.7

Block 3 - OpenAI Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1

Block 4 - Split Out

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 5 - Embeddings OpenAI1

Type / Role
@n8n/n8n-nodes-langchain.embeddingsOpenAi - embeddingsOpenAi
Config choices
Version 1.2

Block 6 - Default Data Loader

Type / Role
@n8n/n8n-nodes-langchain.documentDefaultDataLoader - documentDefaultDataLoader
Config choices
Version 1

Block 7 - Token Splitter1

Type / Role
@n8n/n8n-nodes-langchain.textSplitterTokenSplitter - textSplitterTokenSplitter
Config choices
Version 1

Block 8 - Window Buffer Memory

Type / Role
@n8n/n8n-nodes-langchain.memoryBufferWindow - memoryBufferWindow
Config choices
Version 1.3

Block 9 - Embeddings OpenAI2

Type / Role
@n8n/n8n-nodes-langchain.embeddingsOpenAi - embeddingsOpenAi
Config choices
Version 1.2

Block 10 - Extract from File

Type / Role
n8n-nodes-base.extractFromFile - extractFromFile
Config choices
Version 1

Block 11 - When clicking ‘Test workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 12 - AI Agent1

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 1.7

Block 13 - OpenAI Chat Model1

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1

Block 14 - Embeddings OpenAI

Type / Role
@n8n/n8n-nodes-langchain.embeddingsOpenAi - embeddingsOpenAi
Config choices
Version 1.2

Block 15 - Loop Over Items

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 16 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Structured Output Parser

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.2

Block 20 - Pull Mitre Data From Gdrive

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 21 - Embed JSON in Qdrant Collection

Type / Role
@n8n/n8n-nodes-langchain.vectorStoreQdrant - vectorStoreQdrant
Config choices
Version 1

Block 22 - Query Qdrant Vector Store

Type / Role
@n8n/n8n-nodes-langchain.vectorStoreQdrant - vectorStoreQdrant
Config choices
Version 1

Block 23 - Qdrant Vector Store query

Type / Role
@n8n/n8n-nodes-langchain.vectorStoreQdrant - vectorStoreQdrant
Config choices
Version 1

Block 24 - Get all Zendesk Tickets

Type / Role
n8n-nodes-base.zendesk - zendesk
Config choices
Version 1

Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Automate SIEM alert enrichment with MITRE ATT&CK, Qdrant & Zendesk in n8n
Complexity advanced
Nodes 26
Categories SecOps, AI RAG
Author Angel Menendez
Published 03 Feb 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/2840/2840.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does Automate SIEM alert enrichment with MITRE ATT&CK, Qdrant & Zendesk in n8n do?

n8n Workflow: Automate SIEM Alert Enrichment with MITRE ATT&CK & Qdrant Who is this for? This workflow is ideal for: Cybersecurity teams & SOC analysts who want to automate SIEM alert enrichment . ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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, AI RAG use case.