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 creating multiple associations between messages and message channels in bulk. It is useful when you need to link several messages to their respective channels simultaneously, for example, syncing incoming or outgoing messages with specific communication channels in a messaging platform.
Practical scenarios include:
- Bulk importing message-channel relationships from an external system.
- Synchronizing message data after batch processing or migration.
- Automating the creation of message links during mass messaging campaigns.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related object information is included in the response: - 0: Only the primary object's information. - 1: Primary object plus directly related objects (no further nesting). - 2: Primary object, its related objects, and their related objects. |
| Body | JSON object representing the message data to be synced with a message channel. Example default includes a "direction" field set to "INCOMING". This body defines the details of the message associations being created. |
Output
The output contains a JSON structure representing the created message channel message associations. The depth property controls how nested the returned related objects are, allowing users to receive just the core association data or additional linked entities.
If binary data were involved, it would typically represent attachments or media linked to messages, but this node focuses on JSON data describing message associations.
Dependencies
- Requires an API key credential for authenticating requests to the Twenty API service.
- The node uses the Twenty API base URL configured via credentials.
- No other external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid JSON in the "Body" property can cause request failures. Ensure the JSON is well-formed.
- Incorrect or missing API credentials will result in authentication errors.
- Setting an unsupported depth value outside 0, 1, or 2 may lead to unexpected responses or errors.
Error messages:
- Authentication errors indicate invalid or missing API keys; verify credentials configuration.
- Validation errors on the body payload suggest malformed JSON or missing required fields; check the input format.
- Network or timeout errors may occur if the API endpoint is unreachable; confirm network connectivity and API availability.
Links and References
- Twenty API Documentation (general reference for the API endpoints)
- n8n documentation on Creating Custom Nodes