CT Coach Dev icon

CT Coach Dev

Interact with HttpBin API

Message → Update Message Translation

AI-generated

Overview

This node interacts with the Coach API to update the translation of a specific message. It is useful in scenarios where messages managed by the Coach platform need to be localized or updated with new translations dynamically. For example, if you have a multilingual coaching application and want to update the translated text of a message without altering the original message content, this operation allows you to do so programmatically.

Properties

Name Meaning
Authentication Choose between two authentication methods: "Company Api" or "System Api".
Message ID The unique identifier of the message whose translation you want to update (required).
Message Translation The new translation text for the specified message (required).
Message (Optional) The original message text to update alongside the translation.

Output

The node outputs a JSON object representing the response from the Coach API after attempting to update the message translation. This typically includes confirmation of the update or details about the updated message. The output does not include binary data.

Example output structure:

{
  "success": true,
  "message_id": "string",
  "updated_translation": "string",
  "original_message": "string"
}

(Note: Actual fields depend on the API response.)

Dependencies

  • Requires an API key credential for authentication, either via "Company Api" or "System Api".
  • Makes HTTP POST requests to the Coach API endpoint https://coachtriggerapp.com/crmApi/message/update.
  • The node expects proper configuration of credentials within n8n to authenticate these requests.

Troubleshooting

  • Authentication errors: Ensure that the correct API key credential is selected and properly configured.
  • Invalid Message ID: If the message ID does not exist or is incorrect, the API may return an error or no update will occur.
  • Missing required parameters: Both "Message ID" and "Message Translation" are required; missing these will cause the node to fail.
  • API response parsing errors: If the API returns unexpected data or an error string, the node attempts to parse it as JSON which might fail; verify API availability and response format.

Links and References

Discussion