TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation "Find Many Calendar Channels" retrieves multiple calendar channel objects from an external service. It is useful when you want to list or query calendar channels with various filtering, sorting, and pagination options. For example, you might use it to fetch all calendar channels that meet certain criteria, such as those created after a specific date or sorted by their ID.

Properties

Name Meaning
Order By Sorts the returned calendar channels. You specify fields to sort by, optionally with directions: AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. Default direction is AscNullsFirst. Example: id or name[DescNullsLast].
Filter Filters the calendar channels returned based on field comparisons. 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). Can filter null values and booleans. Example: id[neq]:"00000000-0000-0000-0000-000000000000" to exclude empty IDs.
Limit Limits the number of calendar channels returned. Default is 60.
Depth Controls how much nested related data to include: 0 = only primary calendar channel info; 1 = includes directly related objects; 2 = includes related objects of related objects. Default is 1.
Starting After Returns calendar channels starting after a specific cursor value, used for pagination. Cursor values come from response pageInfo fields startCursor and endCursor.
Ending Before Returns calendar channels ending before a specific cursor value, also for pagination. Cursor values come from response pageInfo fields startCursor and endCursor.

Output

The output JSON contains an array of calendar channel objects matching the query parameters. Each object includes the calendar channel's properties and, depending on the depth parameter, may include nested related objects. The structure reflects the requested depth of nested data.

If pagination is used, the output also includes 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 for authenticating requests to the external Twenty API.
  • The node uses the base URL configured via credentials.
  • No additional environment variables are specified.

Troubleshooting

  • Empty results: Check your filter syntax and ensure the filter does not exclude all records (e.g., the default filter excludes a zero UUID).
  • Invalid filter or order_by format: Ensure filters and order strings follow the documented syntax and comparator names exactly.
  • 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 up and has necessary permissions.
  • Depth too high: Requesting a depth greater than supported by the API may cause errors or incomplete data.

Links and References

Discussion