Actions60
- User Actions
- Teams Actions
- Custom Fields Actions
- Tickets Actions
- Deals Actions
- Webhooks Actions
- Contacts Actions
- Companies Actions
- Bussiness Types Actions
- Tags Actions
- Deal Phases Actions
- Invoices Actions
- Subscriptions Actions
- Products Actions
- Projects Actions
- Tasks Actions
- Files Actions
Overview
The "Delete Task" operation in the Teamleader node allows users to delete a specific task by its ID using the Teamleader API. This operation is useful for automating task management workflows where tasks need to be programmatically removed, such as cleaning up completed or obsolete tasks, or integrating with other systems that trigger task deletions.
Practical examples:
- Automatically deleting tasks that are marked as duplicates or no longer relevant.
- Removing tasks from Teamleader when corresponding records are deleted in another system.
- Cleaning up tasks after project completion via automation.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the task to delete. This is a required string input. |
Output
The output of the delete operation returns a JSON array containing the response data from the Teamleader API. Typically, this will include confirmation of the deletion or any relevant metadata returned by the API. If no data is returned but the request was successful, a message indicating this is provided.
The structure is generally:
[
{
"message": "No data returned but request was successful"
}
]
or the actual data object returned by the API if any.
No binary data output is involved in this operation.
Dependencies
- Requires an active OAuth2 API credential configured for Teamleader with appropriate permissions to delete tasks.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euwith the operation path set to"tasks.delete".
Troubleshooting
Common issues:
- Providing an invalid or non-existent task ID will likely result in an error from the API.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity issues can prevent the API call from succeeding.
Error messages:
"No data got returned": Indicates the API response did not contain expected data; verify the task ID and API status.- API errors related to authorization or permissions: Ensure the OAuth2 token has the necessary scopes.
- Request failures due to invalid parameters: Confirm the task ID is correctly specified and formatted.
To resolve these, verify the task ID exists, check API credentials, and ensure network access to the Teamleader API.
Links and References
- Teamleader API Documentation
- n8n OAuth2 Credential Setup (generic reference for configuring OAuth2 credentials)