CoachTrigger Dev icon

CoachTrigger Dev

Interact with coach trigger action development server API

Actions16

Overview

This node interacts with a Coach Trigger development server API to manage and update messages, user data, activities, and reports related to coaching workflows. Specifically, the "Update Message Translation" operation allows users to update the translation of an existing message in the system. This is useful in multilingual coaching environments where messages need to be localized or corrected after initial creation.

Practical scenarios include:

  • Updating translations of coaching messages after receiving improved or corrected translations.
  • Maintaining consistent multilingual communication within a coaching platform.
  • Automating updates to message content based on feedback or new language support.

Properties

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

Output

The node outputs JSON data representing the response from the API after attempting to update the message translation. The structure typically contains confirmation of the update or details about the updated message. No binary data output is involved.

Example output JSON structure (simplified):

{
  "success": true,
  "message_id": "12345",
  "updated_translation": "Updated translated text"
}

Dependencies

  • Requires access to the Coach Trigger development server API at https://dev.mymatrixapp.com/crmApi/message/update.
  • Requires either a company API key or a system API key credential configured in n8n for authentication.
  • Network connectivity to the API endpoint.

Troubleshooting

  • Authentication errors: Ensure that the correct type of API key is selected and properly configured in n8n credentials. Using the wrong key type will cause authorization failures.
  • Invalid Message ID: If the message ID does not exist or is incorrect, the API may return an error indicating the message was not found.
  • Missing required parameters: Both "Message ID" and "Message Translation" are required; omitting them will cause the node to fail.
  • API endpoint issues: Network problems or changes in the API URL can cause request failures. Verify the endpoint URL and network access.
  • JSON parsing errors: If the API returns malformed JSON, the node might throw parsing errors. Check API stability and response format.

Links and References

Discussion