TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Many Workflow Versions, retrieves multiple versions of workflows from a system that manages workflow versioning. It is useful when you want to list or query historical or current versions of workflows, for example, to audit changes, compare different versions, or restore a previous state.

Typical use cases include:

  • Fetching all versions of a specific workflow to display in a UI.
  • Filtering workflow versions by certain criteria such as creation date or status.
  • Paginating through large sets of workflow versions.
  • Sorting workflow versions by fields like ID or creation time.

Properties

Name Meaning
Order By Specifies the sorting order of the returned workflow versions. The value should be a comma-separated list of field names optionally followed by a direction modifier. Available directions are: AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. Default direction is AscNullsFirst. Example: id,createdAtDescNullsLast. Default is id.
Filter Filters the workflow versions returned based on field comparators and values. Supports complex expressions with conjunctions (and, or, not). Comparators include eq, neq, in, containsAny, is, gt, gte, lt, lte, startsWith, like, ilike. Can filter null values and booleans. Example: id[neq]:"00000000-0000-0000-0000-000000000000". Default excludes empty UUID.
Limit Limits the number of workflow versions returned in one response. Useful for pagination or controlling data volume. Default is 60.
Depth Controls how deeply nested related objects are included in the response: 0 = only primary object, 1 = primary plus directly related objects, 2 = includes related objects of related objects. Default is 1.
Starting After Returns workflow versions starting after a specific cursor value. Used for cursor-based pagination. Cursor values can be found in the response's pageInfo section (startCursor or endCursor).
Ending Before Returns workflow versions ending before a specific cursor value. Also used for cursor-based pagination.

Output

The node outputs JSON data representing a collection of workflow version objects. Each object contains details about a workflow version, potentially including nested related objects depending on the Depth parameter.

The output structure typically includes:

  • An array of workflow version records matching the query.
  • Pagination information such as cursors (startCursor, endCursor) and page info to support further paginated requests.

If binary data were involved (not indicated here), it would represent file attachments or similar, but this node focuses on JSON data.

Dependencies

  • Requires an API key credential to authenticate requests against the Twenty API service.
  • The base URL for the API is configured via credentials.
  • 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 comparator and conjunction syntax.
  • 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.
  • Rate limiting or network errors: Handle retries or backoff as needed; these are external to the node logic.

Links and References

Discussion