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 a specific topic from an existing conversation in the Gladly system. It is useful when you want to remove outdated, irrelevant, or incorrect topics associated with a conversation to keep the conversation context clean and accurate.
Practical examples include:
- Removing a resolved issue topic from a customer support conversation.
- Deleting mistakenly added topics that no longer apply to the ongoing conversation.
- Cleaning up conversation metadata before archiving or reporting.
Properties
| Name | Meaning |
|---|---|
| Conversation Id | The unique identifier of the conversation from which the topic will be deleted. |
| Topic Id | The unique identifier of the topic to be removed from the specified conversation. |
Output
The output JSON typically contains the response from the Gladly API confirming the deletion of the topic from the conversation. This may include status information or confirmation details. There is no indication that binary data is returned by this operation.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The node uses the Gladly API endpoint (base URL:
https://petstore3.swagger.io/api/v3as per bundled code, but likely replaced with the actual Gladly API URL in production). - Proper network access to the Gladly API service is necessary.
Troubleshooting
- Invalid Conversation Id or Topic Id: If either ID is incorrect or does not exist, the API will likely return an error indicating the resource was not found. Verify IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly configured.
- Permission Issues: The API user must have permission to modify conversations and delete topics.
- Network Issues: Connectivity problems can cause request failures; check network settings and API availability.
Links and References
- Gladly API Documentation (for managing conversations and topics)
- n8n Documentation on creating and using API nodes
- REST API best practices for error handling and authentication