Actions50
- Status Actions
- Task Actions
- Calendar Actions
- ClientProfile Actions
- Comment Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
The node integrates with the Scoro API to perform operations on various resources, including Time Entries. Specifically, the Update operation for the Time Entry resource allows users to modify an existing time entry in their Scoro account by specifying its ID and providing updated data in JSON format.
This node is beneficial in scenarios where you need to automate time tracking updates, such as correcting logged hours, changing descriptions, or adjusting associated projects/tasks programmatically within workflows. For example, after receiving updated time data from another system, you can use this node to synchronize those changes into Scoro automatically.
Properties
| Name | Meaning |
|---|---|
| TimeEntry | The identifier of the time entry to update. You can select it either from a searchable list of existing time entries or enter the numeric ID directly. |
| Request | A JSON object representing the fields and values to update on the specified time entry. This should be a valid JSON string describing the nested request body sent to the API. |
Output
The node outputs the response from the Scoro API after attempting to update the time entry. The json output field contains the updated time entry data as returned by the API, reflecting the new state after the update.
If the API supports binary data for this resource (not indicated here), it would be included accordingly, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an active connection to the Scoro API.
- Needs credentials containing:
- Base URL of the Scoro instance.
- Company account ID.
- API key for authentication.
- These credentials must be configured in n8n before using the node.
Troubleshooting
Common issues:
- Providing an invalid or non-numeric Time Entry ID will cause validation errors.
- Malformed JSON in the "Request" property will result in parsing errors before sending the request.
- Missing or incorrect API credentials will lead to authentication failures.
- Attempting to update a non-existent time entry will cause the API to return an error.
Error messages:
"Operation 'update' for resource 'timeEntry' is not supported."— This indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.- Validation error
"Time Entry ID must be numeric"— Ensure the ID entered matches the required numeric format. - JSON parse errors on the "Request" input — Verify that the JSON is well-formed.
- API authentication errors — Check that the API key and other credentials are correctly set up.
Links and References
- Scoro API Documentation — Official API docs for reference on available fields and update payload structure.
- n8n Documentation — For general guidance on using credentials and JSON input in nodes.