Actions16
Overview
This node allows you to delete a Contact from the HighLevel platform by specifying the Contact ID. It is useful in automation scenarios where you need to remove contacts as part of a workflow, such as cleaning up outdated records or responding to user requests for data deletion.
Example use cases:
- Automatically deleting contacts who have unsubscribed.
- Removing test or duplicate contacts during data maintenance.
- Complying with GDPR or other privacy regulations by deleting user data upon request.
Properties
| Name | Type | Meaning |
|---|---|---|
| Contact ID | String | The unique identifier of the contact you want to delete from HighLevel. |
Output
The output will be a JSON object reflecting the result of the delete operation. Typically, this may include:
- A success confirmation (e.g.,
{ "success": true }) - Or an error message if the contact could not be deleted.
Note: The exact structure depends on the HighLevel API's response for a delete operation.
Dependencies
- External Service: Requires access to the HighLevel API.
- API Key: You must provide valid HighLevel API credentials (
highLevelApi) in n8n. - n8n Configuration: Ensure the credential is set up and assigned to this node.
Troubleshooting
Common Issues:
- Invalid Contact ID: If the provided Contact ID does not exist, the API will likely return an error indicating that the contact was not found.
- Authentication Errors: If the API key is missing or invalid, you may receive authentication/authorization errors.
- Network Issues: Connectivity problems can cause timeouts or failed requests.
Common Error Messages & Resolutions:
"Contact not found": Double-check the Contact ID for typos or ensure the contact exists."Unauthorized"or"Invalid API Key": Verify your HighLevel API credentials in n8n."Request failed with status code 4xx/5xx": Check the API documentation for specific error codes and ensure all required fields are correctly filled.