TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation "Find Many View Fields" retrieves multiple view field objects from the Twenty API. 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 view fields with specific criteria, order them, limit the number of results, or include related data up to a certain nesting level.

Practical examples:

  • Fetching all view fields sorted by creation date descending.
  • Retrieving view fields that match certain filter conditions, such as excluding a default or empty ID.
  • Paginating through large sets of view fields using cursors.
  • Including related objects (like linked entities) up to two levels deep for richer context.

Properties

Name Meaning
Order By Sorts the returned objects. Format: field_name_1,field_name_2[DIRECTION_2],.... Directions can be AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. Default direction is AscNullsFirst. Example: id,createdAtDescNullsLast
Filter Filters the returned objects. Format: field[COMPARATOR]:value pairs separated by commas. Supports comparators like eq, neq, in, containsAny, is, gt, gte, lt, lte, startsWith, like, ilike. Supports logical conjunctions or, and, not. Can filter null values with is:NULL or is:NOT_NULL. Boolean filters supported. Example: id[neq]:"00000000-0000-0000-0000-000000000000"
Limit Limits the number of objects returned. Default is 60.
Depth Controls how many levels of nested related objects are included in the response:
- 0: Only primary object
- 1: Primary object + directly related objects
- 2: Primary object + related objects + their related objects
Starting After Returns objects starting after a specific cursor value. Useful for pagination. Cursor values come from startCursor or endCursor in the response's pageInfo.
Ending Before Returns objects ending before a specific cursor value. Useful for reverse pagination. Cursor values come from startCursor or endCursor in the response's pageInfo.

Output

The node outputs JSON data representing a paginated list of view field objects matching the query parameters. The structure typically includes:

  • An array of view field objects with their properties.
  • Pagination info including cursors (startCursor, endCursor) and flags indicating if more pages exist.
  • Nested related objects up to the specified depth level.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Twenty API.
  • The base URL for the API is configured via credentials.
  • No additional external dependencies beyond the Twenty API and its authentication.

Troubleshooting

  • Empty results: Check your filter syntax and values; ensure they match existing data.
  • Invalid filter or order_by format: Ensure correct syntax and valid field names/directions as per documentation.
  • Pagination issues: Use valid cursor values from previous responses for starting_after and ending_before.
  • Authentication errors: Verify that the API key credential is correctly set and has necessary permissions.
  • Depth too high: Requesting very deep nested objects may cause performance issues or timeouts.

Links and References

Discussion