Actions15
Overview
This node integrates with the Redmine API, a project management web application. It allows users to perform various operations on Redmine resources such as Issues, Projects, and Users. Specifically, for the Issue - Get operation, the node retrieves detailed information about a specific issue by its ID.
Common scenarios where this node is beneficial include:
- Fetching issue details to display or process in workflows.
- Automating reporting or notifications based on issue data.
- Integrating Redmine issue tracking with other tools or systems.
For example, you might use this node to get the status and description of an issue when a related event occurs elsewhere, enabling automated updates or alerts.
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 date, update date, and any custom fields associated with the issue.
If the node encounters an error (e.g., invalid issue ID), 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 before 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.
Error messages:
"error": "Issue not found"indicates the specified Issue ID does not exist.- Authentication errors usually mention unauthorized access or invalid credentials.
Resolutions:
- Verify the Issue ID is correct and exists in Redmine.
- Ensure the API key is valid and has sufficient permissions.
- Check network connectivity and Redmine server availability.
- Enable "Continue On Fail" option in the node settings to handle errors gracefully in workflows.