Actions16
Overview
The HighLevel node for n8n allows you to interact with the HighLevel API, specifically to retrieve all tasks associated with a given contact. The "Task: Get All" operation fetches a list of tasks belonging to a specified contact, with options to limit the number of results or return all available tasks.
Common scenarios:
- Fetching all tasks related to a specific contact for reporting or automation.
- Integrating task data from HighLevel into other systems or workflows.
- Monitoring and processing tasks assigned to contacts in bulk.
Practical example:
You might use this node to automatically pull all tasks for a contact when they reach a certain stage in your CRM pipeline, then trigger follow-up actions based on those tasks.
Properties
| Name | Type | Meaning |
|---|---|---|
| Contact ID | String | The unique identifier of the contact whose tasks you want to retrieve. |
| Return All | Boolean | Whether to return all matching tasks (true) or limit the number (false). |
| Limit | Number | The maximum number of tasks to return (only used if Return All is false). |
Output
The output will be an array of JSON objects, each representing a task associated with the specified contact. Each object contains the details of a single task as returned by the HighLevel API.
Example output structure:
[
{
"id": "string",
"title": "string",
"description": "string",
"status": "string",
"dueDate": "string",
// ...other task fields as provided by the API
}
]
Note: The exact fields depend on the HighLevel API's response.
Dependencies
- External Service: Requires access to the HighLevel API.
- API Key: You must configure valid HighLevel API credentials in n8n under the name
highLevelApi. - n8n Configuration: No additional configuration required beyond credential setup.
Troubleshooting
Common issues:
- Invalid Contact ID: If the provided Contact ID does not exist, the node may return an empty array or an error.
- Missing Credentials: If the HighLevel API credentials are not set up correctly, authentication errors will occur.
- Limit Exceeded: If you set a limit outside the allowed range (1–100), the node may throw a validation error.
Error messages and resolutions:
"401 Unauthorized": Check that your API key is correct and has sufficient permissions."404 Not Found": Ensure the Contact ID exists in your HighLevel account."400 Bad Request": Verify that all required properties are filled and within valid ranges.