Plutio icon

Plutio

Consume Plutio API
Join our community

Actions20

Overview

The Plutio Task Update node allows you to update an existing task in your Plutio workspace. This is useful for automating workflows where tasks need to be modified based on triggers or other data, such as updating the assignee, changing the project or board, editing the title or description, or modifying custom fields.

Common scenarios:

  • Automatically reassigning tasks when a team member is unavailable.
  • Updating task details from another system (e.g., CRM, support ticket).
  • Bulk-updating tasks with new information or status changes.

Example:
When a support ticket is escalated, use this node to update the corresponding Plutio task's assignee and add escalation notes.

Properties

Name Type Meaning
Task ID String The unique identifier of the task to update.
Options → Project Name or ID Options The project associated with the task. You can select from a list or specify an ID/expression.
Options → Task Board Name or ID Options The task board within the project. Select from a list or specify an ID/expression.
Options → Task Group Name or ID Options The group within the task board. Select from a list or specify an ID/expression.
Options → Template Name or ID Options The template to apply to the task. Select from a list or specify an ID/expression.
Options → Creator Name or ID Options The user who created the task. Select from a list or specify an ID/expression.
Options → Title String The new title for the task.
Options → Description String The new description for the task (HTML format).
Options → Custom Fields Collection Key-value pairs for custom fields. Only dates in YYYY-MM-DD are accepted for date fields. Each entry includes a field name/ID and value.
Assigned To: Name or ID Collection List of users to assign the task to. You can select from a list or specify IDs/expressions. Multiple assignees supported.

Output

  • The output is a JSON object representing the updated task as returned by the Plutio API.
  • If the operation is successful, the response will include all standard task fields (such as _id, title, descriptionHTML, projectId, assignedTo, etc.), reflecting the updated values.
  • If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message.

Example output:

{
  "_id": "task123",
  "title": "Updated Task Title",
  "descriptionHTML": "<p>New description</p>",
  "projectId": "proj456",
  "assignedTo": ["user789"],
  // ...other task fields...
}

Dependencies

  • External Service: Requires access to the Plutio API.
  • API Credentials: You must configure Plutio API credentials in n8n under the name plutioApi.
  • n8n Configuration: No additional environment variables required beyond credential setup.

Troubleshooting

Common Issues:

  • Invalid Task ID: If the provided Task ID does not exist, the node will return an error from the Plutio API.
  • Permission Denied: If the API key lacks permission to update tasks, you will receive an authorization error.
  • Custom Field Errors: Supplying invalid custom field names/IDs or incorrect value formats (especially for date fields) may result in errors.
  • Assignee Not Found: If the specified assignee does not exist, the update will fail.

Error Messages:

  • "Task not found": Check that the Task ID is correct and exists in Plutio.
  • "Unauthorized": Verify your API credentials and permissions.
  • "Invalid custom field value": Ensure custom field values match expected types/formats.

Links and References

Discussion