TwentyDEVInstall

Overview

This node allows you to delete a specific Workflow Automated Trigger by its unique identifier. It is useful in scenarios where you need to programmatically remove triggers that automate workflows, for example, when cleaning up unused or obsolete automation rules or managing workflow lifecycle dynamically.

Practical examples include:

• Removing an outdated trigger after a workflow update.
• Deleting a trigger as part of a cleanup process in automated deployment pipelines.
• Managing triggers based on external events or conditions.

Properties

Output

The node outputs JSON data representing the result of the deletion operation. Typically, this will confirm whether the trigger was successfully deleted or provide details about the deletion status. There is no binary output expected from this operation.

Dependencies

• Requires an API key credential to authenticate with the external service managing workflow triggers.
• The node depends on the Twenty API (as indicated by the bundled source referencing "TwentyDEV" and its OpenAPI specification).
• Proper configuration of the API domain and authentication credentials within n8n is necessary.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent trigger ID will likely result in an error indicating the trigger could not be found.
  • Missing or incorrect API credentials will cause authentication failures.
  • Network connectivity problems can prevent the node from reaching the API endpoint.

• Error messages and resolutions:

  • "Trigger not found": Verify the provided Id is correct and exists.
  • "Authentication failed": Check that the API key credential is correctly configured and has sufficient permissions.
  • Timeout or network errors: Ensure stable internet connection and that the API endpoint is reachable.

Links and References

• Twenty API Documentation (for detailed API usage and authentication)
• n8n documentation on Using Credentials