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 allows users to create multiple workflows in bulk via an API. It is useful when you need to programmatically set up several workflows at once, for example during initial project setup or migration from another system. Instead of creating workflows one by one manually, this node streamlines the process by accepting an array of workflow definitions and sending them in a single request.
Practical examples:
- Automating the creation of standardized workflows for different teams.
- Migrating existing workflows from another platform into n8n.
- Bulk updating or cloning workflows with predefined configurations.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested data to include in the response: - 0: Only primary workflow information. - 1: Primary workflow plus directly related objects. - 2: Primary workflow, related objects, and their related objects. |
| Body | JSON defining the workflows to create. Typically includes properties like name (workflow name) and statuses (array of statuses such as "DRAFT"). This should be a valid JSON string representing one or more workflows. |
Output
The node outputs JSON data representing the created workflows. The structure corresponds to the API response and includes the workflows' details according to the specified Depth level. This may include nested related objects depending on the depth chosen.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Twenty API service.
- The base URL for the API is configured dynamically from credentials.
- The node uses the Twenty API v1.0.3 OpenAPI specification internally.
Troubleshooting
- Invalid JSON in Body: If the JSON provided in the Body property is malformed, the node will fail. Ensure the JSON syntax is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
- API Limits or Permissions: Creating many workflows at once might hit API rate limits or permission restrictions. Check API quotas and user permissions.
- Incorrect Depth Value: Using unsupported depth values may result in unexpected responses or errors. Use only 0, 1, or 2 as defined.
Links and References
- Twenty API Documentation (general reference for the API used)
- OpenAPI Specification (for understanding the API schema)