TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Many Timeline Activities, retrieves multiple timeline activity records from the Twenty API. It is useful for scenarios where you want to query and list timeline activities with flexible filtering, sorting, pagination, and control over the depth of related data included.

Practical examples include:

  • Fetching recent user activities on a platform sorted by date.
  • Filtering timeline activities based on specific criteria such as activity type or status.
  • Paginating through large sets of timeline activities using cursors.
  • Controlling how much related information (e.g., linked users or projects) is returned alongside each timeline activity.

Properties

Name Meaning
Order By Sorts the returned timeline activities. Accepts a comma-separated list of fields with optional directions. Directions can be: AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. Default direction is AscNullsFirst. Example: createdAt,updatedAtDescNullsLast
Filter Filters the timeline activities returned. Supports complex expressions combining fields, comparators, and conjunctions. Comparators include eq, neq, in, containsAny, is, gt, gte, lt, lte, startsWith, like, ilike. Can filter null values and booleans. Example: status[eq]:active,createdAt[gte]:2023-01-01
Limit Limits the number of timeline activities returned in one response. Default is 60.
Depth Controls the level of nested related objects included in the response: 0 = only primary timeline activity data; 1 = includes directly related objects; 2 = includes related objects of those related objects. Default is 1.
Starting After Returns timeline activities starting after a specific cursor value. Useful for paginating forward through results. Cursor values are found in the response's pageInfo object (startCursor or endCursor).
Ending Before Returns timeline activities ending before a specific cursor value. Useful for paginating backward through results. Cursor values are found in the response's pageInfo object (startCursor or endCursor).

Output

The node outputs JSON data representing the timeline activities matching the query parameters. The structure typically includes:

  • An array of timeline activity objects, each containing fields describing the activity.
  • Pagination info such as cursors (startCursor, endCursor) and flags indicating if more pages exist.
  • Nested related objects depending on the Depth parameter.

If binary data were involved (not indicated here), it would represent attachments or media related to timeline activities, but this operation focuses on JSON data.

Dependencies

  • Requires an API key credential for authenticating with the Twenty API.
  • The node uses the base URL configured via credentials.
  • No additional external dependencies beyond the Twenty API and its authentication.

Troubleshooting

  • Empty results: Check your filter syntax and ensure that the filter matches existing timeline activities. Also verify that the limit and pagination cursors are set correctly.
  • Invalid filter or order_by format: Ensure filters and order strings follow the documented syntax exactly, including correct comparator names and field names.
  • Authentication errors: Confirm that the API key credential is valid and has necessary permissions.
  • Pagination issues: When using starting_after or ending_before, use cursor values exactly as provided in previous responses to avoid errors.
  • Depth too high: Requesting a depth greater than supported may result in incomplete data or errors.

Links and References

Discussion