Actions15
Overview
This node integrates with the Redmine API, a project management web application. It allows users to interact with various Redmine resources such as Issues, Projects, and Users. Specifically, for the Issue - Get operation, the node retrieves detailed information about a single issue identified by its Issue ID.
Common scenarios include:
- Fetching the current status, description, or other details of a specific issue in a Redmine project.
- Automating workflows that require issue data retrieval, such as syncing issues with other tools or generating reports.
- Triggering subsequent actions based on issue properties (e.g., priority, assigned user).
Example use case: Automatically retrieve an issue's details when a new comment is added elsewhere, to update a dashboard or notify stakeholders.
Properties
| Name | Meaning |
|---|---|
| Issue ID | The unique identifier of the issue to retrieve from Redmine. This is a required string. |
Output
The node outputs JSON data representing the retrieved issue's details from Redmine. This typically includes fields such as issue ID, subject, description, status, priority, assigned user, creation and update timestamps, and any custom fields defined in Redmine.
If the node encounters an error (e.g., issue not found), it outputs a JSON object containing an error field with the error message.
The node does not output binary data.
Dependencies
- Requires access to a Redmine instance URL.
- Needs an API key credential for authenticating requests to the Redmine API.
- The node expects these credentials to be configured within n8n prior to execution.
Troubleshooting
Common issues:
- Invalid or missing Issue ID will cause the API call to fail.
- Incorrect or expired API key will result in authentication errors.
- Network connectivity problems to the Redmine server can cause request failures.
- Requesting an issue ID that does not exist returns an error.
Error messages:
"Issue not found": Verify the Issue ID is correct and exists in the Redmine project."Authentication failed"or similar: Check that the API key is valid and has sufficient permissions.- Network errors: Ensure the Redmine URL is reachable from the n8n environment.
To handle errors gracefully, enable the "Continue On Fail" option in the node settings to prevent workflow interruption and capture error details in the output.