mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node operation updates an existing conversation in the mittwald mStudio API. It allows users to modify details of a conversation such as its category, related entity, and title by specifying the conversation's unique identifier. This is useful in scenarios where conversations need to be re-categorized, linked to different entities, or renamed after their creation.

Practical examples include:

  • Changing the category of a support ticket conversation to reflect updated issue classification.
  • Linking a conversation to a different customer or project after initial assignment.
  • Updating the conversation title to better summarize the discussion topic.

Properties

Name Meaning
Conversation Id The unique identifier of the conversation to update. This is required to specify which conversation to modify.
Category Id The identifier of the new category to assign to the conversation.
Related To An object representing the entity to which the conversation is related. This can include fields like aggregate, domain, and id to define the relationship.
Title The new title for the conversation.

Output

The node outputs JSON data representing the updated conversation object returned from the mittwald mStudio API. This typically includes the conversation's updated properties such as its ID, category, related entity, title, timestamps, and any other metadata provided by the API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the mittwald mStudio API.
  • The node uses the base URL https://api.mittwald.de and expects JSON content-type headers.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Missing or invalid Conversation Id: The operation requires a valid conversation ID. Ensure this property is set and corresponds to an existing conversation.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Invalid Category Id or Related To object: Providing incorrect or malformed values may cause the API to reject the update. Validate these inputs before execution.
  • Network or connectivity issues: Confirm that n8n can reach the mittwald API endpoint without firewall or proxy restrictions.

Common error messages will likely relate to HTTP status codes such as 400 (bad request), 401 (unauthorized), or 404 (not found). Resolving them involves checking input correctness and credential validity.

Links and References

Discussion