RogerRoger icon

RogerRoger

Interact with RogerRoger API for Person, Organization and Task resources

Actions15

Task → Update

AI-generated

Overview

The node integrates with the RogerRoger API to update existing tasks. It allows users to modify various attributes of a task such as its title, status (workspace and column), description, tags, associated people and organizations, and due date. This is useful in automation workflows where task details need to be programmatically updated based on external triggers or data changes.

Practical examples include:

  • Automatically updating the status of a task when a related event occurs.
  • Changing the due date or adding tags to a task based on customer interactions.
  • Modifying task descriptions or associations to people and organizations dynamically.

Properties

Name Meaning
Task ID Select the task to update by its UUID or search from a list of tasks. Must be a valid UUID format.
Update Fields Collection of fields to update on the task:
  Title New title for the task.
  Status Update the workspace and column of the task. Includes:
    Workspace Workspace name or ID where the task resides.
    Column Column name or ID within the workspace to set the task's status.
  Description Description text for the task.
  Tags Tags associated with the task. Multiple tags can be selected from available options.
  People People associated with the task. Multiple selections allowed.
  Organizations Organizations associated with the task. Multiple selections allowed.
  Due Date Due date for the task, selectable via a date-time picker.

Output

The node outputs JSON data representing the updated task resource returned from the RogerRoger API. The output includes all relevant fields of the task after the update operation, merged with metadata indicating the resource type ("task") and operation ("update"). There is no binary data output.

Example structure snippet (simplified):

{
  "resource": "task",
  "operation": "update",
  "id": "uuid-of-task",
  "title": "Updated Task Title",
  "description": "Updated description",
  "tags": ["tag1", "tag2"],
  "people": ["personId1", "personId2"],
  "organizations": ["orgId1"],
  "dueDate": "2024-07-01T12:00:00Z",
  "workspace": "/workspaces/123",
  "column": "/workspaces/123/columns/456"
}

Dependencies

  • Requires an API key credential for authenticating with the RogerRoger API.
  • Needs network access to the RogerRoger API base URL configured in the credentials.
  • Uses internal helper methods to fetch dynamic options like workspaces, columns, tags, people, and organizations for dropdowns.
  • No additional external dependencies beyond the RogerRoger API and n8n core modules.

Troubleshooting

  • Invalid Task ID: Ensure the Task ID is a valid UUID format. The node validates this and will error if invalid.
  • API Authentication Errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Missing Required Fields: When updating status, both workspace and column must be valid and exist; otherwise, the API may reject the request.
  • Network Issues: Check connectivity to the RogerRoger API endpoint.
  • Error Messages: The node throws errors with messages from the API response. Common errors include "Not Found" if the task does not exist or "Unauthorized" if credentials are invalid.
  • Use the "Continue On Fail" option in n8n to handle individual item errors gracefully in batch operations.

Links and References

Discussion