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
This node interacts with the Scoro API to perform various operations on different resources. Specifically, for the Time Entry - Delete operation, it deletes a time entry identified by its ID from the Scoro system. This is useful in scenarios where you need to programmatically remove incorrect or obsolete time tracking records from your project management or billing workflows.
Practical examples include:
- Automatically deleting time entries that were created by mistake.
- Cleaning up time entries after a project phase is completed.
- Integrating with other systems to synchronize and maintain accurate 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.
The node does not output binary data.
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 the Scoro REST API endpoints to perform operations.
Troubleshooting
Common issues:
- Invalid or missing TimeEntry ID will cause the operation to fail.
- Incorrect or expired API credentials will prevent authentication.
- Network connectivity problems can cause request failures.
Error messages:
"Operation 'delete' for resource 'timeEntry' is not supported."— This indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.- API errors returned from Scoro (e.g., 404 Not Found if the time entry ID does not exist) should be checked and handled accordingly.
Resolutions:
- Verify the TimeEntry ID is correct and exists in Scoro.
- Confirm API credentials are valid and have necessary permissions.
- Check network access and proxy settings if applicable.
Links and References
- Scoro API Documentation (for detailed API endpoint info)
- n8n documentation on creating custom nodes