MCP and automation

How to integrate Vexday with n8n: ready-made workflows to download

Download ready-made workflows that take Vexday to where the team already works: a CVE analysis, alerts in Jira, the Wazuh queue, the monthly report per client, the weekly bulletin, a supplier on a leak site and ransomware identification. No AI required and no key in the file.

  • Who it's forFor SOCs and MSSPs that automate with n8n.
  • PlanSOC and MSSP plans
  • Timeabout 15 min

What you need

  • A Vexday account on the SOC or MSSP plan.
  • A self-hosted or cloud n8n, on the latest 1.x series or on 2.x.
  • The credentials for the destination the workflow uses: Jira, Wazuh, SMTP, Slack, Discord or Teams.

Step by step

  1. Create the key

    In the Vexday dashboard, open Integrations and click New key. Copy the key right away: it starts with vx_live_ and is shown only once. The Jira alerts workflow does not use the key: it receives the alert webhook.

  2. Create the credential in n8n

    Under Credentials, create a Header Auth credential named Vexday API: in Name, Authorization; in Value, Bearer followed by the key. It stays in n8n and never goes into the workflow file.

    Name:  Authorization
    Value: Bearer vx_live_SUA_CHAVE
  3. Download and import the workflow

    Pick the workflow in the list below and download the JSON (or the bundle with all of them). In n8n, open Workflows, use Import from file and choose the file.

  4. Attach the credentials

    Select the Vexday API credential on every Vexday MCP node and protect the triggers with the credential each one asks for: Basic Auth on the form and on the run and report webhooks; Header Auth on the CVE analysis and ransomware identification webhooks. n8n does not publish a workflow with a node missing its credential: if you will not use a trigger, delete it.

  5. Adjust Config and publish

    In the Config node, fill in the channels (Slack, Discord, Teams or a JSON POST), the language and, on MSSP, the client tag. Publish and run the Executar agora webhook once: the editor's test run does not save the cache or the last report.

The workflows to download

Version 0.9.1. Each file is a workflow to import into n8n, with no key or credential inside. Node names are in Portuguese.

Download all (zip, 97 KB)

T00 CVE analysis

A form or a webhook takes the CVE ID and returns the report: priority, exploitation, actors, Brazilian government alerts, impact on your stack, ransomware use, mitigation and detection.

Plan
SOC and MSSP
Cost
3 calls per analysis
Needs
the protected form or webhook; channels are optional
Download the JSON (97 KB) ↓SHA-256 b04dfcb167a20d85de6db9a8b1a56c6df046d2aef349349970e41acc260b665d

T01 Alerts to Jira

Receives Vexday's alert webhook, checks the signature and keeps one ticket per CVE and client: it creates, comments, raises the priority and opens a new one when the CVE escalates after being closed.

Plan
SOC and MSSP
Cost
no calls: it uses the webhook alerts
Needs
Jira Cloud and a JSON endpoint destination in the dashboard
Download the JSON (124 KB) ↓SHA-256 17f507ad8fc844db03efd8f5c36b3b5b2823a665066a7cfb427b3a056259eab7

T02 Wazuh: what to fix first

Matches Wazuh's vulnerabilities against the KEV and Vexday's risk and returns the queue of what to fix first, with how many agents each CVE hits and ransomware use at the top of the queue.

Plan
SOC and MSSP
Cost
the whole KEV per run, plus enrichment, with a 7-day cache
Needs
Wazuh 4.8 or newer, with a read-only user on the index
Download the JSON (162 KB) ↓SHA-256 0d3dee4b2b1a8886d583642a921e62af3f09853cfc9bfb84ec905a446bb0d7a1

T03 Monthly report per client

On the 1st of every month, it emails each client a report with the MSSP's brand: their stack that month and the Brazil picture compared with the month before. AI is optional and only writes the text.

Plan
SOC and MSSP
Cost
1 call per client per month
Needs
an SMTP server; AI is optional
Download the JSON (81 KB) ↓SHA-256 8988c8e9b5ff7c57352dbc427842b5570c1c29c4a8e2f2137fcd972ec4cdb372

T04 Weekly threat bulletin

Every Monday, your stack's alerts, the verified incidents in the country and the week's ransomware by sector, as a chat summary and a full page.

Plan
SOC and MSSP
Cost
3 calls per bulletin
Needs
the channels and the sectors you follow
Download the JSON (63 KB) ↓SHA-256 ddaa6ce03d0f5bd9dad8397d759878c393abe915175dcf6c913d0f782f845930

T05 Compromised supplier

Every 4 hours, it compares recent victims on ransomware leak sites with your supplier list and alerts with the group's profile, the detection pack and a compromised-third-party playbook. Appearing on a leak site is the group's claim.

Plan
SOC and MSSP
Cost
3 calls per run, plus 2 per group found
Needs
the supplier list, with name and domain
Download the JSON (63 KB) ↓SHA-256 f3ea5c0c9de450a0c8279753bbabb6388ddd69890462336dc6f747aff709368e

T06 Ransomware identification

From the extension, the ransom note, the hash, the family or the group, it points to the likely family with the evidence, the public recovery tool (official link only), the guide and the detection pack.

Plan
SOC and MSSP
Cost
2 to 5 calls per identification
Needs
the protected form or webhook
Download the JSON (121 KB) ↓SHA-256 e229d1c973d6354846e84765e75c73022a5cd51a7765ed4bbe23d8ae6fb0a1ca

Something went wrong?

The workflow stops with "Chave da API do Vexday inválida ou revogada (HTTP 401)"The credential's Value is missing the Bearer or the key was revoked. Check the Vexday API credential and, if needed, create another key under Integrations.
Vexday's per-minute limit shows upThe workflows already space out their calls, but the ones running at the same time share the account's limit. Do not schedule the Wazuh one, the monthly report and the supplier one in the same minute.
n8n will not publishA node is missing its credential. Attach the credential or delete the node you will not use, such as the spare trigger.
The cache or the last report disappearsn8n only saves that data on a production run. Run it on the schedule or through the Executar agora webhook, not the editor's test run.

Frequently asked questions

Do the workflows need AI?

No. The queries are deterministic and every number comes from Vexday. Only the monthly report has an optional AI step, which writes the text and is discarded if it cites a number or CVE that is not in the data.

Does my key end up in the workflow file?

No. The key stays in the n8n credential, and the exported file carries no credentials. The alert signature secret lives in a node of the Jira workflow: do not export that workflow with the secret filled in.

Do the workflows work in Spanish and English?

Node names and messages are in Portuguese. The CVE analysis and ransomware identification reports come out in Portuguese, Spanish or English, set by the language field.

Can I use Vexday in an n8n AI agent?

Yes, with the MCP Client Tool node, using the same address and the same key. The steps are in the guide on connecting the MCP to your assistant.

Keep going