Actions46
- Calendar Actions
- ClientProfile Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Status Actions
- Task Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
The node integrates with the Scoro API to update an existing Time Entry resource. It allows users to modify details of a specific time entry by specifying its ID and providing a JSON object with the updated data. This is useful in scenarios where time tracking data needs correction or adjustment after initial entry, such as updating hours worked, descriptions, or associated projects.
Practical examples:
- Correcting the duration or notes of a logged time entry.
- Changing the project or task linked to a time entry.
- Updating billing or status information related to a time entry.
Properties
| Name | Meaning |
|---|---|
| TimeEntry | The identifier of the time entry to update. Can be selected from a searchable list or entered manually as a numeric ID. |
| Request | A JSON object representing the nested request body containing the fields and values to update for the specified time entry. |
Output
The node outputs JSON data representing the updated time entry as returned by the Scoro API. This typically includes all fields of the time entry after modification, such as IDs, timestamps, durations, descriptions, and any other relevant metadata.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Scoro API.
- Needs configuration of the base URL and company account ID within the credentials.
- Uses internal methods to fetch lists of time entries for selection (searchable list mode).
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.
- Missing or incorrect API credentials will lead to authentication failures.
- Attempting to update a non-existent time entry will cause API errors.
Error messages and resolutions:
"Time Entry ID must be numeric": Ensure the ID entered contains only digits."Operation 'update' for resource 'timeEntry' is not supported.": Verify that the operation and resource names are correctly set.- Authentication errors: Check that the API key and base URL are correctly configured in credentials.
- JSON parse errors on the Request field: Validate the JSON syntax before input.
Links and References
- Scoro API Documentation
- n8n documentation on Creating Custom Nodes