Actions17
Overview
This node integrates with the HighLevel API to manage tasks associated with contacts. Specifically, the "Delete Task" operation allows users to remove a task linked to a particular contact by specifying the contact and task identifiers. This is useful in scenarios where tasks are no longer relevant or were created in error, helping keep task lists clean and up-to-date.
Practical examples include:
- Automatically deleting completed or canceled tasks related to a contact.
- Cleaning up test or duplicate tasks during data synchronization workflows.
Properties
| Name | Meaning |
|---|---|
| Contact Email or ID | Select or specify the contact (by email or ID) to which the task belongs. Options are loaded dynamically. |
| Task ID | The unique identifier of the task to delete. Must be provided as a string. |
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 if it failed. The exact structure depends on the HighLevel API response but generally includes status information.
No binary data output is involved in this operation.
Dependencies
- Requires an authenticated connection to the HighLevel API using OAuth2 credentials.
- The node uses the base URL
https://services.leadconnectorhq.comfor API requests. - Proper permissions on the API key or OAuth token are necessary to delete tasks.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Contact ID or Task ID will cause the deletion to fail.
- Insufficient API permissions can lead to authorization errors.
- Network connectivity problems may prevent the API call from succeeding.
Error messages:
- "Task not found" — Verify that the Task ID is correct and belongs to the specified contact.
- "Unauthorized" or "Forbidden" — Check that the API credentials have the required permissions.
- "Invalid input" — Ensure all required fields are correctly filled and formatted.
Resolving these typically involves verifying input values, checking API credentials, and ensuring network access.
Links and References
- HighLevel API Documentation
- n8n Expressions Documentation (for dynamic property values)