Actions9
Overview
The Get Project Release operation of the "New(releases)" n8n node retrieves detailed information about a specific release for a given project. This is useful in scenarios where you need to fetch metadata or status about a particular software release, such as version details, changelogs, or release dates, from a project tracked by the New(releases) API.
Practical examples:
- Automatically fetching release data for deployment pipelines.
- Monitoring and reporting on the latest changes in a project's releases.
- Integrating release information into dashboards or notifications.
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 identifier of the specific release to retrieve information for. |
Output
The output is a JSON object containing the details of the specified project release. The structure typically includes fields such as:
{
"id": "release-id",
"name": "v1.2.3",
"project": "github/n8n-io/n8n",
"created_at": "2024-05-01T12:34:56Z",
"published_at": "2024-05-02T08:00:00Z",
"tag_name": "v1.2.3",
"description": "Release notes or changelog",
// ...other release-specific fields
}
Note: The exact fields depend on the API response.
Dependencies
- External Service: Requires access to the New(releases) API.
- API Credentials: You must configure the
newReleasesCredentialsApicredential in n8n with appropriate access rights.
Troubleshooting
Common issues:
- Invalid Project or Release Name: If the provided project or release does not exist, the node may return an error or empty result.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures.
- Network Issues: Connectivity problems between n8n and the New(releases) API endpoint can lead to timeouts or failed requests.
Error messages and resolutions:
"Project not found": Check that the Project value is correct and exists in the New(releases) system."Release not found": Ensure the Release Name matches an existing release for the specified project."401 Unauthorized": Verify your API credentials are set up correctly in n8n.
