New(releases) icon

New(releases)

A node to access project release informations

Actions9

Overview

The New(releases) node for n8n allows you to interact with project release information from the New(releases) API.
Specifically, when using the Release resource and the Get Project Release Notes operation, this node retrieves the release notes for a specific release of a given project.
This is useful in scenarios where you want to automate the collection, aggregation, or notification of release notes for software projects—such as sending release notes to a Slack channel, archiving them, or triggering further workflows based on new releases.

Practical examples:

  • Automatically fetch and email release notes to your team whenever a new version is published.
  • Aggregate release notes from multiple projects into a changelog document.
  • Trigger downstream processes (e.g., deployments, notifications) based on the content of release notes.

Properties

Name Type Meaning
Project String Can be either the project internal ID (e.g. pf4w494lbjsd3ydp5hnf4gsptw), or provider/name (e.g. github/n8n-io/n8n). Identifies the project.
Release Name String The name or tag of the release whose notes you want to retrieve.

Output

The node outputs the release notes for the specified project and release.
The structure of the output will typically include a JSON object containing the release note details as returned by the New(releases) API.
While the exact fields depend on the API response, you can expect at least:

{
  "note": "Release notes text...",
  // ...other possible metadata fields depending on the API
}
  • The main field of interest is likely to be note, which contains the textual release notes.

Dependencies

  • External Service: Requires access to the New(releases) API.
  • API Credentials: You must configure the newReleasesCredentialsApi credential in n8n for authentication.
  • n8n Configuration: No special environment variables are required beyond standard credential setup.

Troubleshooting

Common Issues:

  • Invalid Project or Release Name: If the Project or Release Name values are incorrect or do not exist, the node may return an error or an empty result.
  • Missing Credentials: If the required credentials are not set up, the node will fail to authenticate with the API.
  • API Rate Limits or Downtime: If the New(releases) API is unavailable or rate-limited, requests may fail.

Error Messages and Resolutions:

  • "Project not found" or "Release not found": Double-check that the Project and Release Name values are correct and exist in the system.
  • "Authentication failed": Ensure that the newReleasesCredentialsApi credential is correctly configured in n8n.
  • "Network error" or timeouts: Check your network connection and the availability of the New(releases) API.

Links and References

Discussion