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 users to create multiple "Task Targets" in bulk via the Twenty API. It is useful when you need to add several task targets at once, streamlining workflows that involve batch creation of related tasks or objectives. For example, a project manager could use this node to quickly set up multiple task targets for a new project phase without creating each target individually.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much nested related object information is included in the response: - 0: Only the primary task target's information. - 1: The primary task target plus its directly related objects (no further nesting). - 2: The primary task target, its directly related objects, and their related objects. |
| Body | A JSON object representing the task targets to be created. This should contain the details of the task targets in the expected format by the API. |
Output
The node outputs JSON data representing the created task targets. The structure of the output JSON corresponds to the created objects returned by the API, including any nested related objects depending on the selected depth level. There is no binary data output from this operation.
Dependencies
- Requires an API key credential for authenticating with the Twenty API.
- The base URL for the API is configured dynamically from the provided credentials.
- The node sends requests with
AcceptandContent-Typeheaders set toapplication/json.
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 before execution.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key or token is correctly configured.
- API Response Errors: If the API returns errors due to invalid data or server issues, check the error message for details. Adjust the request body accordingly or retry later.
- Depth Parameter Misuse: Setting an unsupported depth value may result in unexpected responses or errors. Use only 0, 1, or 2 as specified.
Links and References
- Twenty API Documentation (general reference for API endpoints and data structures)
- n8n documentation on JSON input handling