Actions9
Overview
The Get Latest Project Release operation of the "New(releases)" n8n node retrieves information about the most recent, non-excluded release for a specified project. This is useful in automation scenarios where you need to monitor or react to new software releases, such as triggering notifications, updating documentation, or deploying new versions.
Practical examples:
- Automatically notify your team when a new version of an open-source library is released.
- Trigger CI/CD pipelines when a new release is published for a monitored project.
- Aggregate and report on the latest releases across multiple projects.
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 whose latest release should be fetched. |
Output
The output is a JSON object containing details about the latest release of the specified project. The structure typically includes fields such as:
{
"id": "release_id",
"name": "v1.2.3",
"tag_name": "v1.2.3",
"published_at": "2024-05-01T12:34:56Z",
"body": "Release notes or description",
"url": "https://...",
// ...other metadata fields depending on the API response
}
- The exact fields may vary based on the upstream API, but generally include identifiers, version/tag, publication date, description, and URLs.
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 are required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid Project Identifier: If the provided "Project" value does not match any known project, the node will likely return an error or empty result. Double-check the project slug or provider/name format.
- Missing Credentials: If credentials are not set up or are invalid, authentication errors will occur.
- API Rate Limits: Excessive requests may trigger rate limiting from the external service.
Error messages and resolutions:
"Project not found": Ensure the "Project" property is correct and the project exists in the external system."Unauthorized"or"Invalid credentials": Check that the correct credentials are configured in n8n."Network error": Verify network connectivity between n8n and the New(releases) API endpoint.