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 you to create multiple workflow runs in bulk via the "Create Many Workflow Runs" operation. It is useful when you need to programmatically start several instances of workflows with specific configurations or statuses at once, rather than triggering them individually. For example, you might use this node to initiate batch processing jobs, automate testing scenarios by running workflows multiple times, or schedule multiple workflow executions with different parameters.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested data is included in the response: - 0: Only the primary workflow run object. - 1: The primary object plus its directly related objects. - 2: Includes related objects of those related objects as well. |
| Body | JSON object representing the workflow run(s) to create. Example default includes: - status: Status of the workflow run (e.g., "NOT_STARTED").- name: Name assigned to the workflow run. You can customize this JSON to specify other properties of the workflow run. |
Output
The node outputs JSON data representing the created workflow runs. The structure corresponds to the API response and includes the workflow run details according to the specified depth level. This may include nested related objects depending on the depth setting. There is no binary output.
Dependencies
- Requires an API key credential for authenticating with the external Twenty API service.
- The node uses a base URL configured from credentials.
- The request headers expect JSON content type and accept JSON responses.
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 incorrect API credentials will cause authentication failures. Verify that the API key and domain are correctly set in the node credentials.
- API Limits or Permissions: Creating many workflow runs at once may hit API rate limits or require specific permissions. Check your API plan and user rights.
- Depth Parameter Misuse: Setting an unsupported depth value could lead to unexpected responses or errors. Use only 0, 1, or 2 as defined.
Links and References
- Twenty API Documentation (general reference for the API endpoints)
- n8n Documentation on Creating Workflow Runs (if available)