Actions9
Overview
The List Project Releases operation of the "New(releases)" n8n node retrieves a list of releases for a specified project from the New(releases) API. This is useful for automating workflows that need to monitor, analyze, or act upon new software releases in projects tracked by this service.
Common scenarios:
- Automatically fetching all releases for a given project to trigger downstream actions (e.g., notifications, deployments).
- Aggregating release data for reporting or analytics.
- Keeping other systems synchronized with the latest release information.
Practical example:
A DevOps team could use this node to periodically check for new releases of an open-source dependency and trigger automated testing or deployment pipelines when a new version is detected.
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. |
| Max Pages | number | Maximum pages to fetch from the New(releases) API. Each page returns up to 10 results. Controls how many releases are retrieved in total. |
Output
The output is a JSON array where each item represents a single release of the specified project. The structure of each release object typically includes fields such as:
{
"id": "release-id",
"name": "Release Name",
"tag_name": "v1.2.3",
"created_at": "2024-01-01T12:00:00Z",
"published_at": "2024-01-02T12:00:00Z",
"body": "Release notes or description",
// ...other release metadata
}
Note: The exact fields depend on the API response but generally include identifiers, names, tags, timestamps, and descriptions.
Dependencies
- External Service: Requires access to the New(releases) API.
- Authentication: Needs valid credentials configured in n8n under
newReleasesCredentialsApi. - n8n Configuration: No special environment variables required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid Project Identifier: If the "Project" value is incorrect, the node may return an error or empty result. Double-check the project slug or ID.
- API Rate Limits: Fetching too many pages or making frequent requests may hit API rate limits.
- Missing Credentials: If credentials are not set up or are invalid, authentication errors will occur.
Error messages and resolutions:
"Project not found": Ensure the "Project" property is correct and the project exists in the New(releases) system."Unauthorized"or"Invalid credentials": Check and update your n8n credentials for the New(releases) API."Max pages exceeded": Lower the "Max Pages" value if you encounter performance issues or timeouts.