Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node allows you to create a new task in the connected system via the Twenty API. It is useful for automating task management workflows, such as adding tasks programmatically when certain triggers occur (e.g., new issue created, new customer onboarded). For example, you can use this node to automatically create a task assigned to a team member with a specific due date and status.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much nested related object data to include in the response: 0 = only primary task info, 1 = primary task plus directly related objects, 2 = primary task plus related objects and their related objects. |
| Body | The main content or description of the task. |
| Title | The title or name of the task. |
| Position | Numeric position of the task record, possibly used for ordering. |
| Assignee Id | Identifier of the user to whom the task is assigned. |
| Created By | JSON object describing the creator of the task record. |
| Status | Current status of the task. Options are: TODO, IN PROGRESS, DONE. |
| Due At | Due date/time for the task completion. |
| Body V 2 | Alternative or extended JSON format for the task body content. |
Output
The node outputs the created task's data as JSON. The output includes all fields returned by the API after creation, reflecting the task's properties and any related nested objects depending on the Depth parameter. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Twenty API.
- The base URL for the API is configured from credentials.
- The node uses the Twenty API v1.0.3 OpenAPI specification internally.
Troubleshooting
- Common issues:
- Invalid or missing required fields like
titleorbodymay cause the API to reject the request. - Incorrect JSON formatting in
Created ByorBody V 2fields will cause parsing errors. - Authentication failures if the API key credential is not set or invalid.
- Invalid or missing required fields like
- Error messages:
- "Unauthorized" or "Authentication failed": Check API key credential configuration.
- "Invalid JSON": Verify that JSON input fields are correctly formatted.
- "Missing required field": Ensure mandatory properties like
titleandbodyare provided.
Links and References
- Twenty API Documentation (assumed based on context)
- n8n documentation on creating custom nodes