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 interacts with the Scoro API to perform various operations on different resources. Specifically, for the Time Entry resource with the Delete operation, it deletes a specified time entry from the Scoro system. This is useful in scenarios where you need to programmatically remove incorrect or obsolete time tracking records.
Practical examples include:
- Automatically deleting time entries that were created by mistake.
- Cleaning up time entries after a project phase ends.
- Integrating with other systems to synchronize and manage time tracking data.
Properties
| Name | Meaning |
|---|---|
| TimeEntry ID | The unique identifier of the time entry to delete |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide details about the deleted time entry. The exact structure depends on the Scoro API response but generally includes status information.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential to authenticate with the Scoro API.
- Needs the base URL and company account ID configured in the credentials.
- The node uses HTTP requests to communicate with the Scoro REST API.
Troubleshooting
Common issues:
- Invalid or missing TimeEntry ID: The node requires a valid ID; otherwise, the API will return an error.
- Authentication failures: Ensure the API key and other credential details are correct.
- Network or connectivity problems can cause request failures.
Error messages:
"Operation 'delete' for resource 'timeEntry' is not supported."β This indicates a misconfiguration or unsupported operation/resource combination.- API errors returned from Scoro (e.g., 404 Not Found if the time entry does not exist) should be checked and handled accordingly.
Links and References
- Scoro API Documentation (for detailed API endpoints and responses)
- n8n documentation on creating custom nodes