Overview
This node integrates with the FullFunnel (HighLevel) service to manage contacts. Specifically, the "Get All" operation under the "Contact" resource retrieves multiple contact records from the FullFunnel platform. It supports fetching either all contacts or a limited subset based on user input.
Common scenarios for this node include:
- Synchronizing contact lists from FullFunnel into other systems.
- Exporting contacts for marketing campaigns or analysis.
- Automating workflows that require bulk access to contact data.
For example, a user might configure this node to fetch up to 50 contacts to process them in subsequent workflow steps, such as filtering or sending emails.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all available contacts (true) or limit the number of results (false). |
| Limit | The maximum number of contacts to return when Return All is set to false. Allowed values are between 1 and 100. Default is 50. |
Output
The output consists of an array of JSON objects, each representing a contact retrieved from FullFunnel. Each contact object contains the contact's details as provided by the FullFunnel API.
Example structure of one item in the output array:
{
"json": {
"id": "contact-id",
"email": "example@email.com",
"firstName": "John",
"lastName": "Doe",
"phone": "+1234567890",
"locationId": "location-id",
...
}
}
No binary data is output by this node.
Dependencies
- Requires an API key credential for FullFunnel (HighLevel) authentication.
- The node makes HTTP requests to the FullFunnel API endpoint at
https://services.leadconnectorhq.com. - The user must provide valid credentials including an API key and location ID.
- The node uses the n8n HTTP request helper to communicate with the FullFunnel API.
Troubleshooting
Common issues:
- Invalid or missing API key or location ID will cause authentication failures.
- Request limits: If
Return Allis false butLimitexceeds 100, the node will reject the input due to validation. - Network connectivity problems can cause request timeouts or errors.
Error messages:
- Errors returned from the FullFunnel API (e.g., 401 Unauthorized) will be surfaced as node execution errors.
- If "Continue On Fail" is enabled, errors for individual items will be included in the output JSON under an
errorfield instead of stopping the workflow.
Resolution tips:
- Verify API key and location ID correctness.
- Ensure network access to the FullFunnel API endpoint.
- Use "Return All" carefully to avoid large data loads that may impact performance.
Links and References
- FullFunnel (HighLevel) API Documentation (Note: link is illustrative; verify actual API docs)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/