TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Many Webhooks, retrieves multiple webhook objects from the connected service. It is useful when you want to list, filter, or paginate through webhooks that have been registered or created in your account or system.

Common scenarios include:

  • Displaying a list of all active webhooks for monitoring or management.
  • Filtering webhooks based on specific criteria such as ID, status, or creation date.
  • Paginating through large sets of webhooks to process or analyze them in batches.

For example, you might use this node to fetch all webhooks created after a certain date or to retrieve only those webhooks related to a particular event type.

Properties

Name Meaning
Order By Sorts the returned webhook objects by specified fields and directions. Format: field_name_1,field_name_2[DIRECTION_2],.... Directions can be AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. Default direction is AscNullsFirst. Example: createdAt, idDescNullsLast sorts by creation date ascending then by ID descending. Default is id.
Filter Filters the returned webhook objects using field comparators and values. Format: field[COMPARATOR]:value. Supports complex filters with conjunctions like and, or, not. Comparators include eq, neq, in, containsAny, is, gt, gte, lt, lte, startsWith, like, ilike. Can filter nulls (is:NULL) and booleans (eq:true). Default excludes a zero UUID ID.
Limit Limits the number of webhook objects returned in one response. Default is 60.
Depth Controls how many levels of nested related objects are included in the response:
- 0: Only primary webhook data.
- 1: Primary webhook plus directly related objects.
- 2: Primary webhook, directly related objects, and their related objects.
Default is 1.
Starting After Returns webhook objects starting after a specific cursor value, used for pagination. Cursor values come from startCursor or endCursor in the response's pageInfo.
Ending Before Returns webhook objects 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 containing an array of webhook objects matching the query parameters. Each webhook object includes its properties and potentially nested related objects depending on the Depth parameter.

The output typically contains:

  • A list/array of webhook records under a key (commonly something like data or similar).
  • Pagination information such as cursors (startCursor, endCursor) and page info to support fetching additional pages.
  • Nested related objects if requested via the Depth property.

If the API supports binary data for webhooks (e.g., payloads or logs), it would be included accordingly, but this operation primarily returns structured JSON data about webhooks.

Dependencies

  • Requires connection to the external 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.
  • No other external dependencies are indicated.

Troubleshooting

  • Empty results: Check your filter criteria; overly restrictive filters may return no webhooks.
  • Invalid filter syntax: Ensure filters follow the documented format with correct comparators and conjunctions.
  • Pagination issues: Use valid cursor values from previous responses for starting_after and ending_before.
  • Authentication errors: Verify that the API key or token is correctly configured and has sufficient permissions.
  • Rate limiting: If the API enforces rate limits, consider reducing request frequency or increasing the limit cautiously.

Links and References

Discussion