New(releases)

Overview

The Search Projects operation of the "New(releases)" n8n node allows users to search for projects within the NewReleases platform using a search string. This is useful in scenarios where you need to find projects by name, keyword, or other identifying information without knowing their exact slug or ID.

Common use cases:

• Automating project discovery workflows.
• Filtering and listing projects matching specific criteria.
• Integrating with other systems that require dynamic project lookup.

Example:
A user wants to find all projects related to "n8n" on NewReleases to monitor their releases or updates.

Properties

Output

The output is an array of JSON objects, each representing a project that matches the search criteria. Each object typically contains details about the project such as its name, provider, slug, and possibly other metadata provided by the NewReleases API.

Example output:

[
  {
    "id": "pf4w494lbjsd3ydp5hnf4gsptw",
    "name": "n8n-io/n8n",
    "provider": "github",
    "slug": "github/n8n-io/n8n",
    // ...other project fields
  }
]

Note: The exact structure depends on the NewReleases API response.

Dependencies

• External Service: Requires access to the NewReleases API.
• Credentials: Needs newReleasesCredentialsApi configured in n8n (API key or token).
• n8n Configuration: No special environment variables required beyond credentials.

Troubleshooting

Common issues:

• Invalid or missing credentials:
  Error message: "401 Unauthorized" or similar.
  Resolution: Ensure the correct API key/token is set up in n8n credentials.

• No results found:
  Error message: Returns an empty array.
  Resolution: Check your search string for typos or try broader keywords.

• API rate limits or downtime:
  Error message: "429 Too Many Requests" or "503 Service Unavailable".
  Resolution: Wait before retrying or check NewReleases status.

Links and References

• NewReleases API Documentation
• n8n Credentials Documentation
• Node Source Code Repository