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 Task resource with the Delete operation, it deletes a task identified by its unique Task ID. This is useful in scenarios where you need to programmatically remove tasks from your Scoro project management system, such as cleaning up completed or obsolete tasks automatically.
Practical examples include:
- Automatically deleting tasks that are marked as canceled or no longer relevant.
- Integrating with other systems to sync task deletions.
- Managing task lifecycle within automated workflows.
Properties
| Name | Meaning |
|---|---|
| Task ID | The ID of the task to delete. |
Output
The output JSON typically contains the response from the Scoro API after attempting to delete the specified task. This usually includes confirmation of deletion or an error message if the deletion failed. The node does not output binary data.
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 API.
- The node depends on proper authentication credentials to authorize requests.
Troubleshooting
- Common issues:
- Invalid or missing Task ID will cause the operation to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent communication with the Scoro API.
- Error messages:
"Operation 'delete' for resource 'task' is not supported."β indicates a misconfiguration or unsupported operation/resource combination.- API errors returned from Scoro (e.g., "Task not found" or "Unauthorized") should be checked and resolved by verifying input parameters and credentials.
Links and References
- Scoro API Documentation (for detailed API endpoints and request/response formats)