TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node allows users to create multiple workflow automated triggers in bulk. Workflow automated triggers are configurations that automatically initiate workflows based on specific events or conditions. This node is useful when you want to programmatically set up many such triggers at once, for example, when onboarding new projects or environments, or when migrating existing trigger setups.

Practical examples include:

  • Creating database event triggers that start workflows whenever certain changes occur in a database.
  • Setting up multiple webhook-based triggers simultaneously to listen for various external events.
  • Automating the deployment of workflow triggers across different environments with consistent settings.

Properties

Name Meaning
Depth Determines how much related nested information is included in the response:
- 0: Only the primary trigger object.
- 1: Primary object plus its directly related objects.
- 2: Primary object, its related objects, and their related objects.
Body The JSON definition of the workflow automated triggers to create. It must specify the trigger type (e.g., DATABASE_EVENT) and any relevant settings for each trigger.

Output

The node outputs JSON data representing the created workflow automated triggers. The structure includes the details of each trigger as returned by the API, potentially including nested related objects depending on the selected depth level.

If binary data were involved (not indicated here), it would typically represent files or attachments related to the triggers, but this node focuses on JSON data only.

Dependencies

  • Requires an API key credential to authenticate requests to the external service managing workflow automated triggers.
  • The node uses a base URL configured via credentials to send HTTP requests.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Invalid JSON in Body: If the JSON provided in the "Body" property is malformed, the node will fail to parse it. Ensure the JSON syntax is correct.
  • Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Verify that the API key or token is valid and properly configured.
  • Depth Parameter Misuse: Providing an unsupported depth value may result in unexpected responses or errors. Use only 0, 1, or 2 as specified.
  • API Limitations: Creating too many triggers at once might hit rate limits or payload size restrictions imposed by the API. Consider batching requests if necessary.

Links and References

Discussion