n8n-nodes-keygate

Community node for n8n that integrates a self-hosted Keygate server with guided operations for admin workflows, public licensing flows, portal seat management, release distribution, and a Custom API Request escape hatch.

Installation

Follow the n8n community node installation guide.

Operations

This version includes guided coverage for:

• Products
• Plans
• Licenses
• API keys
• Webhooks
• Addons
• Analytics
• Audit logs
• Users
• Team
• Settings
• System
• Releases
• Signing keys
• Public license endpoints
• Portal seats
• Invite acceptance
• Release feeds
• Custom API requests

Credentials

Create a Keygate API credential in n8n with:

• Server URL: your Keygate base URL, for example http://localhost:9000
• Access Mode: Admin API Key, Portal Session Cookie, or Public Endpoints Only
• Admin API Key when using /admin/*
• Portal Session Cookie when using /portal/*
• Node License Key

The node is already prepared for commercial licensing. In the current development phase it accepts any Node License Key with 10 or more characters.

Compatibility

• Built from the official @n8n/node scaffold
• Designed for current n8n community-node packaging requirements as of May 15, 2026
• Public-facing docs and README are kept in English to stay compatible with future verification requirements

Usage

The node prioritizes guided fields for common operations and leaves JSON Input available for advanced or newly introduced request fields. For admin areas that change quickly in Keygate, Custom API Request keeps the integration usable without waiting on a package update.

The node is also marked as usableAsTool and offers:

• Simplified response mode for agents and compact workflows
• Raw response mode for debugging and full-fidelity automation

Resources

• n8n creating nodes docs
• n8n community node build guidance
• Keygate OpenAPI
• Keygate repository

Development

npm install
npm run lint
npm run build

Publishing

This package is prepared to publish through GitHub Actions with npm provenance.

Recommended setup:

1. Push the code to the final GitHub repository that matches package.json repository.url.
2. On npmjs.com, create the package or reserve the name if needed.
3. In npm package settings, add a Trusted Publisher for:
   • GitHub owner: your user or org
   • Repository: this repo
   • Workflow: publish.yml
4. Publish by pushing a semver tag such as 0.1.0.

Fallback setup:

• If you cannot use trusted publishing yet, add NPM_TOKEN as a GitHub Actions secret. The workflow already supports it through NODE_AUTH_TOKEN.

The CI workflow validates lint, build, and npm pack --dry-run on every push to main and every pull request.

Version History

• 0.1.0: initial programmatic Keygate node scaffold with broad API coverage, centralized transport, local node-license validation, and AI-tool-oriented output mode