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 interacts with the Twenty API to retrieve detailed information about a single message thread by its unique identifier. It is useful when you want to fetch a specific conversation or discussion thread, including optionally nested related data such as messages within the thread or associated metadata.
Practical examples include:
- Displaying the full details of a particular message thread in a dashboard.
- Fetching conversation history for customer support or community management.
- Integrating message thread data into other workflows or systems for analysis or reporting.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the message thread to retrieve. |
| Depth | Determines how much related nested data to include: - 0: Only the primary message thread info. - 1: Primary thread plus directly related objects. - 2: Primary thread, directly related objects, and their related objects. |
Output
The node outputs JSON data representing the requested message thread. The structure includes the main thread's properties and, depending on the Depth parameter, may include nested related objects such as messages, participants, or other linked entities. No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Twenty API.
- The base URL for the API is configured via credentials.
- The node uses standard HTTP headers for JSON content negotiation.
Troubleshooting
- Missing or invalid Id: Ensure the
Idproperty is provided and correctly references an existing message thread. - Authentication errors: Verify that the API key credential is valid and has necessary permissions.
- Depth parameter misuse: Using a higher depth value may increase response size and latency; adjust according to needs.
- API connectivity issues: Check network access and correct base URL configuration in credentials.
Links and References
- Twenty API Documentation (hypothetical link for reference)
- n8n documentation on HTTP Request nodes and authentication