TwentyDEV icon

TwentyDEV

Consume the Twenty API

Actions252

Overview

This node allows you to retrieve detailed information about a single Workflow Automated Trigger by its unique identifier. It is useful when you need to fetch specific trigger configurations or metadata within an automation workflow system. For example, you might use this node to verify the settings of a particular automated trigger before performing further actions or to audit trigger details programmatically.

Properties

Name Meaning
Id The unique identifier of the Workflow Automated Trigger object you want to find. This is required.
Depth Determines how much related nested data to include in the response:
- 0: Only the primary trigger's information.
- 1: Primary trigger plus directly related objects (no further nesting).
- 2: Primary trigger, its related objects, and their related objects (two levels of nesting).

Output

The node outputs a JSON object representing the Workflow Automated Trigger identified by the provided Id. Depending on the selected Depth, this output includes:

  • The main trigger's properties.
  • Optionally, related objects such as linked workflows or conditions, with nesting depth controlled by the Depth property.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing Workflow Automated Triggers.
  • The node uses a base URL configured via credentials to connect to the relevant API endpoint.
  • No additional environment variables are needed beyond standard API authentication setup.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Id will result in an error indicating the object was not found.
    • Insufficient permissions or incorrect API credentials may cause authentication failures.
    • Setting an unsupported Depth value outside 0, 1, or 2 could lead to unexpected responses or errors.
  • Error messages and resolutions:

    • "Object not found": Verify that the Id is correct and exists in the system.
    • "Authentication failed": Check that the API key credential is valid and properly configured.
    • "Invalid parameter 'depth'": Ensure Depth is set to one of the allowed values (0, 1, or 2).

Links and References

  • Refer to the official API documentation of the Workflow Automation platform for detailed schema and examples of Workflow Automated Triggers.
  • Consult n8n documentation on setting up API credentials and using HTTP request nodes for similar integrations.

Discussion