Actions17
Overview
This node integrates with the HighLevel API to manage contacts and other resources. Specifically, the "Delete Contact" operation allows users to remove a contact from their HighLevel account by specifying the contact's unique identifier. This is useful in scenarios where you want to automate cleanup of outdated or irrelevant contact records, maintain data hygiene, or integrate contact deletion as part of a larger workflow (e.g., after unsubscribing a user or closing a deal).
Example use cases:
- Automatically deleting contacts who have unsubscribed from marketing communications.
- Removing test or duplicate contacts created during data imports.
- Cleaning up contacts after a certain period of inactivity.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to delete. This is required to specify which contact should be removed from the system. |
Output
The node outputs JSON data representing the response from the HighLevel API after attempting to delete the specified contact. Typically, this will include confirmation of deletion or relevant status information. The exact structure depends on the API response but generally confirms success or failure of the deletion request.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the HighLevel API via an OAuth2 authentication credential.
- The node uses the base URL
https://services.leadconnectorhq.comfor API requests. - The API version used is
"2021-07-28". - Proper permissions on the API key or OAuth token are necessary to perform contact deletions.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Contact ID will likely result in an error or no action.
- Insufficient API permissions can cause authorization errors.
- Network connectivity problems may prevent successful API calls.
Error messages:
- "Unauthorized" or "Forbidden": Check that the API credentials are valid and have the required scopes/permissions.
- "Contact not found": Verify that the Contact ID is correct and exists in your HighLevel account.
- Timeouts or network errors: Ensure stable internet connection and that the HighLevel API service is operational.
Resolving these typically involves verifying input parameters, checking API credentials, and ensuring network stability.
Links and References
- HighLevel API Documentation (for detailed API endpoints and authentication)
- n8n documentation on OAuth2 Credentials for setting up API authentication