GoHighLevel V2 icon

GoHighLevel V2

Consume GoHighLevel V2 API

Overview

This node integrates with the GoHighLevel V2 API, allowing users to manage various resources such as Contacts, Companies, Opportunities, and Custom Fields within their GoHighLevel account. Specifically, for the Contact resource with the Add Tag operation, the node enables adding one or more tags to a contact record. This is useful for organizing contacts, segmenting audiences, or triggering workflows based on tag assignments.

Practical examples include:

  • Automatically tagging new leads imported from other systems.
  • Adding tags to contacts based on interactions or status changes.
  • Segmenting contacts for targeted marketing campaigns.

Properties

Name Meaning
Tags A string representing one or multiple tags to add to the contact. These tags help categorize or label the contact within GoHighLevel.

Output

The node outputs JSON data representing the result of the tag addition operation on the contact. The exact structure depends on the GoHighLevel API response but typically includes confirmation of the updated contact details or the applied tags.

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 in the source code.

Dependencies

  • Requires an active connection to the GoHighLevel V2 API.
  • Needs an API authentication token configured via OAuth2 credentials in n8n.
  • The node uses the GoHighLevelManager utility internally to handle API requests.

Troubleshooting

  • Unknown Resource Error: If the resource parameter is set incorrectly, the node throws an error stating the resource is not known. Ensure "contact" is selected when performing contact-related operations.
  • API Authentication Failures: Missing or invalid API credentials will cause authentication errors. Verify that the OAuth2 credential is correctly set up and authorized.
  • Tag Format Issues: Since tags are provided as strings, improper formatting (e.g., empty strings) may lead to no tags being added or API errors. Provide valid, non-empty tag names.
  • Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON for failed items.

Links and References

Discussion