TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation updates a single message folder in the connected service. It allows users to modify properties of an existing message folder by specifying its unique identifier and providing new values for fields such as the folder name, associated message channel, and sync cursor. This is useful in scenarios where you want to organize or rename message folders dynamically within workflows, for example, updating folder names based on external triggers or syncing folder states.

Properties

Name Meaning
Id The unique identifier of the message folder to update. This is required to specify which folder will be modified.
Depth Determines how much related nested data to include in the response:
- 0: Only the primary message folder object.
- 1: The folder plus its directly related objects.
- 2: Folder, its related objects, and their related objects.
Message Channel Id The ID of the message channel associated with this folder.
Name The new name to assign to the message folder.
Sync Cursor A string used for synchronization purposes, likely to track the state or version of the folder for syncing changes.

Output

The node outputs JSON data representing the updated message folder object. Depending on the Depth property, this JSON may include nested related objects up to two levels deep. The output reflects the current state of the folder after the update operation.

There is no indication that the node outputs binary data.

Dependencies

  • Requires an API key credential to authenticate requests to the Twenty API.
  • The base URL for API requests is configured from the user's credentials.
  • The node uses standard HTTP headers for JSON content type and accepts JSON responses.

Troubleshooting

  • Missing or invalid Id: If the Id property is not provided or incorrect, the update will fail because the target folder cannot be identified.
  • Invalid Depth value: Providing a depth outside the allowed range (0, 1, 2) might cause unexpected results or errors.
  • API authentication errors: Ensure the API key credential is correctly set up and has permissions to update message folders.
  • Network or connectivity issues: Failures in reaching the API endpoint will prevent updates; verify network access and base URL configuration.
  • Invalid field values: For example, setting an empty or invalid folder name might cause the API to reject the update.

Links and References

Discussion