For no-code & automation teams

Security testing, in your workflow

You already orchestrate work in n8n. Darkmoon ships a community node so a pentest becomes just another step: trigger it, collect findings, and route its fix pull requests to whoever should review them.

Clone on GitHub Get the n8n node

Your wedge

A node, not a project

Automation teams should not have to write a client to run a pentest.

One n8n node

n8n-nodes-darkmoon triggers a Darkmoon pentest, retrieves its findings, and surfaces the fix pull requests it prepares — inside your existing flows.

Recurring by design

Darkmoon's scheduler runs none, daily, weekly or monthly, and one-shot schedules disable themselves after firing — so recurring assurance is a setting, not a chore.

Reviewed, never merged

Any fix the remediation engine proposes arrives as a pull request for a human to review. Automation triggers the work; it never rubber-stamps a merge.

What you get

What the node lets you build

Trigger on any event
Kick off a pentest from a schedule, a webhook, a deploy notification or any other n8n trigger, then fan the results out to Slack, a ticket, or an email.
Findings as structured data
Pull findings back into the workflow as data you can filter, threshold and route — so a critical finding can page someone while a low one just files a ticket.
Fix PRs in the loop
Review the pull requests the remediation engine prepares from inside your automation, and hand them to the right reviewer.

Start here