Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node operation, Find Many Message Channels, retrieves multiple message channel objects from the connected service. It is useful when you want to list or search through message channels with various filtering, sorting, and pagination options.
Typical use cases include:
- Fetching a list of all available message channels for display or further processing.
- Searching for message channels that meet specific criteria (e.g., by name, status).
- Paginating through large sets of message channels in batches.
- Controlling the depth of related data included in the response to optimize performance or detail level.
For example, you might use this node to get the first 60 message channels sorted by their ID, excluding any default or placeholder channels, and including related objects one level deep.
Properties
| Name | Meaning |
|---|---|
| Order By | Sorts the returned message channels. The value should be a comma-separated list of field names optionally followed by a direction modifier. Directions can be: AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. If no direction is specified, AscNullsFirst is used by default. Example: id,createdAtDescNullsLast. Default is id. |
| Filter | Filters the message channels returned based on field comparators and values. Supports complex expressions using conjunctions (and, or, not). Comparators include eq, neq, in, containsAny, is, gt, gte, lt, lte, startsWith, like, ilike. You can filter nested fields using dot notation. For example, name[like]:test or status[eq]:active. Default excludes channels with id "00000000-0000-0000-0000-000000000000". |
| Limit | Limits the number of message channels returned in one request. Default is 60. |
| Depth | Controls how many levels of nested related objects are included in the response: - 0: Only primary message channel data. - 1: Primary data plus directly related objects. - 2: Primary data, directly related objects, and their related objects. Default is 1. |
| Starting After | Returns message channels starting after a specific cursor value. Useful for pagination. Cursor values can be found in the startCursor or endCursor fields of the pageInfo object in the response. |
| Ending Before | Returns message channels ending before a specific cursor value. Also used for pagination. Cursor values come from startCursor or endCursor in the response's pageInfo. |
Output
The node outputs JSON data containing an array of message channel objects matching the query parameters. Each object includes the fields of the message channel and, depending on the Depth parameter, may include nested related objects up to two levels deep.
Additionally, the output includes pagination information such as cursors (startCursor, endCursor) within a pageInfo object, which can be used to paginate through results using the Starting After and Ending Before input properties.
If the API supports binary data related to message channels (e.g., images or files), it would be included in the binary output; however, based on the provided code and properties, this node primarily returns JSON data.
Dependencies
- Requires connection to the Twenty API service.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- The base URL for the API is set dynamically from credentials.
- Uses standard HTTP headers for JSON content negotiation.
Troubleshooting
- Empty Results: If no message channels are returned, verify your filter syntax and values. Ensure the filter does not exclude all records unintentionally.
- Invalid Filter or Order By Syntax: Errors may occur if the filter or order by strings are malformed. Double-check comparator names, field names, and overall format.
- Pagination Issues: Using invalid or expired cursor values in
Starting AfterorEnding Beforecan cause errors or empty responses. Use cursors directly from previous responses. - Authentication Errors: Ensure the API key or token is valid and has sufficient permissions.
- Depth Parameter Impact: Setting depth too high may increase response size and latency. Adjust according to needs.
Links and References
- Twenty API Documentation (Assumed official docs for the API)
- Pagination concepts: https://graphql.org/learn/pagination/
- Filtering syntax examples (based on property descriptions)