Actions16
Overview
The HighLevel node for n8n allows you to interact with the HighLevel API, specifically to retrieve a list of contacts using the "Get All" operation. This is useful for automating workflows that require fetching contact data from your HighLevel CRM, such as syncing contacts to other systems, generating reports, or triggering actions based on contact lists.
Practical examples:
- Retrieve all contacts and add them to a Google Sheet.
- Filter contacts by name or email and send targeted emails.
- Fetch recently added contacts and trigger onboarding sequences.
Properties
| Name | Type | Meaning |
|---|---|---|
| Return All | Boolean | Whether to return all results or only up to a given limit. If false, the number of results is limited. |
| Limit | Number | Max number of results to return (1–100). Only shown if "Return All" is false. |
| Filters | Collection | Additional filters for the query. Includes: • Query (string): Search by Name, Phone, Email, Tags, Company Name. |
| Options | Collection | Additional options for sorting: • Order (Descending/Ascending): Sort order. • Sort By (Date Added/Updated): Field to sort by. |
Output
The node outputs a list of contact objects in the json field. Each object represents a contact retrieved from HighLevel and contains fields such as name, phone, email, tags, company name, and other contact details as provided by the HighLevel API.
Example output structure:
[
{
"json": {
"id": "123",
"name": "John Doe",
"email": "john@example.com",
"phone": "+1234567890",
"tags": ["Lead", "Newsletter"],
"companyName": "Acme Inc.",
// ...other contact fields
}
},
...
]
Note: The actual fields depend on the HighLevel API response.
Dependencies
- External Service: Requires access to the HighLevel API.
- API Key: You must configure HighLevel API credentials in n8n (
highLevelApi). - Environment: No special environment variables are required beyond n8n credential setup.
Troubleshooting
Common issues:
- Invalid API Key: If the API key is missing or incorrect, authentication errors will occur. Ensure your credentials are set up correctly in n8n.
- Rate Limits: The HighLevel API may enforce rate limits. If you receive errors about too many requests, try reducing the frequency of your queries.
- Filter Syntax: Incorrect filter values (e.g., malformed query strings) may result in empty results or errors. Double-check your filter inputs.
Error messages:
"401 Unauthorized": Check your API credentials."400 Bad Request": Review your input parameters, especially filters and limits."429 Too Many Requests": Wait before retrying; consider adding delays between requests.