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 "Project" resource with the "Get Many" operation, the node fetches multiple projects from Redmine based on user-defined filters and limits.
Common scenarios include:
- Retrieving a list of all projects or a subset filtered by status (open, closed, or all).
- Automating reporting or synchronization tasks that require bulk project data.
- Integrating project information into other workflows or dashboards.
Example: A user wants to get all open projects to generate a report on active workstreams.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching projects or limit the number of results returned. |
| Limit | Maximum number of projects to return if "Return All" is false. Minimum value is 1. |
| Filters | Collection of filters to apply when fetching projects: |
| - Include Archived (status) | Filter projects by their status: "All", "Closed Only", or "Open Only". |
Output
The node outputs an array of JSON objects representing projects retrieved from Redmine. Each object contains the project's details as provided by the Redmine API, such as project ID, name, description, status, and other metadata.
If the node encounters errors during execution and "Continue On Fail" is enabled, it outputs error messages in the json.error field paired with the corresponding input item index.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a Redmine instance via its REST API.
- Needs an API key credential for authentication.
- The Redmine base URL and API key must be configured in the node credentials.
Troubleshooting
Common issues:
- Incorrect or missing API key leading to authentication failures.
- Invalid Redmine URL causing connection errors.
- Requesting too many projects without enabling "Return All" may result in truncated data.
- Filtering with unsupported status values will not return expected results.
Error messages:
- Authentication errors typically indicate invalid API keys; verify credentials.
- Network errors suggest connectivity issues or incorrect URLs.
- If the node throws errors about limits or parameters, check that "Limit" is set to a positive integer and "Return All" is correctly configured.