Publish a Duaer community node

Package requirements

• The name starts with n8n-nodes- or @<scope>/n8n-nodes-. Duaer refuses to install community packages named otherwise.
• The n8n key in package.json lists every node and credential.
• npm run lint passes, and you have tried the node in Duaer.
• The npm package or a public repository has a README covering the credential and each operation.

Publish to npm with provenance

From May 1, 2026, Duaer requires npm provenance on community packages. The Duaer community package scan fails a version without it. GitHub Actions signs the provenance, which proves the repository and commit that built the version. Publishing from your own machine carries no provenance.

1. Before the first release, open the package settings on npmjs.com, go to Trusted Publishers, and add GitHub Actions with the repository owner, repository name, and the workflow file name publish.yml. No long-lived token is needed.
2. Run the first command below to add the publish workflow. Projects created with npm create already have it.
3. Run npm run release. It bumps the version, commits, tags, and pushes. The tag starts the GitHub Actions publish to npm.

npx n8n-node release --init-workflow   # once: adds .github/workflows/publish.yml
npm run release                          # bump, tag, push; GitHub Actions publishes

If you cannot use Trusted Publishers, store NPM_TOKEN in the repository Actions secrets and the workflow uses it instead.

Install it in Duaer

1. As the owner or an admin of the Duaer instance, open Settings › Community nodes.
2. Enter the package name and accept the risk notice.
3. When the install finishes, search for the node in the node panel.

Read community node risks before you install.