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 update a single Task Target object in the connected system via the Twenty API. It is useful when you need to modify details of an existing Task Target, such as linking it to different opportunities, companies, persons, or tasks.
Common scenarios include:
- Updating the association of a Task Target to a new Opportunity or Company.
- Changing the linked Person or Task for a specific Task Target.
- Adjusting the depth of related objects returned in the response to control the amount of nested data retrieved.
For example, if you have a Task Target that was initially linked to one company but needs to be reassigned to another, this node can perform that update seamlessly.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the Task Target object to update. This is required. |
| Depth | Determines how much nested related data to include in the response: 0 (only primary object), 1 (primary + directly related), 2 (primary + related + their related). |
| Opportunity Id | (Optional) The ID of the Opportunity to associate with the Task Target. |
| Company Id | (Optional) The ID of the Company to associate with the Task Target. |
| Person Id | (Optional) The ID of the Person to associate with the Task Target. |
| Task Id | (Optional) The ID of the Task to associate with the Task Target. |
Output
The node outputs a JSON object representing the updated Task Target. The structure includes the primary Task Target fields and, depending on the Depth parameter, may also include nested related objects up to two levels deep.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Twenty API service.
- Needs an API authentication token configured in the node credentials.
- The base URL for the API is set dynamically from the provided credentials.
Troubleshooting
- Missing or invalid Id: The node requires a valid Task Target Id to update. Ensure the Id is correct and exists in the system.
- Authentication errors: If the API key or token is missing or invalid, the request will fail. Verify your credentials are correctly set up.
- Invalid related object IDs: Providing non-existent Opportunity, Company, Person, or Task IDs may cause errors or no changes. Confirm these IDs exist before updating.
- Depth parameter misuse: Setting an unsupported depth value might result in unexpected responses. Use only 0, 1, or 2 as specified.
Links and References
- Twenty API Documentation (example placeholder link)
- n8n documentation on Creating Custom Nodes