TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation "Find Many Tasks" retrieves multiple task objects from an external service via its API. It is designed to query and return a list of tasks based on various filtering, sorting, pagination, and depth options. This operation is useful when you want to fetch a batch of tasks for processing, reporting, or integration purposes.

Typical use cases include:

  • Fetching all tasks assigned to a user or project with specific criteria.
  • Retrieving tasks updated after a certain date.
  • Paginating through large sets of tasks in batches.
  • Including related nested objects (like subtasks or linked entities) up to a specified depth.

Properties

Name Meaning
Order By Sorts the returned tasks by one or more fields. Format: field_name_1,field_name_2[DIRECTION_2],.... Directions can be AscNullsFirst, AscNullsLast, DescNullsFirst, or DescNullsLast. Default direction is AscNullsFirst. Example: created_at,priorityDescNullsLast
Filter Filters the tasks returned using field comparators. Format: field[COMPARATOR]:value. Supports complex filters with conjunctions (or, and, not). Comparators include eq, neq, in, containsAny, is, gt, gte, lt, lte, startsWith, like, ilike. Can filter null values and booleans. Example: status[eq]:open,priority[gte]:3
Limit Limits the number of tasks returned in one response. Default is 60. Useful for pagination or controlling data volume.
Depth Controls how many levels of nested related objects are included in each task's data. Options: 0 (only primary task info), 1 (task + directly related objects), 2 (task + related objects + their related objects). Helps control response size and detail level.
Starting After Returns tasks starting after a specific cursor value. Used for cursor-based pagination. Cursor values come from startCursor or endCursor in previous response's pageInfo.
Ending Before Returns tasks ending before a specific cursor value. Also used for cursor-based pagination.

Output

The node outputs JSON data containing an array of task objects matching the query parameters. Each task object includes fields as defined by the API, potentially including nested related objects depending on the Depth parameter.

If the API supports binary data for tasks (e.g., attachments), the node would output binary data accordingly, but this operation primarily returns structured JSON task data.

Dependencies

  • Requires an API key credential for authenticating with the external service.
  • The base URL for the API is configured via credentials.
  • The node uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Empty results: Check your filter criteria; overly restrictive filters may return no tasks.
  • Invalid filter syntax: Ensure filters follow the correct format with valid comparators and conjunctions.
  • Pagination issues: Use cursors correctly with Starting After and Ending Before properties to paginate through results.
  • API authentication errors: Verify that the API key credential is set up correctly and has necessary permissions.
  • Depth too high: Requesting too deep nested objects may cause slow responses or timeouts; try reducing the Depth value.

Links and References

Discussion