Actions15
Overview
This node integrates with the Redmine API to manage projects, issues, and users. Specifically, for the Project - Create operation, it allows users to create a new project in Redmine by specifying essential details such as the project's name and identifier, along with optional additional fields like description, homepage URL, enabled modules, visibility settings, parent project, and custom fields.
Common scenarios where this node is beneficial include:
- Automating project setup workflows when onboarding new teams or clients.
- Creating standardized project templates programmatically.
- Integrating project creation into larger automation pipelines involving issue tracking or user management.
Example use case: Automatically create a new project in Redmine whenever a new client is added to a CRM system, setting up necessary modules and permissions based on client type.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the project to be created. |
| Identifier | A unique identifier for the project, used in URLs. |
| Additional Fields | Optional extra settings for the project, including: |
| Description | A textual description of the project. |
| Homepage | URL of the project's homepage. |
| Enabled Modules | List of modules to enable for the project. Options include: Calendar, Documents, Files, Forums, Gantt, Issue Tracking, News, Repository, Time Tracking, Wiki. |
| Inherit Members | Boolean flag indicating whether the project should inherit members from its parent project. |
| Is Public | Boolean flag indicating if the project is public (visible to all users). |
| Parent ID | The ID of the parent project under which this project will be nested. |
| Custom Fields | Custom fields can be added as key-value pairs, allowing for additional metadata specific to the user's Redmine setup. |
Output
The node outputs an array of JSON objects representing the created project(s). Each output item contains the full response from the Redmine API for the created project, typically including fields such as project ID, name, identifier, description, enabled modules, and other metadata.
If binary data were involved (not applicable here), it would be summarized accordingly, but this operation deals solely with JSON data.
Dependencies
- Requires access to a Redmine instance via its REST API.
- Needs an API key credential for authentication with Redmine.
- The node expects the Redmine base URL and API key to be configured in the node credentials.
- No additional external dependencies beyond the Redmine API.
Troubleshooting
Common Issues:
- Invalid or missing API key: The node will fail to authenticate with Redmine.
- Duplicate project identifier: Redmine requires unique identifiers; attempting to create a project with an existing identifier will cause an error.
- Missing required fields: Both "Name" and "Identifier" are mandatory; omitting them will result in validation errors.
- Incorrect module names or custom field IDs may cause the API to reject the request.
Error Messages:
- Authentication errors usually indicate invalid API credentials.
- Validation errors from Redmine will specify which fields are incorrect or missing.
- Network or connectivity errors suggest issues reaching the Redmine server URL.
Resolution Tips:
- Verify API key correctness and permissions.
- Ensure the project identifier is unique within Redmine.
- Double-check all required fields are provided.
- Confirm the Redmine URL is reachable and correct.