Actions17
Overview
This node integrates with the HighLevel API to update a specific task associated with a contact. It allows users to modify various attributes of a task such as its title, body content, due date, completion status, and assigned user. This is useful in scenarios where task management needs to be automated or synchronized with other systems, for example updating follow-up tasks after a customer interaction or adjusting deadlines based on new information.
Practical examples include:
- Marking a task as completed when a related event occurs.
- Changing the assigned user of a task dynamically based on workload.
- Updating the due date or details of a task programmatically from another workflow.
Properties
| Name | Meaning |
|---|---|
| Contact Email or ID | The contact to which the task belongs. Can be selected from a list or specified by an expression. |
| Task ID | The unique identifier of the task to update. |
| Update Fields | A collection of fields to update on the task: |
| - Assigned To | User to assign the task to. Selectable from a list or via expression. |
| - Completed | Boolean flag indicating if the task is completed. |
| - Body | Text content or description of the task. |
| - Due Date | The due date and time for the task. |
| - Title | The title or name of the task. |
Output
The node outputs JSON data representing the updated task object returned by the HighLevel API. This typically includes all task properties reflecting the changes made, such as updated title, completion status, assigned user, and timestamps.
If binary data were involved (not indicated here), it would represent file attachments or similar, but this node focuses on JSON task data only.
Dependencies
- Requires an API authentication token configured in n8n credentials to access the HighLevel API.
- Depends on the HighLevel service being available at
https://services.leadconnectorhq.com. - Uses internal helper methods to load options for contacts and users dynamically.
Troubleshooting
- Invalid Contact or Task ID: If the provided contact or task ID does not exist or is incorrect, the API will return an error. Verify IDs are correct and accessible.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth2 token is properly set up.
- Permission Issues: The authenticated user must have permission to update tasks for the specified contact.
- Date Format Issues: The due date must be in a valid ISO 8601 format; otherwise, the API may reject the request.
- Empty Update Fields: If no fields are specified to update, the node might send an empty payload resulting in no changes or errors.