New(releases) icon

New(releases)

A node to access project release informations

Actions9

Overview

This n8n node, New(releases), provides access to project release information from the NewReleases API. When configured with the Release resource and its default operation (which is "list"), it retrieves a list of releases for a specified project. This is useful for automating workflows that need to monitor, archive, or react to new software releases in projects tracked by NewReleases.

Common scenarios:

  • Monitoring open-source or internal project releases.
  • Triggering notifications or downstream processes when new releases are published.
  • Aggregating release data for reporting or analytics.

Example use case:
Automatically fetch all releases for a GitHub repository and send a summary to a Slack channel whenever a new release appears.

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). This identifies which project's releases you want to list.
Max Pages Number Maximum pages to fetch from New(releases) API. Each page returns up to 10 results. Controls how many releases are retrieved in total. (Default: 50)

Output

The node outputs an array of JSON objects, each representing a release for the specified project. The structure of each object depends on the NewReleases API, but typically includes fields such as:

{
  "id": "release-id",
  "name": "v1.2.3",
  "tag_name": "v1.2.3",
  "published_at": "2024-06-01T12:00:00Z",
  "body": "Release notes or description",
  // ...other metadata fields
}
  • Each item in the output array corresponds to a single release.
  • No binary data is produced by this operation.

Dependencies

  • External Service: Requires access to the NewReleases API.
  • Credentials: Needs a configured credential named newReleasesCredentialsApi in n8n.
  • Environment: No special environment variables required beyond standard n8n setup.

Troubleshooting

Common issues:

  • Invalid Project Identifier: If the "Project" value is incorrect or does not exist, the node may return an error or an empty result set.
  • API Key Missing or Invalid: If credentials are not set up correctly, authentication errors will occur.
  • Pagination Limits: If "Max Pages" is set too low, not all releases will be fetched; if set too high, may hit API rate limits.

Error messages and resolutions:

  • "Project not found": Double-check the "Project" identifier format and value.
  • "Unauthorized" or "Invalid API key": Ensure the correct credentials are configured in n8n.
  • "Too many requests": Lower the "Max Pages" value or implement rate limiting.

Links and References

Discussion