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
This node integrates with the Scoro API to perform various operations on different resources within a Scoro account. Specifically, for the Time Entry resource and the Set Done operation, it marks a specified time entry as completed or "done". This is useful in scenarios where you want to programmatically update the status of time entries after work has been finished, enabling automated workflow management and accurate time tracking.
Practical examples include:
- Automatically marking time entries as done once a related task or project phase is completed.
- Syncing time entry statuses from external systems into Scoro.
- Batch updating multiple time entries' statuses based on business rules.
Properties
| Name | Meaning |
|---|---|
| Time Entry | The specific time entry to mark as done. Can be selected from a searchable list or provided by its numeric ID. |
The "Time Entry" property supports two modes:
- From List: Select a time entry from a searchable list fetched dynamically.
- By ID: Enter the numeric ID of the time entry directly (must be numeric).
Output
The node outputs JSON data representing the result of the "Set Done" operation on the specified time entry. This typically includes confirmation details such as the updated time entry's ID, status, timestamps, and any other relevant metadata returned by the Scoro API.
If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the time entry, but this is not applicable for this operation.
Dependencies
- Requires an active connection to the Scoro API via an API key credential.
- Needs configuration of the base URL and company account ID for the Scoro instance.
- The node depends on internal methods to fetch lists of time entries for selection and to route the operation to the correct API endpoint.
Troubleshooting
Common Issues:
- Providing an invalid or non-numeric Time Entry ID will cause validation errors.
- If the specified time entry does not exist or is already marked done, the API may return an error.
- Network or authentication issues with the Scoro API can prevent successful execution.
Error Messages:
"Operation 'setDone' for resource 'timeEntry' is not supported."β indicates a misconfiguration or unsupported operation; verify the resource and operation names.- Validation error
"Time Entry ID must be numeric"β ensure the ID input contains only digits. - API authentication errors β check that the API key and base URL are correctly configured.
Links and References
- Scoro API Documentation β official API reference for understanding endpoints and payloads.
- n8n Documentation on Creating Custom Nodes β for extending or troubleshooting custom nodes.