Actions26
Overview
This node integrates with the GoHighLevel V2 API, allowing users to perform various operations on different resources such as Contacts, Companies, Opportunities, and Custom Fields. Specifically, for the Contact resource with the Get operation, it retrieves detailed information about a specific contact by its unique ID.
Common scenarios include:
- Fetching contact details to enrich CRM data.
- Retrieving contact information before performing updates or other actions.
- Integrating contact data into workflows for marketing automation or customer support.
Example: Given a Contact ID, the node fetches all available data about that contact from GoHighLevel, which can then be used downstream in the workflow for personalized messaging or reporting.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the contact's details as returned by the GoHighLevel API. The structure typically includes fields such as contact name, email, phone number, custom fields, tags, and other metadata associated with the contact.
If multiple contacts were retrieved (not applicable here since Get uses a single ID), the output would be an array of JSON objects. For this operation, the output is a single JSON object per input item.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the GoHighLevel V2 API via OAuth2 authentication.
- The user must configure the node with valid API credentials (an API key or OAuth2 token) to authenticate requests.
- The node depends on internal utility modules and resource handlers bundled within the node package to manage API calls.
Troubleshooting
Common issues:
- Invalid or missing Contact ID: The node requires a valid Contact ID; providing an empty or incorrect ID will cause errors.
- Authentication failures: If the API credentials are invalid or expired, the node will fail to connect.
- Network or API downtime: Temporary connectivity issues may cause request failures.
Error messages:
"The resource "contact" is not known!"— indicates an unsupported resource was selected; ensure "Contact" is chosen.- API error messages returned from GoHighLevel will be passed through; check the message for details like "Contact not found" or permission issues.
Resolution tips:
- Verify the Contact ID exists in your GoHighLevel account.
- Re-authenticate or update API credentials if authorization errors occur.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.
Links and References
- GoHighLevel API Documentation
- n8n Documentation on Creating Custom Nodes