Actions16
Overview
The HighLevel node's "Task" resource with the "Create" operation allows users to create a new task associated with a specific contact in the HighLevel platform. This is useful for automating task management workflows, such as assigning follow-up actions to team members, setting reminders, or tracking progress on client-related activities.
Practical examples:
- Automatically create a follow-up task when a new lead is added.
- Assign tasks to team members based on incoming support requests.
- Schedule tasks with due dates for project milestones.
Properties
| Name | Type | Meaning |
|---|---|---|
| Contact ID | String | The unique identifier of the contact to whom the task will be linked. |
| Title | String | The title or name of the task. |
| Due Date | DateTime | The deadline by which the task should be completed. |
| Additional Fields | Collection | Optional fields to further define the task (see below): |
| └ Assigned To | Options | The user assigned to the task; can select from a list or specify an ID via expression. |
| └ Description | String | A detailed description of the task. |
| └ Status | Options | The status of the task; possible values are "Incompleted" or "Completed". |
Output
The node outputs a json object representing the created task. The structure typically includes:
- Task ID
- Associated Contact ID
- Title
- Due Date
- Assigned User (if provided)
- Description (if provided)
- Status (default: "Incompleted" unless specified)
Example output:
{
"id": "task_12345",
"contactId": "contact_67890",
"title": "Follow up call",
"dueDate": "2024-07-01T10:00:00Z",
"assignedTo": "user_abcde",
"description": "Call the client to discuss next steps.",
"status": "incompleted"
}
Note: Actual output fields may vary depending on the API response.
Dependencies
- External Service: Requires access to the HighLevel API.
- API Key: Must configure valid HighLevel API credentials in n8n under the credential type
highLevelApi. - Environment: No additional environment variables required beyond standard n8n setup.
Troubleshooting
Common issues:
- Missing or invalid Contact ID: Ensure the Contact ID exists in HighLevel; otherwise, the API will reject the request.
- Invalid date format: The Due Date must be in a valid ISO 8601 format.
- Insufficient permissions: The API key used must have permission to create tasks.
Common error messages:
"Contact not found": Check that the Contact ID is correct and exists."Invalid field value": Verify all required fields are filled and formatted correctly."Unauthorized": Ensure your API credentials are set up properly in n8n.