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 updates a single message thread in the connected service. It is useful when you need to modify or refresh details of an existing message thread by specifying its unique identifier. Common scenarios include updating thread metadata, changing thread status, or refreshing related nested data.
For example, you might use this node to update the properties of a conversation thread after receiving new information or to adjust how much related data is returned with the thread.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the message thread to update. |
| Depth | Determines how much nested related data to include in the response: - 0: Only the primary object. - 1: Primary object plus directly related objects. - 2: Primary object, directly related objects, and their related objects. |
Output
The output JSON contains the updated message thread object. Depending on the Depth property, this object may include nested related objects up to two levels deep. This allows you to receive detailed information about the thread and its relationships in one response.
If the node supports binary data (not indicated here), it would typically represent attachments or media related to the message thread, but no such binary output is evident from the provided code.
Dependencies
- Requires an API key credential for authenticating requests to the external Twenty API service.
- The base URL for API requests is configured via credentials.
- The node uses OpenAPI specifications bundled internally to define request structure and parameters.
Troubleshooting
- Missing or invalid Id: Ensure the
Idproperty is provided and corresponds to an existing message thread; otherwise, the update will fail. - Invalid Depth value: Use only the allowed options (0, 1, or 2) to avoid unexpected responses or errors.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or API errors: Check connectivity and API availability; inspect error messages for rate limits or permission issues.
Links and References
- Twenty API Documentation (example placeholder link)
- n8n documentation on creating custom nodes