Actions79
- Lead Status Actions
- Pipeline Actions
- Template Actions
- Lead Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Email Template Actions
- Task Actions
- User Actions
- Custom Field Actions
Overview
This node integrates with the Close.com CRM platform, allowing users to perform various operations on different CRM resources. Specifically, for the Task resource with the Delete operation, it enables users to delete a task by specifying its unique Task ID. This is useful in scenarios where tasks are no longer relevant or were created in error and need to be removed from the CRM system.
Practical examples include:
- Automatically deleting completed or obsolete tasks as part of a workflow cleanup.
- Removing tasks that were duplicated or incorrectly assigned.
- Managing task lifecycle programmatically within broader automation processes.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to delete. This is required to specify which task should be deleted. |
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 task. If an error occurs, the output may contain an error message describing the issue.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Close.com CRM API.
- The node depends on network access to the Close.com API endpoints.
- Proper configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Task ID will cause the operation to fail.
- Missing or incorrect API authentication credentials will prevent the node from connecting to Close.com.
- Network connectivity problems can cause timeouts or request failures.
Error messages:
"The resource "task" is not known!"— indicates an unsupported resource was selected; ensure "Task" is chosen.- Errors related to authorization typically indicate invalid or missing API keys; verify credential setup.
- If the task ID does not exist, the API may return a not found error; double-check the Task ID value.
To resolve errors, verify the Task ID correctness, ensure valid API credentials, and check network connectivity.