Actions26
Overview
This node integrates with the GoHighLevel V2 API to manage various resources such as contacts, companies, and opportunities. Specifically, for the Company resource with the Remove Tag operation, it allows users to remove one or more tags from a company record in GoHighLevel. This is useful for keeping company data organized by dynamically updating tags based on changing business contexts or workflows.
Practical examples include:
- Automatically removing outdated or irrelevant tags from companies after certain events.
- Cleaning up tags when a company moves through different sales stages.
- Managing marketing segments by adjusting tags programmatically.
Properties
| Name | Meaning |
|---|---|
| Tags | A comma-separated list of tags to remove from the selected company. |
Output
The node outputs JSON data representing the result of the tag removal operation on the company. The exact structure depends on the GoHighLevel API response but typically includes confirmation of the updated company data or status of the tag removal.
If multiple input items are processed, the output will be an array of JSON objects corresponding to each item’s result.
No binary data output is indicated.
Dependencies
- Requires an active connection to the GoHighLevel V2 API.
- Needs an API authentication token configured via OAuth2 credentials within n8n.
- The node relies on internal helper functions (
handleCompanyOperations) to perform the actual API calls.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing tags that do not exist or are not associated with the company may result in no changes or errors.
- Incorrect resource or operation parameters will throw errors indicating unknown resources or unsupported operations.
Error messages:
"The resource \"company\" is not known!"— indicates the resource parameter was invalid or not handled.- API errors returned from GoHighLevel (e.g., permission denied, invalid tags) will be surfaced in the node’s error output if "Continue On Fail" is enabled.
To resolve errors:
- Verify API credentials and permissions.
- Ensure tags exist and are correctly formatted as comma-separated strings.
- Confirm the resource and operation parameters match supported values.