Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Task → Update
AI-generatedOverview
This node integrates with the Twenty CRM API to update an existing Task record. It allows users to modify details such as the task's title, body content, status, and due date. This operation is useful in scenarios where task information needs to be kept current, for example, updating the progress of a task, changing its deadline, or editing descriptive details.
Practical examples include:
- Marking a task as "In Progress" or "Done" after work has started or completed.
- Changing the due date of a task when deadlines shift.
- Updating the task description or title to reflect new requirements or clarifications.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Task record to update. |
| Title | The title or name of the task. |
| Body | The detailed description or notes about the task, supporting multiline text. |
| Status | The current state of the task. Options: "To Do", "In Progress", "Done". |
| Due Date | The date and time by which the task should be completed. |
Output
The node outputs JSON data representing the updated Task record as returned by the Twenty CRM API. The structure typically includes all fields of the task, reflecting the changes made. If multiple input items are processed, the output is an array of such JSON objects, each corresponding to one updated task.
No binary data output is produced by this node.
Dependencies
- Requires connection to the Twenty CRM API via an API key credential configured in n8n.
- The node uses HTTP PATCH requests to update task records on the Twenty CRM service.
- Proper API URL and authentication credentials must be set up in n8n for successful communication.
Troubleshooting
- Invalid JSON in Fields: Although not applicable directly to the Task resource update (which does not use a JSON field input), similar errors can occur if custom resources are used improperly. Ensure any JSON inputs are correctly formatted.
- HTTP Errors: Errors from the API such as 401 Unauthorized or 404 Not Found may indicate invalid credentials or incorrect task IDs. Verify that the API key is valid and the task ID exists.
- Missing Required Fields: The "ID" and "Title" fields are required. Omitting these will cause the node to fail. Make sure these properties are provided.
- Date Format Issues: The "Due Date" must be a valid datetime string. Invalid formats may cause API rejection.
Links and References
- Twenty CRM API Documentation (general reference for API endpoints and data structures)
- n8n Documentation on Creating Custom Nodes