TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node allows updating a single automated trigger associated with a workflow in the TwentyDEV platform. Automated triggers enable workflows to start automatically based on specific events or schedules, such as database changes or cron schedules. This node is useful when you want to modify the configuration of an existing automated trigger, for example, changing its type, adjusting settings, or linking it to a different workflow.

Practical examples:

  • Changing a database event trigger to a cron trigger to run a workflow periodically.
  • Updating the settings of a cron trigger to change its schedule.
  • Modifying which workflow an automated trigger activates.

Properties

Name Meaning
Id The unique identifier of the automated trigger to update.
Depth Level of nested related objects to include in the response: 0 (only primary object), 1 (primary + directly related), 2 (primary + related + related of related).
Type The type of the automated trigger. Options: DATABASE EVENT, CRON.
Settings JSON object defining the settings for the automated trigger.
Workflow Id The ID of the workflow that this automated trigger will activate.

Output

The node outputs the updated automated trigger object in JSON format. The structure includes the primary trigger's details and, depending on the Depth property, may include nested related objects up to two levels deep. This output can be used downstream in the workflow for further processing or logging.

No binary data output is involved.

Dependencies

  • Requires an API key credential to authenticate requests to the TwentyDEV API.
  • The node uses the base URL provided by the credential's domain configuration.
  • No additional external dependencies are required beyond the TwentyDEV API access.

Troubleshooting

  • Invalid Id: If the provided Id does not correspond to an existing automated trigger, the API will likely return an error indicating the resource was not found. Verify the Id is correct.
  • Malformed JSON in Settings: The Settings property expects valid JSON. Invalid JSON syntax will cause parsing errors. Ensure the JSON is well-formed.
  • Unauthorized Access: Missing or invalid API credentials will result in authentication errors. Confirm that the API key credential is correctly configured.
  • Unsupported Type: Providing a Type value other than "DATABASE_EVENT" or "CRON" will cause the request to fail. Use only the supported options.
  • Workflow Id Issues: If the specified workflow ID does not exist or the user lacks permission, the update will fail. Verify the workflow ID and permissions.

Links and References

Discussion