GoHighLevel Simple

Integração simples com GoHighLevel API usando API Key
Join our community

Actions6

Overview

This node integrates with the GoHighLevel API to manage opportunities and other resources such as contacts and locations. Specifically, for the Opportunity - Get All operation, it retrieves a list of all opportunities associated with the user's account, limited by a specified maximum number of results.

Typical use cases include:

  • Fetching all sales opportunities to display or process in workflows.
  • Synchronizing opportunity data from GoHighLevel into other systems.
  • Automating reporting or analytics based on current pipeline opportunities.

For example, a user might set this node to "Get All" opportunities with a limit of 50 to retrieve the top 50 open deals for further processing or notification.

Properties

Name Meaning
Limit Maximum number of opportunity records to return. Accepts numbers between 1 and 100.

Output

The node outputs an array of JSON objects, each representing an opportunity retrieved from the GoHighLevel API. Each object contains the full details of an opportunity as returned by the API, including fields like pipeline ID, stage ID, opportunity name, status, contact association, and other metadata.

No binary data is output by this node.

Example output structure (simplified):

[
  {
    "id": "opportunity_id_123",
    "pipelineId": "pipeline_id_abc",
    "stageId": "stage_id_xyz",
    "name": "Opportunity Name",
    "status": "open",
    "contactId": "contact_id_456",
    ...
  },
  ...
]

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 internally used in requests.
  • No additional external dependencies are required.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Incorrect or missing location ID in credentials may result in empty or unauthorized responses.
    • Exceeding the maximum allowed limit (over 100) will be rejected by the node's input validation.

  • Error messages:

    • Authentication errors typically indicate invalid API keys; verify and update credentials.
    • HTTP 403 or 401 errors suggest permission issues; ensure the API key has proper access rights.
    • Network or timeout errors may occur if the GoHighLevel service is unreachable; check connectivity.

  • To resolve errors, confirm that the API key is valid, the location ID is correct, and the limit parameter is within allowed bounds.

Links and References

Discussion