Getting a community node verified by n8n in 2026: what it actually took

Description and use

The author details the steps taken to get their community node n8n-nodes-prisma-reviews verified by n8n in 2026, covering the use of the official CLI, publishing via GitHub Actions with npm provenance, keeping the repo and npm package in sync, and adding new webhook events based on community feedback.

Problem

How to get a community node verified by n8n so it appears in the n8n Cloud nodes panel without an install step.

Outcome

The node was successfully verified and published, enabling users to use it in n8n Cloud without manual installation, and the author added new webhook events based on community input.

Workflow

• Use the official @n8n/node-cli to run lint, build, and release commands.
• Run n8n-node lint on every commit to enforce strict lint rules (alphabetical options, style-compliant descriptions, credential test requests).
• Publish the package from GitHub Actions with npm provenance: bump version, push tag, run publish.yml workflow that lints, builds, and publishes with signed provenance.
• Ensure every npm release has a corresponding GitHub commit, tag, and CHANGELOG entry so the repo and package stay in sync.
• Listen to community feedback; add webhook events (location.sync_failed, location.sync_recovered) based on forum requests to improve node functionality.

Evidence

@n8n/node-cli gives you n8n-node build, n8n-node lint and n8n-node release.

Source

Since 1 May 2026 n8n only verifies packages published from GitHub Actions with npm provenance.

Source

Packages published from a laptop with npm publish do not get provenance and cannot be verified.

Source

n8n checks that what is on npm matches the public repo. Every version that goes to npm is a commit and a tag on GitHub first, with a CHANGELOG entry.

Source

The most useful feature in our latest release came from the n8n forum. A user asked how to tell "no new reviews" apart from "the check failed".

Source