Actions17
Overview
This node integrates with the HighLevel API to manage various resources such as Contacts, Opportunities, Tasks, and Calendars. Specifically, for the Opportunity - Delete operation, it allows users to delete an existing opportunity by specifying its unique identifier. This is useful in scenarios where opportunities are no longer relevant or were created in error and need to be removed from the system.
Practical examples include:
- Automatically cleaning up outdated or lost sales opportunities.
- Removing test or duplicate opportunities during data synchronization.
- Managing pipeline hygiene by deleting irrelevant opportunities programmatically.
Properties
| Name | Meaning |
|---|---|
| Opportunity ID | The unique identifier of the opportunity to delete. This is a required string input. |
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 active connection to the HighLevel API via an OAuth2-based authentication credential.
- The node uses the base URL
https://services.leadconnectorhq.comand expects API version2021-07-28. - Proper permissions to delete opportunities must be granted to the authenticated user or API key.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Opportunity ID will likely cause the API to return an error indicating the resource was not found.
- Insufficient permissions or expired authentication tokens can lead to authorization errors.
- Network connectivity problems may prevent the node from reaching the HighLevel API endpoint.
Error messages and resolutions:
- "Not Found" or similar: Verify that the Opportunity ID is correct and exists in the system.
- "Unauthorized" or "Forbidden": Check that the API credentials are valid and have the necessary permissions.
- Timeouts or network errors: Ensure stable internet connection and that the HighLevel service is operational.
Links and References
- HighLevel API Documentation (for detailed API endpoints and responses)
- n8n documentation on OAuth2 Credentials for setting up authentication with external services