Actions43
- Project Actions
- User Actions
- Work Package Actions
- Time Entry Actions
- Version Actions
- Type Actions
- Status Actions
- Priority Actions
- Category Actions
Overview
This node integrates with the OpenProject API to manage various resources such as projects, users, work packages, time entries, versions, types, statuses, priorities, and categories. Specifically, for the User - Get operation, it retrieves detailed information about a single user by their unique ID.
Common scenarios where this node is beneficial include:
- Fetching user details to display or use in workflows.
- Validating user existence before performing other operations.
- Integrating OpenProject user data into other systems or reports.
For example, you might use this node to get a user's profile information by providing their User ID, then use that data downstream in your workflow to assign tasks or send notifications.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose details you want to retrieve. This is a required string input. |
Output
The node outputs a JSON object representing the user resource as returned by the OpenProject API. This typically includes fields such as user ID, name, email, login, status, and other user-related metadata.
The output structure corresponds directly to the OpenProject user resource schema and can be used in subsequent nodes for further processing.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the OpenProject API.
- Needs an API key credential configured in n8n for authentication.
- The base URL of the OpenProject instance must be provided in the credentials.
- Uses HTTP Basic Authentication with the API key encoded in Base64.
Troubleshooting
Error: "The resource 'user' is not supported!"
This indicates an invalid resource parameter; ensure the resource is set to "user".Error: "OpenProject error response: ..."
This usually means the API responded with an error message, such as "User not found" or "Unauthorized". Check that the User ID is correct and that the API key has sufficient permissions.Network or authentication errors
Verify that the base URL and API key are correctly configured in the node credentials.Empty or unexpected output
Confirm that the User ID exists in the OpenProject system and that the API endpoint is reachable.