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 you to create multiple tasks at once in the "Tasks" resource of the connected service. It is useful when you need to batch-create several tasks programmatically, for example, importing a list of tasks from another system or generating tasks based on some automated workflow logic.
A practical example would be creating a set of TODO items with predefined statuses and details in one API call, rather than creating each task individually, which improves efficiency and reduces the number of requests.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested information is included in the response: - 0: Only the primary task object. - 1: The primary task plus its directly related objects. - 2: The primary task, its related objects, and their related objects. |
| Body | JSON object representing the task(s) to create. This should include the task details such as status, description, etc. Example default is { "status": "TODO" }. |
Output
The output contains a JSON field representing the created task objects. Depending on the Depth property, this JSON will include varying levels of nested related objects associated with each task.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential to authenticate with the external Twenty API service.
- The base URL for API requests is configured dynamically from credentials.
- The node uses the Twenty API version 1.0.3 OpenAPI specification for request construction.
Troubleshooting
- Invalid JSON in Body: If the JSON provided in the Body property is malformed, the node will fail to parse it. Ensure valid JSON syntax.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key credential is correctly configured.
- API Limits or Quotas: Creating many tasks at once may hit rate limits or payload size restrictions imposed by the API. Consider batching smaller groups if errors occur.
- Incorrect Depth Value: Using unsupported depth values might result in unexpected responses or errors. Use only 0, 1, or 2 as specified.
Links and References
- Twenty API Documentation (general reference for the API used)
- OpenAPI Specification (for understanding the API schema)