New(releases)

A node to access project release informations

Actions9

Release Actions
Project Actions

Overview

The Delete Project operation in the "New(releases)" n8n node allows users to delete a project from the NewReleases API. This is useful for managing and cleaning up projects that are no longer needed or were created by mistake. For example, if you have automated workflows that create projects for testing or temporary use, this operation can help you remove them programmatically.

Practical scenarios:

Automating cleanup of obsolete or test projects.
Integrating with CI/CD pipelines to remove projects after deployment or testing.
Managing project lifecycle directly from n8n without manual intervention.

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 delete.

Output

The output will be a JSON object (or array of objects) representing the response from the NewReleases API after attempting to delete the specified project(s). The exact structure depends on the API's response, but typically it may include status information or confirmation of deletion.

Example output:

[
  {
    "success": true,
    "message": "Project deleted successfully",
    "project": "github/n8n-io/n8n"
  }
]

Note: The actual fields may vary depending on the API implementation.

Dependencies

External Service: Requires access to the NewReleases API.
API Key/Credentials: You must configure the newReleasesCredentialsApi credential in n8n.
n8n Configuration: No special environment variables required beyond standard credential setup.

Troubleshooting

Common issues:

Invalid Project Identifier: If the provided project slug does not exist or is incorrect, the API may return an error such as "Project not found".
Missing Credentials: If credentials are not set up correctly, you may see authentication errors.
Insufficient Permissions: The API key used must have permission to delete projects; otherwise, you may receive a "Forbidden" or "Unauthorized" error.

How to resolve:

Double-check the "Project" value for typos or incorrect format.
Ensure your API credentials are valid and have the necessary permissions.
Review the API documentation for any additional requirements.