Actions16
Overview
The HighLevel node's "Task: Update" operation allows you to update an existing task in the HighLevel platform. This is useful for automating workflows where task details—such as title, due date, assignee, or status—need to be programmatically modified based on triggers or other data within your n8n workflow.
Common scenarios:
- Automatically updating a task's status when a related event occurs (e.g., marking a task as completed when a deal closes).
- Changing the assignee of a task based on workload balancing.
- Updating task details from another system or form submission.
Practical example:
When a support ticket is resolved in your helpdesk system, use this node to update the corresponding HighLevel task's status to "Completed" and add a resolution note.
Properties
| Name | Type | Meaning |
|---|---|---|
| Contact ID | String | The identifier of the contact to whom the task belongs. Required to locate the correct task. |
| Task ID | String | The unique identifier of the task to update. Required. |
| Title | String | The new title for the task. Required. |
| Due Date | DateTime | The updated due date for the task. Required. |
| Additional Fields | Collection | Optional fields to further specify task details (see below). |
Additional Fields (Collection):
- Assigned To (Options): User to assign the task to. Can select from a list or specify an ID via expression.
- Description (String): A description or notes for the task.
- Status (Options): The current status of the task; options are "Incompleted" or "Completed".
Output
The node outputs a json object representing the updated task. The structure typically includes:
- Task identifiers (e.g.,
id,contactId) - Updated fields (e.g.,
title,dueDate,assignedTo,description,status) - Any additional metadata returned by the HighLevel API
Example output:
{
"id": "task_123",
"contactId": "contact_456",
"title": "Follow up call",
"dueDate": "2024-07-01T10:00:00Z",
"assignedTo": "user_789",
"description": "Call client to discuss renewal.",
"status": "completed"
}
Note: Actual output fields may vary depending on the HighLevel API 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 special environment variables required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid Contact ID or Task ID: If either ID is incorrect or does not exist, the API will return an error. Double-check that both IDs are valid and correspond to existing records.
- Missing Required Fields: Omitting required fields like Title or Due Date will result in validation errors.
- Permission Denied: Ensure the API key used has sufficient permissions to update tasks.
Common error messages:
"404 Not Found": The specified task or contact does not exist. Verify the IDs."400 Bad Request": One or more required fields are missing or invalid. Check all input values."401 Unauthorized": Invalid or missing API credentials. Reconfigure your HighLevel API credentials in n8n.