WbCommunication

Overview

This node operation allows updating (patching) existing response templates by modifying their name and text content. It is useful in scenarios where you need to maintain or update predefined message templates dynamically, such as customer support replies, automated notifications, or marketing messages. For example, if a company wants to update the wording of a frequently used email template without creating a new one, this operation enables that by specifying the template ID and new content.

Properties

Output

The node outputs JSON data representing the updated template after the patch operation. This typically includes the template's ID, updated name, and text fields reflecting the changes made. There is no indication that binary data is output by this node.

Dependencies

• Requires an API key credential for authentication with the external service managing the templates.
• The node uses a base URL configured from an imported OpenAPI specification.
• The node sends HTTP PATCH requests with JSON bodies containing the updated template data.

Troubleshooting

• Common issues:
  • Providing an invalid or non-existent Template ID will likely result in an error indicating the template was not found.
  • Omitting required properties (Name, Template ID, or Text) will cause validation errors before the request is sent.
  • Text length outside the allowed range (less than 2 or more than 1000 characters) may cause rejection by the API.
• Error messages:
  • "Template not found" or similar indicates the Template ID does not exist; verify the ID.
  • Validation errors about missing or invalid fields require checking input property values.
• To resolve these, ensure all required fields are correctly filled and the Template ID corresponds to an existing template.

Links and References

• No direct links provided in the source code.
• Refer to the external API documentation for the template management service for detailed information on PATCH operations and field constraints.