TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation "Find Many Note Targets" retrieves multiple note target objects from the connected service. It supports filtering, sorting, pagination, and controlling the depth of nested related objects included in the response. This is useful when you want to query a list of note targets with specific criteria, such as filtering by fields, ordering results, limiting the number of returned items, or fetching related data up to a certain nesting level.

Practical examples:

  • Fetching all note targets created after a certain date, ordered by creation time.
  • Retrieving a paginated list of note targets with filters applied on status or type.
  • Getting note targets along with their directly related objects for richer context.

Properties

Name Meaning
Order By Sorts the returned note targets. Accepts a comma-separated list of field names optionally followed by a direction. Directions can be: AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. Default direction is AscNullsFirst. Example: createdAt,updatedAtDescNullsLast
Filter Filters the returned note targets based on field comparators and values. Supports comparators like eq, neq, in, containsAny, is, gt, gte, lt, lte, startsWith, like, ilike. Complex filters can be built using conjunctions (or, and, not). Null and boolean filtering supported. Example: status[eq]:active,priority[gte]:3
Limit Limits the maximum number of note targets returned in one request. Default is 60.
Depth Controls how many levels of nested related objects are included in the response: 0 = only primary note target info; 1 = primary plus directly related objects; 2 = primary, directly related, and related objects of those related objects. Default is 1.
Starting After Returns note targets starting after a specific cursor value, used for pagination. Cursor values come from startCursor or endCursor in the response's pageInfo.
Ending Before Returns note targets ending before a specific cursor value, also used for pagination. Cursor values come from startCursor or endCursor in the response's pageInfo.

Output

The node outputs JSON data containing an array of note target objects matching the query parameters. Each object includes fields of the note target and, depending on the Depth parameter, may include nested related objects up to two levels deep.

If pagination is used, the output also contains pageInfo with cursors (startCursor, endCursor) to facilitate fetching subsequent or previous pages.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the Twenty API.
  • The base URL for the API is set dynamically from credentials.
  • The node depends on the external Twenty API service to fetch note target data.

Troubleshooting

  • Invalid filter syntax: If the filter string is malformed or uses unsupported comparators, the API may return errors. Ensure filters follow the documented format and use valid comparator keywords.
  • Pagination cursors missing or invalid: Using starting_after or ending_before with incorrect cursor values will cause no results or errors. Use cursors exactly as provided in the previous response's pageInfo.
  • Authentication errors: Missing or invalid API credentials will prevent data retrieval. Verify that the API key or token is correctly configured in n8n credentials.
  • Exceeding limit: Setting a very high limit might cause performance issues or API rejections. Use reasonable limits and paginate results if needed.
  • Depth too high: Requesting a depth beyond supported levels may result in incomplete data or errors. Only 0, 1, or 2 are valid.

Links and References

  • Twenty API Documentation (generic placeholder link)
  • Pagination concepts: cursors, startCursor, endCursor
  • Filtering syntax and comparator reference in API docs

Discussion