Actions26
- Milestone Actions
- Project Actions
- Project Admin Actions
- Task Actions
- Time Log Actions
Overview
The node integrates with the Cloodo Worksuite API to retrieve data related to various project management resources. Specifically, for the Time Log resource with the Get operation, it fetches detailed information about a specific time log entry identified by its ID. This is useful in scenarios where users want to track or analyze time entries logged against projects or tasks, such as generating reports on work hours or auditing time tracking.
Practical examples:
- Fetching a single time log entry to review the duration and details of work done.
- Integrating time log data into dashboards or external reporting tools.
- Validating or updating time logs based on retrieved information.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the time log entry to retrieve. Users must provide this ID to specify which time log record they want to get. |
Output
The node outputs JSON data representing the requested time log entry. This JSON typically includes fields such as the time log's ID, associated user, start and end times, duration, description, and any other metadata provided by the Cloodo Worksuite API for a time log.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the time log, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an active connection to the Cloodo Worksuite API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4. - Proper network access to the API endpoint is necessary.
Troubleshooting
- Missing or invalid ID: If the ID property is empty or incorrect, the API will likely return an error indicating that the time log was not found. Ensure the ID is correct and corresponds to an existing time log.
- Authentication errors: If the API key or token is missing, expired, or invalid, the node will fail to authenticate. Verify that the API credentials are correctly set up in n8n.
- Network issues: Connectivity problems to the API endpoint can cause request failures. Check network settings and firewall rules.
- API rate limits: Excessive requests might trigger rate limiting; handle such errors by implementing retries or backoff strategies.
Links and References
- Cloodo Worksuite API Documentation (Assumed URL based on baseURL, verify actual docs)
- n8n documentation on Creating Custom Nodes