Inputs
Outputs
None. This block does not expose a useful downstream output. No later block can read a{{ steps.complete_task.* }} value from it. If a later block needs the task, reference the task variable you passed into Complete task. Do not wait for this block to return one.
Behavior
Complete task changes the status of the referenced task to complete, then ends. It acts on whichever task the input resolves to at run time. So a variable that points to a single task completes exactly that task. The block reads its target from a task reference. Pass it the task variable from Create task, or the one carried from the Task created trigger. A record and the task linked to it are different objects. The input is typed as a task. So passing a record or a linked record instead of a task fails the block. The action is a write, so it consumes 1 credit each time it runs. Only the path a workflow actually runs consumes credits. A Complete task block on a branch that does not run costs nothing for that run.Gotchas
- The input must be a task, not a linked record. A task and the record it links to are different objects. Wiring a record variable into the input fails the block. Map the task variable from Create task or Task created, not the record the task points at.
- There is no output to chain from. The block returns no usable downstream value. A later block that expects a completed-task result has nothing to read. Reference the original task variable you passed in instead of expecting one back from Complete task.
- Auto-completing human tasks hides operational problems. Closing a task a person was meant to action removes the signal that the work is overdue or stuck. Complete only tasks the workflow created for itself. Leave human-owned tasks for a person to close.
Examples
Closing a follow-up task once an external confirmation arrives
A workflow creates a follow-up task. It waits for an external system to confirm the work is done, then closes the task it created.
After the confirmation webhook resolves, the workflow marks the follow-up task complete. The task no longer appears in the assignee’s open list.
Completing the triggering task after a sync succeeds
A workflow starts from the Task created trigger. It syncs the task to an external system, then closes the task once the sync returns success.
When the sync succeeds, the triggering task is marked complete. This keeps the Attio task list in step with the external system of record.