TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation "Find Many Workflow Runs" allows you to retrieve multiple workflow run records from a system that tracks executions of workflows. It supports filtering, sorting, pagination, and controlling the depth of related nested data returned. This is useful when you want to analyze or monitor workflow executions in bulk, for example:

  • Fetching recent workflow runs sorted by start time.
  • Filtering runs by status or specific workflow IDs.
  • Paginating through large sets of workflow runs.
  • Including related objects such as execution details or user info up to two levels deep.

Practical examples include generating reports on workflow performance, auditing workflow executions, or integrating workflow run data into dashboards.

Properties

Name Meaning
Order By Sorts the returned workflow runs by specified fields. Format: field_name_1,field_name_2[DIRECTION_2],.... Directions can be AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. Default direction is AscNullsFirst. Example: createdAt,updatedAtDescNullsLast sorts by creation date ascending then update date descending.
Filter Filters the workflow runs based on field comparators and values. Format: field[COMPARATOR]:value. Supports comparators like eq, neq, in, containsAny, is, gt, gte, lt, lte, startsWith, like, ilike. Supports logical conjunctions or, and, not. Can filter nulls with field[is]:NULL or booleans with field[eq]:true. Example: status[eq]:success.
Limit Limits the number of workflow runs returned in one response. Default is 60.
Depth Controls how many levels of nested related objects are included in the response:
- 0: Only primary workflow run data.
- 1: Primary object plus directly related objects.
- 2: Primary object, its related objects, and their related objects.
Starting After Returns workflow runs starting after a specific cursor value, used for pagination. Cursor values come from startCursor or endCursor in the response's pageInfo.
Ending Before Returns workflow runs ending before a specific cursor value, also for pagination. Cursor values come from startCursor or endCursor in the response's pageInfo.

Output

The node outputs JSON data representing a collection of workflow run objects matching the query parameters. The structure includes:

  • An array of workflow run objects, each containing fields describing the run (e.g., ID, status, timestamps).
  • Nested related objects depending on the depth parameter.
  • Pagination information including cursors (startCursor, endCursor) and page info to support fetching additional pages.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential to authenticate requests against the Twenty API service.
  • The base URL for the API is configured via credentials.
  • No other external dependencies are required.

Troubleshooting

  • Empty results: Check your filter syntax and ensure the filter criteria match existing workflow runs.
  • Invalid filter or order_by format: Ensure filters and sort strings follow the documented syntax exactly, including correct comparator names and comma separation.
  • 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 very deep nested objects may increase response size and latency; try reducing depth if performance issues occur.

Links and References

Discussion