Actions57
- Agents Actions
- Public Answer Actions
- Answer Management Actions
- Communications Actions
- Customers Actions
- Conversations Actions
- Get Conversations
- Get Conversation
- Patch Conversation
- Create Item
- Get Item
- Delete Item
- Get Media
- Get Voice Transcript
- Create Customer Item
- Delete Customer Item
- Get Conversation Items
- Add Topic To Conversation
- Delete Topic From Conversation
- Add Note To Conversation
- Get Note From Conversation
- Reply To Message
- Redact Content
- Export Actions
- Freeform Topics Actions
- Message Automation Actions
- Proactive Conversations Actions
- Tasks Actions
- User Identity Actions
- Topics Actions
- Webhooks Actions
- Payloads Actions
Overview
This node operation allows users to add or update the content of an existing answer in multiple languages and types within an Answer Management system. It is particularly useful for managing multilingual support content, FAQs, or knowledge base articles where answers need to be tailored by language and content type (e.g., public-facing content). For example, a customer support team can use this node to add a Spanish version of a password reset instruction that is publicly visible.
Properties
| Name | Meaning |
|---|---|
| Answer Id | The unique identifier of the answer to which content will be added or updated. |
| Language | The language code (ISO 639 format) specifying the language of the content being added. |
| Type | The type of answer content; must be set to public indicating publicly visible content. |
| Body Html | The HTML body content of the answer, representing the main text or message shown to users. |
| Title | The title of the answer content, summarizing the subject or purpose of the answer. |
Output
The node outputs JSON data representing the result of the add/update operation on the answer content. This typically includes confirmation details such as the updated answer ID, language, type, and the content fields (title and body). There is no indication of binary data output.
Dependencies
- Requires access to the Gladly API endpoint configured with a valid API key credential.
- The node expects the organization to have the specified language configured.
- Network connectivity to the Gladly API service is necessary.
- No additional environment variables are explicitly required beyond standard API authentication setup.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Answer Id will likely cause the operation to fail.
- Using a language code not configured for the organization will result in errors.
- Setting the Type to anything other than
publicis not supported and may cause rejection. - Malformed HTML in the Body Html property could lead to unexpected rendering or API errors.
Error Messages:
- "Answer not found" — Verify the Answer Id is correct and exists.
- "Language not supported" — Ensure the language code matches one configured in your org.
- "Invalid type" — Confirm the Type property is set to
public. - "Authentication failed" — Check that the API key credential is correctly configured and valid.
Links and References
- Gladly API Documentation (for detailed API usage and language configuration)
- ISO 639 Language Codes (for valid language codes)