TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Many View Groups, retrieves multiple "View Group" objects from an external service via its 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 groups with specific criteria, order them, limit the number returned, or include related data.

Practical examples:

  • Fetching all view groups created after a certain date, sorted by name.
  • Retrieving a paginated list of view groups for display in a dashboard.
  • Getting detailed information about view groups including their related entities up to two levels deep.

Properties

Name Meaning
Order By Sorts the returned view groups by specified fields. Format: field_name_1,field_name_2[DIRECTION_2],.... Directions can be AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. Default direction is AscNullsFirst. Example: name,createdAtDescNullsLast
Filter Filters the returned view groups based on field conditions. Format: field[COMPARATOR]:value. 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 field[is]:NULL or boolean values with field[eq]:true. Example: status[eq]:active
Limit Limits the number of view groups returned. Default is 60.
Depth Controls how many levels of nested related objects are included in the response:
- 0: Only primary view group data
- 1: Primary view group + directly related objects
- 2: Primary view group + related objects + their related objects
Starting After Returns view groups starting after a specific cursor value (used for pagination). Cursor values come from startCursor or endCursor in the response's pageInfo.
Ending Before Returns view groups ending before a specific cursor value (used for pagination). Cursor values come from startCursor or endCursor in the response's pageInfo.

Output

The node outputs JSON data representing a collection of view group objects matching the query parameters. The structure typically includes:

  • An array of view group objects with their fields and optionally nested related objects depending on the Depth parameter.
  • Pagination info such as cursors (startCursor, endCursor) and page metadata to support fetching subsequent pages using Starting After and Ending Before.

If the API supports binary data for view groups (e.g., images or files), the node would output binary data accordingly, but this is not indicated here.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the external Twenty API.
  • The base URL and headers for requests are set from credentials.
  • Uses the bundled OpenAPI specification to build request properties and handle routing.

Troubleshooting

  • Empty results: Check your filter syntax and ensure the filter matches existing view groups.
  • Invalid filter or order_by format: Ensure filters and sort strings follow the documented syntax exactly, including correct comparator names and directions.
  • Pagination issues: Use valid cursor values from previous responses for Starting After and Ending Before.
  • Authentication errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
  • Depth too high: Requesting very deep nested objects may cause performance issues or timeouts; try reducing the depth.

Links and References

Discussion