TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation "Find Many Connected Accounts" retrieves multiple connected account records from an external service via its API. It supports filtering, sorting, pagination, and controlling the depth of nested related objects returned in the response.

Typical use cases include:

  • Listing all connected accounts with specific criteria (e.g., filtering out placeholder or invalid IDs).
  • Fetching connected accounts sorted by certain fields.
  • Paginating through large sets of connected accounts using cursors.
  • Controlling how much related data is included for each connected account to optimize performance or detail level.

For example, you might use this node to get a list of active connected accounts ordered by creation date, limited to 50 results per request, including their immediate related objects but not deeper nested relations.

Properties

Name Meaning
Order By Sorts the returned connected accounts. Format: field_name_1,field_name_2[DIRECTION_2],.... Directions can be AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. Default direction is AscNullsFirst. Example: createdAt,usernameDescNullsLast sorts first by creation date ascending, then username descending with nulls last.
Filter Filters the connected accounts returned. Format: field[COMPARATOR]:value pairs separated by commas. Supports comparators like eq, neq, in, containsAny, is, gt, gte, lt, lte, startsWith, like, ilike. Logical conjunctions or, and, not can be used for complex filters. Example: id[neq]:"00000000-0000-0000-0000-000000000000" excludes empty UUIDs.
Limit Limits the number of connected accounts returned in one response. Default is 60.
Depth Controls how many levels of nested related objects are included: 0 returns only primary connected account info; 1 includes directly related objects; 2 includes related objects of those related objects as well. Default is 1.
Starting After Returns connected accounts starting after a specific cursor value. Useful for paginating forward. Cursor values come from startCursor or endCursor in the response's pageInfo.
Ending Before Returns connected accounts ending before a specific cursor value. Useful for paginating backward. Cursor values come from startCursor or endCursor in the response's pageInfo.

Output

The node outputs JSON data representing a paginated list of connected accounts matching the query parameters. The structure typically includes:

  • An array of connected account objects, each containing fields as defined by the API schema.
  • Pagination information (pageInfo) with cursors (startCursor, endCursor) to support fetching subsequent or previous pages.
  • Nested related objects according to the specified depth.

If binary data were involved, it would be summarized here, but this operation deals with JSON data only.

Dependencies

  • Requires an API key credential for authenticating requests to the external Twenty API service.
  • The base URL and authentication headers are configured via node credentials.
  • No additional environment variables are indicated.

Troubleshooting

  • Empty Results: If no connected accounts are returned, verify your filter syntax and values. Ensure that the filter does not exclude all records unintentionally.
  • Invalid Cursor Errors: When using starting_after or ending_before, ensure the cursor values come exactly from the previous response's pageInfo. Using outdated or malformed cursors will cause errors.
  • Sorting Issues: Incorrect order_by format or unsupported field names may result in API errors or ignored sorting.
  • Depth Too High: Setting depth to 2 may increase response size significantly and slow down the request. Use lower depth if performance is a concern.
  • Authentication Failures: Confirm that the API key credential is valid and has necessary permissions.

Links and References

Discussion