Overview
This node interacts with the FullFunnel (GoHighLevel) API to manage contacts. Specifically, the "Get All" operation under the "Contact" resource retrieves multiple contacts from the FullFunnel system. It supports filtering by search query, tags, and pagination via a "start after" contact ID. Users can choose to return all matching contacts or limit the number of results.
This node is beneficial in scenarios where you need to synchronize, analyze, or process contact data stored in FullFunnel. For example, marketing automation workflows can fetch all contacts tagged with a specific campaign label, or CRM integrations can pull batches of contacts for reporting or updates.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching contacts or only up to a specified limit. |
| Limit | Maximum number of contacts to return if not returning all. Value range: 1 to 100. |
| Filters | Collection of filters to narrow down the contacts retrieved: |
| - Query | Search string to filter contacts by text match. |
| - Tags | Comma-separated list of tags to filter contacts by. |
| - Start After | Contact ID to start after, used for pagination to continue fetching from a specific point. |
Output
The output is an array of JSON objects, each representing a contact retrieved from FullFunnel. Each contact object contains fields as returned by the FullFunnel API, such as contact details and metadata.
If "Return All" is enabled and there are more than 100 contacts, the node automatically paginates through results up to a maximum of 500 contacts, aggregating them into the output.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for FullFunnel (GoHighLevel) authentication.
- The node makes HTTP requests to the FullFunnel REST API endpoint at
https://rest.gohighlevel.com/v2. - The node expects a configured location ID from the credentials to scope contact queries.
Troubleshooting
Common issues:
- Exceeding API rate limits may cause request failures.
- Providing invalid or expired API credentials will result in authentication errors.
- Using an invalid "Start After" contact ID for pagination may lead to empty or incomplete results.
- Setting "Return All" with very large datasets may hit internal limits (max 500 contacts fetched).
Error messages:
- Authentication errors typically indicate missing or incorrect API keys; verify credentials.
- Validation errors on filters or parameters suggest incorrect input values; check property formats.
- Network or timeout errors may require retrying or checking connectivity.
Links and References
- FullFunnel (GoHighLevel) API Documentation
- n8n documentation on HTTP Request Node (for understanding underlying request mechanics)