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 specific Message Channel by its unique identifier. It is useful when you need to fetch data about a single message channel, including optionally nested related objects depending on the depth level specified. Typical use cases include displaying channel details in dashboards, integrating channel data into other workflows, or performing conditional logic based on channel attributes.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the Message Channel to retrieve. This is required to specify which channel to find. |
| Depth | Determines how much related object data to include in the response: - 0: Only the primary Message Channel data. - 1: Primary Message Channel plus directly related objects. - 2: Primary Message Channel, directly related objects, and their related objects (two levels deep). |
Output
The node outputs JSON data representing the requested Message Channel. The structure includes the primary channel's properties and, depending on the Depth parameter, nested related objects up to two levels deep. This allows flexible retrieval of associated data without additional requests.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Twenty API.
- The node uses the base URL configured via credentials.
- The node depends on the bundled OpenAPI specification for request construction.
Troubleshooting
- Missing or invalid Id: If the
Idproperty is empty or incorrect, the API will likely return an error indicating the resource was not found. Ensure the correct channel ID is provided. - Authentication errors: If the API key credential is missing or invalid, authentication failures will occur. Verify that the credential is correctly set up.
- Invalid Depth value: Although limited to 0, 1, or 2, providing an unsupported value might cause unexpected behavior. Use only the provided options.
- Network or API issues: Connectivity problems or API downtime can cause request failures. Check network access and API status.
Links and References
- Twenty API Documentation (general reference for the API)
- n8n documentation on Using Credentials
- n8n documentation on Working with APIs