Actions199
- Collections Actions
- Forms Actions
- Actions Capabilities Actions
- Activities Actions
- Attachments Actions
- Budgets Actions
- Categories Actions
- Custom Actions Actions
- Custom Options Actions
- Documents Actions
- File Links Actions
- View File Link
- Delete File Link
- Open File Link
- Download File Link
- List Project Storages
- Get Project Storage
- Open Project Storage
- Create Storage
- Get Storage
- Update Storage
- Delete Storage
- Get Storage Files
- Prepare Storage File Upload
- Create Storage Folder
- Create Storage Oauth Credentials
- Open Storage
- Create Work Package File Link
- List Work Package File Links
- Grids Actions
- Groups Actions
- Help Texts Actions
- Memberships Actions
- Query Filter Instance Schema Actions
- News Actions
- Notifications Actions
- O Auth 2 Actions
- Posts Actions
- Principals Actions
- Priorities Actions
- Query Columns Actions
- Query Filters Actions
- Query Operators Actions
- Query Sort Bys Actions
- Relations Actions
- Previewing Actions
- Revisions Actions
- Roles Actions
- Time Entries Actions
- Time Entry Activities Actions
- Types Actions
- User Preferences Actions
- Wiki Pages Actions
- Work Schedule Actions
- Meetings Actions
- Values Property Actions
- Projects Actions
- Queries Actions
- Users Actions
- Statuses Actions
- Versions Actions
- Work Packages Actions
- Get Project Work Package Collection
- Create Project Work Package
- List Work Package File Links
- Form Create Work Package In Project
- Project Available Assignees
- List Work Packages
- Create Work Package
- Form Create Work Package
- List Work Package Schemas
- View Work Package Schema
- Delete Work Package
- View Work Package
- Update Work Package
- List Work Package Activities
- Comment Work Package
- Work Package Available Assignees
- Available Projects For Work Package
- List Available Relation Candidates
- Available Watchers
- Create Work Package File Link
- Form Edit Work Package
- Revisions
- Reminders
- List Watchers
- Add Watcher
- Remove Watcher
- Views Actions
Overview
This node interacts with the OpenProject API to list users based on specified criteria. It is useful for retrieving user information from an OpenProject instance, such as when you want to automate user management, generate reports, or synchronize user data with other systems.
Typical use cases include:
- Fetching a paginated list of users filtered by status, group membership, or name.
- Sorting users by specific attributes like status.
- Selecting only certain user properties to optimize data transfer and processing.
For example, you might use this node to get all invited users in a particular group or to find users whose names or emails match a search string.
Properties
| Name | Meaning |
|---|---|
| Offset | Page number inside the requested collection. Determines which page of results to retrieve. |
| Page Size | Number of elements to display per page. Controls how many users are returned in one request. |
| Filters | JSON string specifying filter conditions. Supports filtering by user status (e.g., invited), group membership (by group name or ID), user name (first/last/email), and login. The format matches the OpenProject queries endpoint. |
| Sort By | JSON string specifying sort criteria. Defines how the results should be ordered, e.g., by status ascending. Matches the format used by the OpenProject queries endpoint. |
| Select | Comma-separated list of user properties to include in the response. For example, "total,elements/name,elements/self,self" selects total count and specific user fields. |
Output
The node outputs JSON data representing the list of users retrieved from OpenProject. The structure typically includes:
total: Total number of users matching the query.elements: An array of user objects, each containing the selected properties such as name and self-reference URLs.- Additional metadata depending on the
selectparameter.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the OpenProject API.
- Needs the base URL of the OpenProject instance configured in the node credentials.
- Depends on the OpenProject REST API being accessible and properly configured to accept the queries.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Malformed JSON in the Filters or Sort By properties can lead to request errors.
- Requesting too large a page size may result in timeouts or performance issues.
- Filtering or sorting by unsupported fields will cause the API to reject the request.
Error messages:
- Authentication errors usually indicate invalid or expired API tokens; verify and update credentials.
- JSON parsing errors suggest that the Filters or Sort By inputs are not valid JSON strings; ensure correct formatting.
- HTTP 400 or 422 errors often mean invalid query parameters; check filter and sort criteria against OpenProject API documentation.