TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Many Workflow Automated Triggers, is designed to retrieve multiple workflow automated trigger objects from an external service via its API. It allows users to query and filter these triggers based on various criteria, control the sorting order, limit the number of results, and specify the depth of related nested objects included in the response.

Typical use cases include:

  • Fetching a list of all active or specific workflow automated triggers for monitoring or reporting.
  • Retrieving triggers filtered by certain fields such as ID, status, or other attributes.
  • Paginating through large sets of triggers using cursors.
  • Including related data about each trigger to understand their context or configuration.

For example, a user might want to get the first 60 workflow automated triggers sorted by their creation date, excluding any with a default or null ID, and including related objects one level deep.

Properties

Name Meaning
Order By Specifies how to sort the returned workflow automated triggers. The value should be a comma-separated list of field names optionally followed by a direction modifier. Available directions are: AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. If no direction is specified, AscNullsFirst is used by default. Example: createdAt,updatedAtDescNullsLast. Default is id.
Filter Filters the triggers returned based on field comparisons. Supports complex expressions combining multiple fields and comparators such as eq (equals), neq (not equals), in, containsAny, is (for null checks), gt (greater than), gte, lt, lte, startsWith, like, ilike. Logical conjunctions like and, or, not can be used. Example: status[eq]:active,id[neq]:"00000000-0000-0000-0000-000000000000".
Limit Limits the maximum number of workflow automated triggers returned in the response. Default is 60.
Depth Controls how many levels of nested related objects are included in the response:
- 0: Only primary trigger objects.
- 1: Primary triggers plus their directly related objects.
- 2: Primary triggers, their related objects, and those related objects' related objects. Default is 1.
Starting After Returns objects starting after a specific cursor value, useful for pagination. Cursor values can be found in the startCursor and endCursor fields of the pageInfo object in the response data.
Ending Before Returns objects ending before a specific cursor value, also for pagination purposes. Cursor values are found similarly in the response's pageInfo.

Output

The node outputs JSON data containing an array of workflow automated trigger objects matching the query parameters. Each object includes fields representing the trigger's properties and, depending on the Depth parameter, may include nested related objects up to two levels deep.

The output structure typically includes:

  • An array of trigger objects with their attributes.
  • Pagination information such as cursors (startCursor, endCursor) inside a pageInfo object to facilitate fetching subsequent pages.
  • No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential to authenticate requests to the external Twenty API service.
  • The node uses the base URL provided by the user's credentials configuration.
  • The node depends on the external Twenty API endpoint that supports querying workflow automated triggers with filtering, sorting, pagination, and depth options.

Troubleshooting

  • Common issues:

    • Incorrect filter syntax may cause the API to reject the request or return no results. Ensure filters follow the documented format and use valid comparators.
    • Using invalid cursor values for pagination (starting_after or ending_before) may result in empty responses or errors.
    • Exceeding the allowed limit or unsupported depth values could lead to API errors.
    • Missing or invalid API authentication credentials will prevent successful requests.

  • Error messages:

    • "Unauthorized" or "Authentication failed": Check that the API key credential is correctly configured and has necessary permissions.
    • "Invalid filter syntax": Review the filter string for correct comparator usage and formatting.
    • "Cursor not found": Verify that the cursor values used for pagination come from a valid previous response.
    • "Limit exceeds maximum allowed": Reduce the limit value to within acceptable bounds.

Links and References

Discussion