TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation updates a single task in the connected system via the Twenty API. It allows users to modify various attributes of an existing task by specifying its unique identifier and providing new values for one or more fields. This is useful in workflows where task details need to be programmatically changed, such as updating status after completion, changing assignees, adjusting due dates, or modifying task descriptions.

Practical examples include:

  • Automatically marking a task as "DONE" when a related process finishes.
  • Changing the assignee of a task based on workload distribution.
  • Updating the task's position or priority dynamically.
  • Modifying the task title or body content based on external inputs.

Properties

Name Meaning
Id The unique identifier of the task to update. This is required to specify which task record will be modified.
Depth Determines how much nested related object data to include in the response: 0 returns only the primary task info; 1 includes directly related objects; 2 includes related objects of those related objects.
Body The main textual content or description of the task.
Title The title or name of the task.
Position Numeric value indicating the task's position or order among other tasks.
Assignee Id Identifier of the user assigned to the task.
Created By JSON object describing the creator of the task record.
Status Current status of the task. Options are: "TODO", "IN PROGRESS", or "DONE".
Due At Due date/time string indicating when the task should be completed.
Body V 2 Alternative JSON-formatted body content for the task, allowing richer or structured data than the plain text "Body" field.

Output

The node outputs the updated task object in JSON format. The structure reflects the task's properties including any nested related objects depending on the Depth parameter. This output can be used downstream in the workflow for further processing or logging.

If binary data were involved (not indicated here), it would typically represent attachments or files related to the task, but this node focuses on JSON data.

Dependencies

  • Requires an active connection to the Twenty API with appropriate authentication credentials (e.g., an API key or token).
  • The node expects the base URL and authentication details to be configured in n8n credentials.
  • No additional external dependencies beyond the Twenty API and n8n environment are needed.

Troubleshooting

  • Missing or invalid Id: The update operation requires a valid task ID. Ensure the "Id" property is correctly set and corresponds to an existing task.
  • Invalid JSON in Created By or Body V 2: These fields expect valid JSON strings. Malformed JSON will cause parsing errors. Validate JSON syntax before input.
  • Status value errors: Only "TODO", "IN PROGRESS", or "DONE" are accepted. Using unsupported status values will result in errors.
  • API authentication failures: Check that the API credentials are correctly configured and have sufficient permissions to update tasks.
  • Network or connectivity issues: Ensure the n8n instance can reach the Twenty API endpoint.

Links and References

Discussion