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 perform various operations on different resources such as projects, users, work packages, time entries, versions, types, statuses, priorities, and categories. Specifically, for the Category resource with the Get operation, the node retrieves detailed information about a single category by its ID.
Common scenarios where this node is beneficial include:
- Fetching metadata or details of a specific category in an OpenProject instance.
- Automating workflows that require category data retrieval for reporting or processing.
- Integrating OpenProject category data into other systems or dashboards.
Example use case:
- You want to get the details of a category with ID
123to display its name and description in a custom dashboard or to use it in conditional logic within your workflow.
Properties
| Name | Meaning |
|---|---|
| Category ID | The unique identifier of the category to retrieve. This is a required string input. |
Output
The node outputs an array of JSON objects, each representing the response from the OpenProject API for the requested category. The structure corresponds directly to the OpenProject category resource representation, typically including fields like:
id: The category's unique identifier.name: The name of the category.- Other metadata fields provided by the OpenProject API for categories.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to an OpenProject instance via its REST API.
- Needs an API key credential configured in n8n for authentication.
- The node uses HTTP Basic Authentication with the API key encoded in base64.
- The base URL of the OpenProject instance and the API key must be set in the node credentials.
Troubleshooting
Common issues:
- Invalid or missing Category ID will cause the API call to fail.
- Incorrect API key or base URL configuration will result in authentication errors.
- Network connectivity issues to the OpenProject server can cause request failures.
Error messages:
OpenProject error response: <message>indicates the API returned an error message, often due to invalid parameters or permissions.- Generic errors may indicate network problems or misconfiguration.
Resolutions:
- Verify the Category ID is correct and exists in the OpenProject instance.
- Check that the API key and base URL are correctly configured in the node credentials.
- Ensure the OpenProject server is reachable from the n8n environment.
- Enable "Continue On Fail" if you want the workflow to proceed despite individual item errors.