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 retrieve detailed information about a single task from the "Tasks" resource by specifying its unique identifier. It is useful when you need to fetch the full details of a specific task, including optionally related nested objects depending on the depth level chosen. For example, you might use this node to get the status and metadata of a particular task in a project management system or to display task details in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the task object you want to retrieve. |
| Depth | Determines how much related nested data to include in the response: - 0: Only the primary task information. - 1: Task plus directly related objects. - 2: Task, directly related objects, and their related objects (two levels deep). |
Output
The node outputs a JSON object representing the requested task. The structure includes the task's core properties such as id, title, description, status, and other metadata. Depending on the selected depth, the output may also contain nested related objects, such as subtasks, assigned users, or linked projects, up to two levels deep.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the external Twenty API service.
- The node uses the base URL configured in the credentials to send requests.
- No additional environment variables are needed beyond the API authentication setup.
Troubleshooting
Common issues:
- Providing an invalid or non-existent task Id will result in an error or empty response.
- Incorrect API credentials or missing authentication will cause authorization errors.
- Setting an unsupported depth value outside 0, 1, or 2 may lead to unexpected results or errors.
Error messages:
- "Task not found": Verify that the provided Id is correct and exists in the system.
- "Unauthorized" or "Authentication failed": Check that the API key credential is valid and properly configured.
- "Invalid parameter": Ensure the depth value is one of the allowed options (0, 1, or 2).
Links and References
- Twenty API Documentation (for detailed info on task objects and related resources)
- n8n documentation on Using API Credentials