OpenProject icon

OpenProject

Interact with OpenProject via API

Actions199

Overview

This node interacts with the OpenProject API to retrieve items of a custom field. Specifically, the "Get Custom Field Items" operation fetches the values associated with a particular custom field, optionally filtered by a parent item and limited by hierarchy depth. This is useful when you want to dynamically obtain the options or entries defined for a custom field in OpenProject, for example, to populate dropdowns, validate inputs, or synchronize data.

Practical examples:

  • Fetching all selectable options for a custom dropdown field to present them in another system.
  • Retrieving hierarchical custom field items up to a certain depth to analyze or report on nested structures.
  • Filtering custom field items by a parent identifier to get only relevant subsets.

Properties

Name Meaning
Id The unique identifier of the custom field whose items you want to retrieve.
Parent (Optional) The identifier of the parent hierarchy item to filter the custom field items.
Depth (Optional) The level of hierarchy depth to retrieve for the custom field items.

Output

The node outputs JSON data representing the list of custom field items retrieved from OpenProject. Each item corresponds to an entry within the specified custom field, potentially including hierarchical relationships if parent and depth are used.

If the custom field supports hierarchical data, the output will reflect this structure according to the requested depth.

No binary data output is indicated.

Dependencies

  • Requires an active connection to an OpenProject instance via its REST API.
  • Needs an API authentication token configured in the node credentials to authorize requests.
  • The base URL of the OpenProject server must be set in the credentials.

Troubleshooting

  • Invalid or missing custom field ID: Ensure the Id property is correctly set to an existing custom field's unique identifier.
  • Authentication errors: Verify that the API key or token provided in credentials is valid and has sufficient permissions.
  • Network or connectivity issues: Confirm that the OpenProject server URL is reachable from the n8n environment.
  • Incorrect parent ID or depth: If filtering by parent or setting depth returns no results, check that these values correspond to actual hierarchy items and valid depth levels.

Common error messages may include HTTP 401 Unauthorized (authentication failure), 404 Not Found (invalid resource or ID), or 400 Bad Request (invalid parameters). Resolving these typically involves verifying credentials, IDs, and parameter correctness.

Links and References

Discussion