Community packages now manageable via Public API

n8n instances gain programmatic control over community nodes and packages. The Public API now includes dedicated endpoints for installing, listing, updating, and uninstalling community packages — work previously confined to the UI or command line.

Each operation maps to a distinct API key scope: communityPackage:install, communityPackage:list, communityPackage:update, and communityPackage:uninstall. This granularity lets administrators scope access precisely — an integration might list available packages without gaining install or uninstall permissions.

The endpoints delegate to the existing CommunityPackagesLifecycleService, which already handles npm operations, validation, and error management. A new mapper layer transforms the internal data structures into a clean API response format including package name, installed version, author details, included nodes, and update availability.

Community package management joins a growing list of programmable operations in the n8n API, enabling automation scenarios like batch node updates across multiple instances or scripted deployment pipelines that provision community nodes on demand.

This capability lands in the n8n CLI package, with OpenAPI specifications generated for documentation.