HighLevelPro icon

HighLevelPro

Consume HighLevel API
Join our community

Actions17

Overview

This node integrates with the HighLevel API to create a new Task associated with a specific Contact. It allows users to specify key details such as the task's title, due date, completion status, and optionally assign the task to a user or add descriptive body text.

Common scenarios include automating task creation for follow-ups, reminders, or action items linked to contacts in a CRM workflow. For example, after capturing a lead, this node can automatically create a task to call the contact within a specified timeframe.

Properties

Name Meaning
Contact Email or ID The contact to which the task belongs. Choose from a list of contacts or specify an ID via expression.
Title The title or name of the task.
Due Date The date and time by which the task should be completed.
Completed Boolean indicating whether the task is marked as completed (true) or not (false).
Additional Fields: Assigned To Optionally assign the task to a user. Choose from a list or specify a user ID via expression.
Additional Fields: Body Optional detailed description or notes about the task.

Output

The node outputs JSON data representing the created task object returned by the HighLevel API. This typically includes fields such as the task ID, title, due date, completion status, assigned user, and any other metadata provided by the API response.

No binary data output is involved.

Dependencies

  • Requires an API authentication token configured via OAuth2 credentials for the HighLevel service.
  • The node uses the base URL https://services.leadconnectorhq.com and expects API version 2021-07-28.
  • It depends on helper methods to load options dynamically for contacts and users.

Troubleshooting

  • Authentication errors: Ensure that the OAuth2 credential is correctly set up and has valid access tokens.
  • Invalid contact or user IDs: When specifying IDs manually, verify they exist in the HighLevel account; otherwise, the API will reject the request.
  • Missing required fields: The node requires Contact Email or ID, Title, Due Date, and Completed fields. Omitting these will cause errors.
  • Date format issues: The Due Date must be a valid datetime string; invalid formats may cause API rejections.
  • API rate limits or connectivity issues: Network problems or exceeding API limits can cause failures; retry or check API usage quotas.

Links and References

Discussion