OpenProjectInstall

Overview

This node interacts with the OpenProject API to update an existing time entry resource. It allows users to modify details of a specific time entry such as the number of hours worked, the associated activity, comments, and the date the time was spent on.

Common scenarios where this node is beneficial include:

• Adjusting logged work hours after initial entry.
• Adding or updating comments related to a time entry for better context.
• Correcting or specifying the date when the work was performed.
• Changing the activity type linked to the time entry.

For example, a project manager might use this node to update a developer's time entry to reflect additional hours worked or to add notes about the task completed.

Properties

Output

The node outputs a JSON object representing the updated time entry as returned by the OpenProject API. This includes all standard fields of a time entry resource, reflecting the new values after the update operation.

If the API returns any error, the node will output an error message in the JSON under an error key if "Continue On Fail" is enabled; otherwise, it throws an error.

The node does not output binary data.

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 PATCH method to update the resource via the OpenProject REST API.

Troubleshooting

• Invalid Time Entry ID: If the specified time entry ID does not exist, the API will return an error indicating the resource was not found. Verify the ID is correct.
• Incorrect Hours Format: The hours property must be in ISO 8601 duration format (e.g., PT1H30M). Using an invalid format may cause the API to reject the request.
• Missing Required Fields: The timeEntryId, hours, and activityId are required. Omitting these will result in errors.
• API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to update time entries.
• Date Format Issues: The optional spentOn field should be a valid datetime string. Invalid formats may cause errors.
• Network or API Downtime: Network issues or OpenProject server downtime can cause request failures.

Error messages from the API are surfaced clearly, e.g., "OpenProject error response: <message>", helping identify the root cause.

Links and References

• OpenProject API Documentation - Time Entries
• ISO 8601 Duration Format