SmensoInstall

Summary

Update the dependencies of a task by specifying an array of predecessor task dependency objects, each including task ID, dependency type (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish), and lag time.

Inputs

• Project ID (required) — The GUID of the project containing the task.
• Task ID (required) — The GUID of the task to update dependencies for.
• Predecessor Task IDs (JSON) (required) — A JSON array of dependency objects with properties: taskId (string), type (dependency type: FS, SS, FF, SF), and lag (number) representing the lag time in the dependency.

Output shape

The updated task dependencies as returned by the API JSON response.

The operation sends a PATCH request to update dependencies for the given task. It requires the dependency data as a JSON array. The shape matches the API's JSON response to the PATCH call, containing the updated dependencies. Pagination or errors are handled outside this operation.

Examples

Example 1: Update a task's dependencies by specifying multiple predecessor tasks with different dependency types and lags.

Provide valid Project ID and Task ID; set Predecessor Task IDs (JSON) to an array of objects each with taskId, type (FS/SS/FF/SF), and lag (integer).

Links

• n8n community nodes installation guide