GoHighLevel Simple

Integração simples com GoHighLevel API usando API Key

Actions6

Overview

This node integrates with the GoHighLevel API to manage contacts, opportunities, and locations. Specifically for the Contact - Get All operation, it retrieves a list of contacts from the GoHighLevel platform. This is useful when you want to fetch multiple contact records in bulk, for example, to synchronize contacts with another system, generate reports, or perform batch processing.

Practical examples:

  • Fetching all contacts up to a specified limit to export them to a CRM or mailing list.
  • Retrieving contacts to analyze customer data or segment users.
  • Using the contact list as input for further automation workflows.

Properties

Name Meaning
Limit Maximum number of contact results to return. Accepts numbers from 1 to 100. Default is 20.

Output

The output is an array of JSON objects, each representing a contact retrieved from the GoHighLevel API. Each item contains the full contact data as returned by the API, including fields such as first name, last name, email, phone, and other contact details.

The node does not output binary data.

Example output structure (simplified):

[
  {
    "json": {
      "id": "contact_id_123",
      "firstName": "John",
      "lastName": "Doe",
      "email": "john.doe@example.com",
      "phone": "+1234567890",
      ...
    }
  },
  {
    "json": {
      "id": "contact_id_456",
      "firstName": "Jane",
      "lastName": "Smith",
      "email": "jane.smith@example.com",
      "phone": "+0987654321",
      ...
    }
  }
]

Dependencies

  • Requires an API key credential for authenticating with the GoHighLevel API.
  • The node uses the base URL https://services.leadconnectorhq.com for API requests.
  • The API key must have access to the relevant location ID, which is included automatically from the credentials.
  • No additional environment variables are required beyond the API key credential.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • If the location ID associated with the API key is incorrect or missing, the request may fail or return no contacts.
    • Exceeding the maximum allowed limit (over 100) will be rejected; ensure the limit is between 1 and 100.
    • Network connectivity issues can cause request failures.
  • Error messages:

    • "Unauthorized" or "Invalid API key": Check that the API key credential is correctly configured and valid.
    • "Not Found" or empty results: Verify the location ID and that there are contacts available in that location.
    • "Request failed" or timeout errors: Check network connection and API service status.
  • To handle errors gracefully, enable the node's "Continue On Fail" option to allow workflow execution to proceed even if some requests fail.

Links and References

Discussion