TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation updates a single "Message Channel Message Association" object in the connected service. It allows you to modify details about the association between messages and message channels, such as changing message identifiers, direction, or related thread information.

Common scenarios for this node include:

  • Correcting or updating message metadata after initial creation.
  • Synchronizing message associations when external messaging provider data changes.
  • Adjusting message direction or linking messages to different channels or threads.

For example, if a message was initially linked to the wrong channel or has an incorrect external ID, this node can update those fields to maintain accurate records.

Properties

Name Meaning
Id The unique identifier of the message channel message association object to update. This is required to specify which record to modify.
Depth Determines how much nested related object data to return in the response:
- 0: Only the primary object's info.
- 1: Primary object plus directly related objects.
- 2: Includes related objects of related objects.
Message External Id The message ID as provided by the external messaging provider. Useful for syncing or referencing the original message source.
Message Channel Id Identifier of the message channel associated with the message.
Message Id Internal or system-specific message identifier.
Direction The direction of the message relative to the system: either INCOMING or OUTGOING.
Message Thread External Id The thread ID from the external messaging provider, indicating the conversation thread the message belongs to.

Output

The node outputs the updated "Message Channel Message Association" object in JSON format. The output includes the updated fields and, depending on the Depth property, may also include nested related objects up to two levels deep.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key or authentication token configured in the node credentials to access the Twenty API.
  • The base URL and headers are set according to the credential domain and standard JSON content types.
  • The node depends on the external Twenty API service to perform the update operation.

Troubleshooting

  • Missing or invalid Id: Since the Id property is required, omitting it or providing an incorrect value will cause the update to fail. Ensure the correct object ID is supplied.
  • Invalid field values: Providing invalid values for properties like Direction (anything other than INCOMING or OUTGOING) may result in errors.
  • API authentication errors: If the API key or credentials are missing or invalid, the request will be rejected. Verify that credentials are correctly configured.
  • Network or service errors: Temporary network issues or downtime of the external API can cause failures. Retrying later or checking service status may help.
  • Depth parameter misuse: Setting an unsupported depth level might lead to unexpected responses or errors; use only 0, 1, or 2.

Links and References

Discussion