TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Workflow Automated Trigger Duplicates, is designed to identify duplicate automated triggers within workflows. It helps users detect if there are any overlapping or redundant triggers configured in their workflow automation setup. This can be particularly useful for maintaining clean and efficient workflows by avoiding multiple triggers that perform the same or similar actions.

Common scenarios include:

  • Auditing existing workflow triggers to ensure no duplicates exist.
  • Cleaning up workflow configurations before deployment.
  • Debugging unexpected behavior caused by multiple triggers firing simultaneously.

For example, a user might want to check if multiple database event triggers with identical settings are present, which could cause duplicated workflow executions.

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 describing the trigger types and their specific settings to search for duplicates. For example, an entry might specify a trigger type like DATABASE_EVENT along with its configuration details.
Ids JSON array of IDs to filter the search scope. Can be used to limit the duplicate search to specific trigger IDs or include null values as placeholders.

Output

The output is a JSON structure containing the found duplicate workflow automated triggers. The exact structure depends on the API response but generally includes:

  • Details of each detected duplicate trigger.
  • Nested related objects depending on the Depth parameter.
  • Metadata about the triggers such as type, settings, and identifiers.

No binary data output is expected from this operation.

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.
  • The node relies on the @devlikeapro/n8n-openapi-node package and a bundled OpenAPI specification (twenty-v1.0.3-openapi.json) to build request properties and handle communication.

Troubleshooting

  • Invalid JSON in Data or Ids: Since Data and Ids expect JSON input, malformed JSON will cause errors. Ensure valid JSON syntax when entering these fields.
  • Authentication Errors: Missing or incorrect API credentials will result in authentication failures. Verify that the API key credential is correctly set up.
  • Empty or No Results: If no duplicates are found, the output may be empty. Confirm that the Data and Ids parameters accurately reflect the triggers you want to check.
  • Depth Parameter Misuse: Setting an unsupported depth level (outside 0-2) may cause unexpected results or errors. Use only the provided options.

Links and References

Discussion