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 deletes specific answer content from the Gladly platform based on language and type. It is useful when you want to remove localized or categorized answer content entries, for example, removing outdated or incorrect public-facing answers in a particular language or deleting internal reference answers.
Practical scenarios include:
- Cleaning up answer content that is no longer relevant in a certain language.
- Removing email-specific answer templates that need to be replaced.
- Managing multilingual content by selectively deleting answers per language.
Properties
| Name | Meaning |
|---|---|
| Answer Id | The unique identifier of the answer to delete content from. |
| Language | The language code (ISO 639 format) specifying which language version of the answer to delete. The language must be configured for the organization. |
| Type | The category/type of the answer content to delete. Must be one of: public, email, messaging, or reference. |
Output
The node outputs JSON data representing the result of the deletion operation. Typically, this will confirm whether the deletion was successful or provide details about the deleted content. There is no indication that binary data is output by this operation.
Dependencies
- Requires an API key credential to authenticate with the Gladly API.
- The node depends on the Gladly API being accessible at its base URL.
- Proper configuration of languages and answer types within the Gladly organization is necessary for the operation to succeed.
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.
- Specifying an unsupported type value outside of
public,email,messaging, orreferencewill cause validation errors. - Network or authentication failures can prevent the API call from succeeding.
Error messages and resolutions:
- "Answer not found": Verify the Answer Id is correct and exists.
- "Language not supported": Ensure the language code matches one configured in your Gladly org.
- "Invalid type parameter": Use only the allowed types listed above.
- Authentication errors: Check that the API key credential is valid and has proper permissions.
Links and References
- Gladly API Documentation (for managing answers): Gladly Developer Portal
- ISO 639 Language Codes: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes