POST /tasks/{task_gid}/setParent

Required scope: tasks:write

Updates the parent of a given task. This endpoint can be used to make a task a subtask of another task, or to remove its existing parent. When using insert_before and insert_after, at most one of those two options can be specified, and they must already be subtasks of the parent. Returns the complete, updated record of the affected task.

Servers

Path parameters

Name Type Required Description
task_gid String Yes

The task to operate on.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Query parameters

Name Type Required Description
opt_pretty Boolean No

Provides “pretty” output. Provides the response in a “pretty” format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging.

opt_fields[] Array No

This endpoint returns a resource which excludes some properties by default. To include those optional properties, set this query parameter to a comma-separated list of the properties you wish to include.

Request body fields

Name Type Required Description
data Object No
data.insert_after String No

A subtask of the parent to insert the task after, or null to insert at the beginning of the list.

data.parent String Yes

The new parent of the task, or null for no parent.

data.insert_before String No

A subtask of the parent to insert the task before, or null to insert at the end of the list.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.