Actions17
Overview
The node integrates with the HighLevel API to retrieve multiple contact records. It is designed to fetch a list of contacts from the user's HighLevel account, supporting filtering, sorting, and pagination options.
This node is useful in scenarios where you want to:
- Synchronize or export contact lists from HighLevel.
- Perform bulk operations on contacts by first retrieving them.
- Build workflows that react to or analyze contact data.
For example, you could use this node to get all contacts added within a certain timeframe, sorted by their update date, or to search contacts matching specific keywords across fields like name, phone, email, tags, or company name.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching contacts or limit the number of results. |
| Limit | Maximum number of contacts to return (only applicable if "Return All" is false). |
| Filters | Query string to search contacts by Name, Phone, Email, Tags, and Company Name. |
| Options | Additional options for ordering and sorting the results: |
| Order | Sort order of results: "Descending" or "Ascending". |
| Sort By | Field to sort by: "Date Added" or "Date Updated". |
Output
The node outputs an array of contact objects in the json field of each item. Each object represents a contact record retrieved from HighLevel, containing details such as contact name, phone, email, tags, company name, and other relevant metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for HighLevel.
- The node makes HTTP requests to the HighLevel API endpoint at
https://services.leadconnectorhq.com. - Proper permissions and API access must be granted to the connected account to read contact data.
Troubleshooting
- Empty Results: If no contacts are returned, verify that the query filter matches existing contacts and that the account has contacts available.
- Authentication Errors: Ensure the OAuth2 credential is valid and has not expired. Re-authenticate if necessary.
- Rate Limits: The HighLevel API may enforce rate limits; if errors occur due to too many requests, implement delays or reduce request frequency.
- Invalid Parameters: Check that numeric limits are positive integers and that option values conform to allowed choices.