Scoro

Overview

This node integrates with the Scoro API to perform various operations on different resources. Specifically, for the Time Entry resource and the Set Done operation, it allows users to mark a particular time entry as completed or "done" within Scoro. This is useful in scenarios where you track work hours or tasks and want to update the status of a time entry once the work is finished.

Practical examples include:

• Automatically marking a time entry as done after a task is completed.
• Updating time tracking records in bulk workflows.
• Synchronizing time entry statuses between Scoro and other project management tools.

Properties

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 a number).

Output

The node outputs JSON data representing the result of the "set done" operation on the selected time entry. This typically includes confirmation details such as the updated time entry's ID, status, timestamps, or any 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.
• Needs an API key credential configured in n8n with access rights to modify time entries.
• The base URL and company account ID must be set correctly in the credentials.
• The node uses internal methods to fetch lists of time entries for selection and to execute the "set done" operation via the Scoro API.

Troubleshooting

• Invalid Time Entry ID: If the entered ID is not numeric or does not exist, the node will throw an error. Ensure the ID is correct and numeric.
• Operation Not Supported: If the operation "setDone" is not recognized for the "timeEntry" resource, verify that the node version supports this operation.
• Authentication Errors: If API credentials are missing or invalid, the node will fail to connect. Check that the API key and base URL are correctly configured.
• Permission Issues: Insufficient permissions in Scoro may prevent updating time entries. Confirm the API user has write access.
• Network Issues: Connectivity problems can cause request failures. Verify network access to the Scoro API endpoint.

Links and References

• Scoro API Documentation
• n8n Documentation - Creating Nodes
• Scoro Time Tracking Features