NPM n8n INTEGRATION: AUTOMATE NPM WITH N8N

The Update Distribution Tag action allows you to programmatically modify distribution tags for your npm packages—a critical operation in release management workflows. Distribution tags like latest, next, beta, or canary help users install specific versions without knowing exact version numbers, and keeping them updated is essential for a smooth release process.

Configuration parameters:

• Credential to connect with: A required dropdown to select your authenticated Npm account. Ensure this credential has publish permissions for the target package.
• Resource: Set to "Distribution Tag" to work with npm's tagging system.
• Operation: Set to "Update" to modify an existing tag's target version.
• Package Name: A required text field where you enter the exact name of your npm package (e.g., @myorg/my-package).
• Package Version: A required text field specifying which version the tag should point to. Supports fixed values or n8n expressions for dynamic versioning.
• Distribution Tag Name: A required text field for the tag to update (e.g., latest, beta, next).

Typical use cases:

• Automatically update the latest tag after a successful production deployment
• Set a canary tag to the newest pre-release version after nightly builds
• Manage beta and stable tags as part of a staged rollout workflow
• Synchronize distribution tags across multiple packages in a monorepo release

When to use it: This action is essential for any automated release pipeline. Combine it with CI/CD webhooks or Jenkins triggers to ensure your distribution tags always reflect your current release state.

The Get All Distribution Tags action retrieves every distribution tag associated with a specific npm package, returning both the tag names and the versions they point to. This is invaluable for auditing, monitoring, and building dashboards that track your package's release status.

Configuration parameters:

• Credential to connect with: A required dropdown to select your Npm account credential for authentication.
• Resource: Set to "Distribution Tag" to query the package's tag configuration.
• Operation: Set to "Get All" to retrieve the complete list of tags.
• Package Name: A required text field where you specify which package's tags to retrieve. Accepts the full package name including scope if applicable.

Typical use cases:

• Build a monitoring dashboard showing current tag states across all your packages
• Verify tag consistency before triggering a deployment workflow
• Create audit reports tracking which versions are currently tagged for different release channels
• Compare distribution tags across multiple packages to ensure synchronized releases

When to use it: Use this action at the start of release workflows to check current tag states, or in scheduled workflows that generate regular reports on your package's distribution configuration. It pairs well with comparison logic to detect unexpected changes.

The Package Search action lets you query the npm registry to find packages matching specific criteria. This is the same search functionality available on npmjs.com, now accessible programmatically within your n8n workflows for discovery, analysis, and competitive research automation.

Configuration parameters:

• Credential to connect with: A required dropdown for selecting your Npm account credentials.
• Resource: Set to "Package" to indicate you're working with npm packages.
• Operation: Set to "Search" to query the registry.
• Query: An optional text field for your search terms. Leave empty for broad searches or enter specific keywords, package names, or descriptions.
• Limit: An optional number field controlling how many results to return. Default is 10, adjust based on your processing needs.
• Offset: An optional number field for pagination. Set to 0 to start from the first result, or use higher values to paginate through large result sets.

Typical use cases:

• Discover new packages in a specific domain and log them to a database for evaluation
• Monitor the npm ecosystem for packages similar to yours (competitive analysis)
• Build an internal tool that suggests relevant packages based on project requirements
• Create alerts when new packages matching certain keywords appear in the registry

When to use it: This action is perfect for building discovery and monitoring workflows. Combine it with scheduled triggers to regularly scan for new packages, or use it in response to team requests to automate package research and evaluation processes.

The Get Package Versions action retrieves the complete list of published versions for a specific npm package. This is essential for dependency monitoring, version tracking, and building automation that responds to new releases.

Configuration parameters:

• Credential to connect with: A required dropdown to select your authenticated Npm account.
• Resource: Set to "Package" to work with package data.
• Operation: Set to "Get Versions" to retrieve the version history.
• Package Name: A required text field specifying the exact package name to query (e.g., lodash, @types/node).

Typical use cases:

• Monitor critical dependencies and trigger alerts when new versions are published
• Build a changelog aggregator that fetches version lists and compares against previous runs
• Create an internal dashboard displaying version histories for all packages your team depends on
• Implement automated compatibility checks by comparing available versions against your requirements

When to use it: This action shines in monitoring and dependency management workflows. Schedule it to run periodically against your dependency list, compare results with previous runs, and trigger downstream actions (notifications, updates, tests) when new versions appear.

💡 TIP: Store the version list results in a database like MongoDB or Airtable between runs. This allows you to easily compare and detect new versions without maintaining complex workflow state.

The Get Metadata action retrieves comprehensive information about an npm package, including its description, repository links, maintainers, dependencies, and more. This is the richest data source available through the integration, perfect for building detailed reports and analysis workflows.

Configuration parameters:

• Credential to connect with: A required dropdown for your Npm account credential selection.
• Resource: Set to "Package" to access package information.
• Operation: Set to "Get Metadata" to retrieve detailed package data.
• Package Name: A required text field for the exact package name you want to query.
• Package Version: An optional text field to specify a particular version. If left blank or set to latest, returns metadata for the most recent published version.

Typical use cases:

• Generate automated security reports by extracting dependency lists and maintainer information
• Build an internal package registry that mirrors npm metadata for approved packages
• Create documentation by automatically pulling descriptions, repository links, and README content
• Monitor packages for maintainer changes or license updates that might affect compliance

When to use it: Use this action whenever you need detailed package information beyond just version numbers. It's particularly valuable for compliance workflows, documentation generation, and security auditing where you need access to the full metadata payload. For automated documentation workflows, consider integrating with Notion.