OpenProject icon

OpenProject

Consume OpenProject API

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 Type resource with the Update operation, it allows updating an existing type entity in OpenProject by specifying its ID and the fields to update.

Common scenarios where this node is beneficial include automating project management workflows, synchronizing type definitions across systems, or programmatically maintaining type metadata within OpenProject.

For example, you might use this node to update the name or other attributes of a type after receiving input from another system or user interaction, ensuring your OpenProject instance stays current without manual edits.

Properties

Name Meaning
Type ID The ID of the type to update (string).

Note: The provided properties JSON only includes the typeId property required for identifying which type to update. Additional fields to update would typically be specified in the node UI but are not detailed here.

Output

The node outputs an array of JSON objects representing the response from the OpenProject API after performing the update operation on the Type resource. Each output item contains the updated type data as returned by the API.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to an OpenProject instance via its REST API.
  • Needs an API key credential configured in n8n for authentication.
  • Uses HTTP Basic Authentication with the API key encoded in base64.
  • Depends on the axios library for making HTTP requests.

Troubleshooting

  • Common issues:

    • Invalid or missing Type ID will cause the API call to fail.
    • Incorrect API key or base URL configuration will result in authentication errors.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Errors returned by OpenProject API are captured and presented with their message, e.g., "OpenProject error response: <message>".
    • If the API returns no specific message, the node throws a generic error with the underlying message.
  • Resolution tips:

    • Verify that the Type ID exists and is correct.
    • Check that the API key and base URL credentials are properly set up in n8n.
    • Ensure network access to the OpenProject server.
    • Use the "Continue On Fail" option in the node settings to handle errors gracefully during batch operations.

Links and References

Discussion