Actions15
Overview
This node integrates with the Redmine API to retrieve user data. Specifically, the "User - Get Many" operation fetches multiple user records from a Redmine instance. It is useful in scenarios where you need to list users for reporting, synchronization, or administrative tasks within workflows.
For example, you might use this node to:
- Retrieve all active users in a project management system.
- Filter users by group or status to generate targeted notifications.
- Limit the number of users fetched to optimize performance in large organizations.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching user results or only up to a specified limit. |
| Limit | The maximum number of user records to return when "Return All" is false (minimum 1). |
| Filters | Collection of filters to narrow down the user list: |
| Group ID | Filter users by their associated group identifier. |
| Name | Filter users by their name (partial or full match depending on API behavior). |
| Status | Filter users by status with options: Active, Registered, or Locked. |
Output
The node outputs an array of user objects in the json field of each item. Each object represents a user record retrieved from Redmine and includes details such as user ID, name, status, group membership, and other relevant user attributes as provided by the Redmine API.
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 configured in n8n for authentication.
- The Redmine URL and API key must be set in the node credentials before execution.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Incorrect Redmine URL or network issues can prevent connecting to the API.
- Using filters with invalid values may result in empty responses or errors.
- Exceeding API rate limits or permissions restrictions can cause errors.
Error messages:
- Authentication errors typically indicate problems with the API key or credentials setup.
- "Not Found" or similar errors may mean the resource or filter criteria do not exist.
- Timeout or network errors suggest connectivity problems to the Redmine server.
Resolutions:
- Verify API key validity and permissions.
- Confirm the Redmine URL is correct and accessible.
- Adjust filters to valid values supported by your Redmine instance.
- Check network connectivity and firewall settings.