TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation "Find Many Message Channel Message Associations" retrieves multiple message channel message association objects from the Twenty API. It is useful for scenarios where you want to query and list associations between messages and channels, such as fetching all message-channel links with filtering, sorting, and pagination support.

Practical examples include:

  • Listing all message associations in a specific order.
  • Filtering associations by certain criteria (e.g., IDs not equal to a default null UUID).
  • Paginating through large sets of message associations using cursors.
  • Controlling the depth of related nested objects returned for richer data context.

Properties

Name Meaning
Order By Sorts the returned objects by specified fields. Format: field_name_1,field_name_2[DIRECTION_2],.... Directions can be AscNullsFirst, AscNullsLast, DescNullsFirst, or DescNullsLast. Default direction is AscNullsFirst. Example: id,createdAtDescNullsLast
Filter Filters the returned objects based on field comparators. Format: field[COMPARATOR]:value,.... Comparators include 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 also supported.
Limit Limits the number of objects returned in one response. Default is 60.
Depth Controls how many levels of nested related objects are included in the response:
- 0: Only primary object info
- 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 paginating forward. Cursor values come from startCursor or endCursor in response's pageInfo.
Ending Before Returns objects ending before a specific cursor value. Useful for paginating backward. Cursor values come from startCursor or endCursor in response's pageInfo.

Output

The node outputs JSON data representing a collection of message channel message association objects matching the query parameters. The structure includes:

  • An array of association objects with their fields and optionally nested related objects depending on the depth parameter.
  • Pagination information including cursors (startCursor, endCursor) within a pageInfo object to facilitate further paging.
  • 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.
  • The node uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Empty results: Check your filter criteria; overly restrictive filters may return no data.
  • Invalid filter syntax: Ensure filter strings follow the documented format with correct comparators and conjunctions.
  • Pagination errors: Use valid cursor values obtained from previous responses when using starting_after or ending_before.
  • API authentication failures: Verify that the API key credential is correctly set up and has necessary permissions.
  • Depth too high: Requesting very deep nested objects may increase response size and latency; adjust depth accordingly.

Links and References

Discussion