Delete Task
highlevel.delete_task
ActionCRM & salesconnection required
Calls the HighLevel API with the connection's credentials.
Delete a task from a contact.
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
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
contact_id The contact id, e.g. 'ocQHyuzHvysMo5N5VsXc' — the last segment of the contact's URL in HighLevel. | string | Yes | — | — | — |
task_id Id of the task to act on, from highlevel.list_tasks — not its name. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
succeeded True when HighLevel confirmed the delete. | boolean | — |
reported False when HighLevel answered 2xx without a success flag — accepted, but not confirmed. | boolean | — |
response HighLevel's delete response exactly as sent. | object | — |
contact_id The contact the task hung off. | string | — |
task_id The task that was deleted. | string | — |
{
"contact_id": "",
"reported": false,
"response": {},
"succeeded": false,
"task_id": ""
}Notes
- HighLevel has no standalone task endpoint: a task is addressed by contact and task id.
See Delete 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.