TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node interacts with the "Blocklists" resource of the Twenty API to find duplicate blocklist entries. It allows users to submit data or IDs representing blocklist items and returns information about duplicates found within those inputs. This is useful in scenarios where you want to identify redundant or overlapping entries in your blocklists, helping maintain clean and efficient lists.

Practical examples include:

  • Checking a set of IP addresses or domains against existing blocklists to find duplicates.
  • Validating new blocklist entries before adding them to avoid redundancy.
  • Auditing blocklists for cleanup by identifying repeated entries.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response:
- 0: Only primary object info.
- 1: Primary object plus directly related objects.
- 2: Primary object, its related objects, and their related objects.
Data JSON array containing blocklist data objects to check for duplicates. The structure depends on the API's expected blocklist item format.
Ids JSON array of blocklist entry IDs to check for duplicates.

Output

The node outputs JSON data representing the duplicate blocklist entries found based on the input data or ids. The output includes the primary blocklist objects and, depending on the depth parameter, may also include related nested objects up to two levels deep.

If the API supports binary data (not indicated here), it would typically represent attachments or files related to blocklist entries, but this node primarily deals with JSON data.

Dependencies

  • Requires an API key credential for authenticating with the Twenty API.
  • The base URL for the API is configured via credentials.
  • The node uses the official OpenAPI specification bundled internally to build requests.

Troubleshooting

  • Invalid JSON in Data or Ids: Since data and ids are JSON inputs parsed at runtime, malformed JSON will cause errors. Ensure valid JSON formatting.
  • Authentication Errors: Missing or incorrect API credentials will result in authentication failures. Verify that the API key or token is correctly configured.
  • Depth Parameter Misuse: Using unsupported depth values outside 0, 1, or 2 may cause unexpected responses or errors.
  • Empty Input Arrays: Providing empty arrays for data or ids might return no results or errors; ensure inputs contain valid entries.

Links and References

Discussion