TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

The node interacts with the "Workflow Versions" resource to find duplicate workflow versions based on specified criteria. It allows users to specify filters and parameters to identify duplicates among workflow versions, which is useful for managing and cleaning up multiple versions of workflows in an automation environment.

Common scenarios include:

  • Identifying redundant or duplicate workflow versions to maintain a clean and efficient workflow repository.
  • Auditing workflow versions by status or name to ensure consistency.
  • Automating cleanup processes by detecting duplicates programmatically.

For example, a user might want to find all draft workflow versions that share the same name to decide which ones to archive or delete.

Properties

Name Meaning
Depth Determines how much related nested data to include in the response:
- 0: Only primary workflow version information.
- 1: Primary object plus directly related objects.
- 2: Includes related objects of related objects as well.
Data JSON array specifying filter criteria for workflow versions, e.g., status and name. Example:
json<br>[{"status": "DRAFT", "name": "Workflow Version name"}]<br>
Ids JSON array of workflow version IDs to limit the search scope. Example:
json<br>[null]<br> (can be replaced with specific IDs)

Output

The node outputs JSON data containing the found duplicate workflow versions according to the specified filters and depth level. The structure includes the primary workflow version objects and their related nested objects depending on the depth parameter.

If binary data were involved, it would typically represent attachments or files related to workflow versions, but this node focuses on JSON data only.

Dependencies

  • Requires an API key credential to authenticate requests to the external Twenty API service.
  • The node uses the Twenty API base URL configured via credentials.
  • No additional environment variables are explicitly required beyond standard API authentication.

Troubleshooting

  • Invalid JSON in Data or Ids properties: Since these fields expect JSON input, malformed JSON will cause errors. Ensure valid JSON syntax.
  • Authentication errors: If the API key or domain is misconfigured, the node will fail to connect. Verify credentials and endpoint settings.
  • No duplicates found: This may indicate that the filter criteria are too restrictive or incorrect. Try broadening the filters or checking the input data.
  • Depth parameter misuse: Setting depth too high may result in large responses or slow performance. Use appropriate depth levels based on needs.

Links and References

Discussion