Plutio icon

Plutio

Consume Plutio API

Overview

The Plutio Task Move operation in n8n allows you to move a task from one task group to another within your Plutio workspace. This is useful for workflow automation where tasks need to be reorganized, reprioritized, or moved between different stages or categories (task groups) as part of a process.

Common scenarios:

  • Moving a task to a "Completed" group after finishing.
  • Reassigning tasks to different project phases.
  • Automating Kanban board transitions.

Example:
Automatically move a task to the "In Review" group when a related approval is received.


Properties

Name Type Meaning
Task ID String The unique identifier of the task you want to move.
Task Group Name or ID Options The destination task group. You can select from a list or specify an ID/expression.
Position Number The position (after which task ID) where the task should be placed in the new group.

Output

The node returns the result of the move operation as JSON. The structure typically includes:

  • All available fields of the updated/moved task, such as:
    • _id: Task ID
    • title: Task title
    • taskGroupId: The new group ID
    • Other task properties as provided by the Plutio API

If the API does not return a detailed object, it may return a simple success confirmation like:

{
  "success": true
}

Dependencies

  • External Service: Requires access to the Plutio API.
  • Authentication: Needs valid Plutio API credentials configured in n8n under the name plutioApi.

Troubleshooting

Common issues:

  • Invalid Task ID: If the provided Task ID does not exist, the API will return an error.
  • Invalid Task Group: If the target group is missing or incorrect, the move will fail.
  • Missing Permissions: The connected Plutio account must have permission to move tasks.

Error messages and resolutions:

  • "Task not found": Check that the Task ID is correct and exists in Plutio.
  • "Task group not found": Ensure the Task Group Name or ID is valid.
  • "Unauthorized": Verify that your API credentials are correct and have sufficient permissions.

Links and References

Discussion