Actions26
Overview
This node integrates with the GoHighLevel V2 API, allowing users to interact with various resources such as Contacts, Companies, Opportunities, and Custom Fields. Specifically, for the Contact resource with the Get Many operation, it retrieves multiple contact records from the GoHighLevel system.
Common scenarios where this node is beneficial include:
- Exporting a list of contacts for marketing or CRM purposes.
- Synchronizing contacts between GoHighLevel and other systems.
- Filtering contacts based on creation or update timestamps to process only recent changes.
For example, a user might configure the node to fetch all contacts created after a certain date to send them a welcome email campaign.
Properties
| Name | Meaning |
|---|---|
| Limit | Maximum number of contact results to return when not returning all. Minimum value is 1. Default is 50. |
| Return All | Boolean flag indicating whether to return all matching contacts or limit the results to the specified number. |
| Filters | Collection of optional filters to narrow down the contacts returned: |
| Created After | Only return contacts created after this date/time. |
| Created Before | Only return contacts created before this date/time. |
| Updated After | Only return contacts updated after this date/time. |
| Updated Before | Only return contacts updated before this date/time. |
Output
The node outputs an array of JSON objects, each representing a contact record retrieved from GoHighLevel. Each item in the output corresponds to one contact with its associated fields as provided by the API.
If multiple contacts are returned, the output will be an array of these JSON objects. There is no binary data output for this operation.
Dependencies
- Requires an active connection to the GoHighLevel V2 API via OAuth2 authentication.
- The node expects the user to have configured the necessary API credentials (an API key or OAuth2 token) within n8n.
- No additional external dependencies beyond the GoHighLevel API and n8n's standard environment.
Troubleshooting
Common issues:
- Authentication failures due to invalid or expired API tokens.
- Exceeding API rate limits imposed by GoHighLevel.
- Incorrect filter date formats causing the API to reject requests.
- Requesting too many records without enabling "Return All" may result in truncated data.
Error messages:
"The resource "contact" is not known!"— This indicates an unsupported resource was selected; ensure "Contact" is chosen.- API errors related to authentication or permissions typically require checking the configured credentials.
- If the node returns partial data or errors, verify that the filters and limits are set correctly and that the GoHighLevel account has sufficient access rights.