Complete Task

highlevel.complete_task
ActionCRM & salesconnection required

Calls the HighLevel API with the connection's credentials.

Mark a task completed, or reopen it.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
HighLevel
Secret shape
{"client_id": "…", "client_secret": "…", "refresh_token": "…"} for a marketplace app, or {"access_token": "…"} for a Private Integration Token
Config it needs
location_id, user_type, base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
contact_id
The contact id, e.g. 'ocQHyuzHvysMo5N5VsXc' — the last segment of the contact's URL in HighLevel.
stringYes———
task_id
Id of the task to act on, from highlevel.list_tasks — not its name.
stringYes———
completed
True to complete the task, false to reopen it.
booleanNotrue——

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "completed": true
}

Output

One shape.

result

FieldTypeExample
id
The task id.
string—
title
The task's title, as HighLevel stored it.
string—
body
Task body text.
string—
assignedTo
User id the task is assigned to.
string—
dueDate
When the task is due (ISO-8601).
string—
completed
True once the task is done.
boolean—
contactId
The contact the task hangs off.
string—
{
  "assignedTo": "",
  "body": "",
  "completed": false,
  "contactId": "",
  "dueDate": "",
  "id": "",
  "title": ""
}

Notes

  • HighLevel has no standalone task endpoint: a task is addressed by contact and task id.

See Complete Task run in a workflow.

In a technical demo we add the HighLevel connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.