Actions9
Overview
The Create Projects operation for the Project resource in this n8n node allows users to create a new project entry in the New(releases) system. This is useful for tracking software projects across various providers (such as GitHub, Docker Hub, PyPI, etc.) and configuring how you want to be notified about new releases or updates.
Common scenarios:
- Automatically adding new repositories or packages to your release monitoring workflow.
- Setting up custom notification preferences for different projects.
- Excluding certain versions or pre-releases from notifications using regex patterns.
Practical example:
A DevOps engineer wants to monitor a new open-source library on GitHub and receive weekly email notifications about its releases, excluding any beta or alpha versions.
Properties
| Name | Type | Meaning |
|---|---|---|
| Provider | options | The platform where the project is hosted (e.g., GitHub, Docker Hub, PyPI, etc.). |
| Project Name | string | A user-friendly name for the project. |
| Email_notification | options | Frequency of email notifications about project updates/releases (None, Daily, Weekly, etc.). |
| Exclude Pre-Releases? | boolean | Whether to exclude pre-release versions from notifications and tracking. |
| Exclude Updated? | boolean | Whether to exclude already updated projects from notifications. |
| Note | string (multi) | An optional note or description for the project. |
| Exclude Version Regex | fixedCollection | One or more regular expressions to exclude (or include, if "Include?" is checked) specific versions. |
Output
The output is a JSON object representing the newly created project. Typical fields may include:
{
"id": "string",
"name": "string",
"provider": "string",
"email_notification": "string",
"exclude_prereleases": true,
"exclude_updated": false,
"note": "string",
"exclude_version_regexp": [
{
"value": "regex_pattern",
"inverse": false
}
],
// ...other metadata fields
}
- The structure will reflect the properties sent, plus additional metadata such as project ID and timestamps.
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to the New(releases) API.
- API Credentials: You must configure
newReleasesCredentialsApiin n8n for authentication. - Environment: Ensure network access to the New(releases) API endpoint.
Troubleshooting
Common issues:
- Missing or invalid credentials: If the required API credentials are not set up, the node will fail with an authentication error.
- Invalid provider or project name: Using an unsupported provider or leaving the project name blank will result in an error from the API.
- Regex errors: Malformed regular expressions in "Exclude Version Regex" can cause the API to reject the request.
Error messages and resolutions:
"401 Unauthorized": Check that your API credentials are correctly configured in n8n."400 Bad Request": Review all input fields, especially required ones like Provider and Project Name. Also, check regex syntax."Network Error": Ensure n8n can reach the New(releases) API endpoint.