Project → Update
AI-generatedOverview
This node integrates with the Clockify API to update project details within a specified workspace. It allows users to modify various attributes of an existing project, such as its name, color, billing status, archival state, visibility (public or not), associated client, and notes.
Common scenarios where this node is beneficial include:
- Automating project management workflows by updating project information based on external triggers.
- Synchronizing project data from other systems into Clockify.
- Bulk updating multiple projects' properties programmatically without manual intervention.
For example, you could use this node to automatically archive projects that are completed or change the billing status of projects based on contract updates.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | Select or specify the workspace in which the project exists. This is required to scope the update operation correctly. |
| Project Name or ID | Select or specify the project to update within the chosen workspace. |
| Update Fields | A collection of fields to update on the project. These include: - Archived: Boolean indicating if the project is archived. - Billable: Boolean indicating if the project is billable. - Client Name or ID: The client associated with the project. - Color: Hexadecimal RGB color code for the project. - Is Public: Boolean indicating if the project is public. - Name: The project's name (2-250 characters). - Note: Additional notes about the project. |
Output
The node outputs JSON data representing the updated project object returned by the Clockify API after the update operation. This includes all project details reflecting the changes made.
If multiple input items are processed, the output will be an array of updated project objects corresponding to each input.
The node does not output binary data.
Dependencies
- Requires an active connection to the Clockify API via an API key credential configured in n8n.
- The node depends on the Clockify REST API being accessible and the provided workspace and project IDs being valid.
- The user must have appropriate permissions in Clockify to update projects within the specified workspace.
Troubleshooting
- Invalid Workspace or Project ID: If the workspace or project ID is incorrect or missing, the API call will fail. Ensure these IDs are correct and exist in your Clockify account.
- Insufficient Permissions: Lack of proper permissions to update projects may result in authorization errors. Verify that the API key has sufficient rights.
- Invalid Field Values: Providing invalid values (e.g., malformed color codes, too short/long project names) can cause validation errors. Follow the field requirements strictly.
- API Rate Limits: Frequent calls might hit Clockify's rate limits, causing temporary failures. Implement retry logic or reduce request frequency.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON under an
errorproperty.