Actions37
- Issue Actions
- Lead Actions
- Opportunity Actions
- Account Actions
- Attendance Actions
- Personal Contact Actions
- Time Entry Actions
- User Actions
Overview
This node integrates with Easy Redmine to perform various operations on different resources such as Issues, Leads, Opportunities, Accounts, and others. Specifically, for the Issue resource with the Get One operation, it retrieves a single issue by its unique identifier. This is useful when you need detailed information about a specific issue in your project management workflow.
Practical examples include:
- Fetching details of a particular bug or task by its ID to display or process further.
- Retrieving an issue before updating or adding comments to ensure you have the latest data.
- Integrating issue details into reports or dashboards dynamically.
Properties
| Name | Meaning |
|---|---|
| Issue ID | The unique numeric identifier of the issue to retrieve. |
The property "Issue ID" must be provided when using the Get One operation on the Issue resource.
Output
The output is a JSON array containing one object representing the requested issue's data as returned by Easy Redmine's API. The structure includes all fields related to the issue, such as title, description, status, priority, assignee, and other metadata defined by Easy Redmine.
If the node encounters an error (e.g., issue not found), the output will contain an error message describing the problem.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Easy Redmine via an API key credential configured in n8n.
- The node uses the base URL from the credential's domain setting.
- The node expects JSON responses from Easy Redmine's REST API.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Issue ID will result in an error indicating the issue was not found.
- Network or authentication errors if the API key or domain is misconfigured.
- Rate limiting or permission errors from Easy Redmine if the API user lacks access rights.
Error messages:
- Errors returned by the API are captured and presented in the output under an
errorfield. - If the node is set to continue on failure, errors for individual items will appear inline without stopping execution.
- To resolve errors, verify the Issue ID exists, check API credentials, and ensure proper permissions.
- Errors returned by the API are captured and presented in the output under an