Actions15
Overview
This node integrates with the Redmine API, a project management web application. Specifically, for the Project - Update operation, it allows users to update details of an existing project in Redmine. This is useful when you want to modify project metadata such as description, homepage URL, enabled modules, visibility, parent project, or custom fields programmatically within an n8n workflow.
Practical examples include:
- Automatically updating project descriptions or settings based on external triggers.
- Enabling or disabling specific modules (like Issue Tracking or Wiki) for a project.
- Changing project visibility or hierarchy dynamically.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project to update. |
| Additional Fields | A collection of optional fields to update on the project: |
| - Custom Fields | Multiple custom fields can be set by specifying their ID and value. |
| - Description | Text description of the project. |
| - Enabled Modules | List of modules to enable for the project. Options include: Calendar, Documents, Files, Forums, Gantt, Issue Tracking, News, Repository, Time Tracking, Wiki. |
| - Homepage | URL of the project's homepage. |
| - Inherit Members | Boolean flag indicating whether the project should inherit members from its parent project. |
| - Is Public | Boolean flag indicating if the project is publicly visible. |
| - Parent ID | The ID of the parent project, establishing project hierarchy. |
Output
The node outputs JSON data representing the updated project information returned by the Redmine API after the update operation. This typically includes the project's current state reflecting all changes made.
If an error occurs during the update, the output will contain an error field with the error message.
No binary data output is produced by this node.
Dependencies
- Requires connection 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 credentials.
Troubleshooting
- Common issues:
- Invalid or missing Project ID will cause the update to fail.
- Incorrect API key or insufficient permissions may result in authorization errors.
- Providing invalid values for modules or custom fields might cause API validation errors.
- Error messages:
"error": "Project not found"indicates the specified Project ID does not exist.- Authorization errors suggest checking the API key and user permissions.
- Validation errors usually require verifying the format and allowed values of input fields.