TwentyDEV icon

TwentyDEV

Consume the Twenty API

Actions252

Overview

This node allows you to create a new workflow record in the target system via an API. It is useful for automating the creation and management of workflows programmatically, such as setting up new automation sequences or processes without manual intervention. For example, you might use this node to dynamically generate workflows based on user input or external events, ensuring consistent setup and version control.

Properties

Name Meaning
Depth Determines how much nested related data to include in the response:
- 0: Only primary workflow information.
- 1: Primary workflow plus directly related objects.
- 2: Includes related objects of related objects.
Last Published Version Id The identifier of the last published version of the workflow.
Name The name assigned to the new workflow.
Created By JSON object describing the creator of the workflow record.
Position Numeric value indicating the position or order of the workflow record.
Statuses JSON array representing the current statuses of the workflow versions.

Output

The node outputs JSON data representing the newly created workflow record, including any nested related objects depending on the Depth property. This output typically contains identifiers, metadata, and status information about the workflow. There is no indication that binary data is produced by this node.

Dependencies

  • Requires an API key credential to authenticate requests to the Twenty API.
  • The base URL for API requests is configured from the provided credentials.
  • The node uses the Twenty API OpenAPI specification internally to build request properties and handle communication.

Troubleshooting

  • Invalid or missing API credentials: Ensure that the API key and domain are correctly set in the node credentials.
  • Malformed JSON inputs: Properties like Created By and Statuses expect valid JSON strings; invalid JSON will cause errors.
  • Incorrect property values: For example, setting Depth outside the allowed options (0, 1, 2) may result in unexpected responses.
  • Network or API errors: Check connectivity and API availability if requests fail.
  • Empty required fields: Fields like Name should not be empty when creating a workflow.

Links and References

Discussion