Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node operation allows creating multiple workflow versions in bulk. It is useful when you need to programmatically generate several versions of a workflow, for example during automated deployment pipelines, version management, or batch updates of workflows in an environment.
Practical examples include:
- Creating draft versions of workflows with specific names before publishing.
- Automating the creation of multiple workflow versions with different configurations or statuses.
- Managing workflow lifecycle by generating versions in bulk for testing or staging environments.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much nested related data to include in the response: - 0: Only primary workflow version information. - 1: Primary object plus directly related objects. - 2: Includes related objects of related objects as well. |
| Body | JSON object representing the workflow version(s) to create. Typically includes fields like status (e.g., "DRAFT") and name (the workflow version name). This property accepts raw JSON input describing the workflow version details. |
Output
The node outputs JSON data representing the created workflow versions. The structure corresponds to the API response and includes the newly created workflow version objects along with any requested nested related objects depending on the Depth parameter.
No binary data output is indicated.
Dependencies
- Requires an API key credential to authenticate requests against the Twenty API service.
- The base URL for the API is configured via credentials.
- The node uses the Twenty API OpenAPI specification internally to build requests.
Troubleshooting
- Invalid JSON in Body: If the JSON provided in the Body property is malformed, the node will fail. Ensure valid JSON syntax.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
- Invalid Depth Value: Using a depth value outside the allowed range (0, 1, 2) may result in errors or unexpected responses.
- API Rate Limits or Quotas: Bulk creation might hit API limits; monitor usage and handle rate limiting accordingly.
Links and References
- Twenty API Documentation (general reference for the API)
- n8n documentation on working with JSON parameters
- Best practices for bulk operations in APIs