← All plugins
NUCLEIbeta

Nuclei

Template-based vulnerability scanning with the embedded ProjectDiscovery nuclei engine — run scans, preview and search 13,000+ templates by filter, update the catalog, and validate custom templates against targets a flow provides. Active scanning, gated by per-connection safety settings.

SDK
Go
Protocol
inflowv1
Actions
6
Version
v0.1.0
Author
Venapce
Runs on
Any inflowv1 host
Categories
DevOps and infrastructureUtility

Reach for it when

Template-based vulnerability scanning inside a flow, with templates chosen by filter rather than one at a time.

The use people don't expect

A finding on its own is a severity and a hostname. In a flow it can be joined to what the host actually is — the service on it, the database it talks to, the team on call — before anyone is paged.

A flow that uses it

Each one is a shape of flow, not a template to copy. Node names are the labels as they appear on the canvas; a name with a slash means either would do.

01

Findings that arrive with their context

Starts withA schedule, or a new asset appearing in the inventory.

  1. NUCLEI

    Scans the targets the flow supplies, templates picked by severity and tag. Findings stream as they match.

  2. POSTGRES

    Looks up what each host is and who owns it.

  3. ZVEC / QDRANT

    Finds past findings that look like this one and how they were resolved.

  4. CLAUDE AGENT

    Writes the triage note: what this drags with it, what it probably needs.

  5. JIRA

    One ticket, already readable, assigned to the right team.

What you getAlert fatigue is mostly a context problem. Beta, and it scans whatever you point it at — authorisation is on you.

The reference, not the pitch

This page is about what the plugin is for. Every action, every connection field, the ports, the install one-liner and the caveats are in the catalog entry, which is the thing the maintainer updates.

Near it in the catalog