Actions9
Overview
The Get Project operation of the "New(releases)" n8n node retrieves detailed information about a specific project from the NewReleases API. This is useful for workflows that need to fetch metadata or status about a project, either by its internal ID or by a provider/name combination (e.g., GitHub repository). Common scenarios include automating project monitoring, integrating project data into dashboards, or triggering actions based on project details.
Example use cases:
- Fetching project details to display in a report.
- Validating if a project exists before performing further automation.
- Retrieving project metadata for synchronization with other systems.
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). Used to identify which project to retrieve. |
Output
The output is a JSON object containing the project's details as returned by the NewReleases API. The structure typically includes fields such as:
{
"id": "pf4w494lbjsd3ydp5hnf4gsptw",
"provider": "github",
"name": "n8n-io/n8n",
"created_at": "2022-01-01T00:00:00Z",
"updated_at": "2022-06-01T12:34:56Z",
"email_notification": true,
"exclude_prereleases": false,
"exclude_updated": false,
"note": "",
"exclude_version_regexp": []
// ...other project-specific fields
}
Note: The exact fields depend on the API response and may include additional metadata.
Dependencies
- External Service: Requires access to the NewReleases API.
- Credentials: Needs a configured credential named
newReleasesCredentialsApiin n8n. - Environment: No special environment variables are required beyond standard n8n setup.
Troubleshooting
Common issues:
- Invalid Project Identifier: If the provided Project value does not match any existing project, the node will likely return an error or an empty result. Double-check the ID or provider/name format.
- Authentication Errors: If credentials are missing or invalid, you may see errors related to authentication failure. Ensure the
newReleasesCredentialsApicredential is set up correctly. - API Rate Limits or Downtime: If the NewReleases API is unavailable or rate-limited, requests may fail temporarily.
Error messages and resolutions:
"Project not found": Verify the Project input is correct and exists in NewReleases."401 Unauthorized": Check your API credentials in n8n."Network Error": Ensure n8n can reach the NewReleases API endpoint.
