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 updates an existing Topic in the Gladly system. It allows users to modify key attributes of a Topic such as its name, whether it is disabled, and its parent Topic if it is nested. This is useful for maintaining an organized hierarchy of Topics or changing their status without deleting and recreating them.
Practical examples include:
- Renaming a Topic to better reflect its purpose.
- Disabling a Topic that is no longer relevant but should be retained for historical reasons.
- Changing the parent Topic to reorganize the topic structure.
Properties
| Name | Meaning |
|---|---|
| Name | The new name of the Topic. This is required and identifies the Topic to update. |
| Disabled | A boolean flag indicating if the Topic is currently not in use (true = disabled). |
| Parent Id | Optional ID of the parent Topic if this Topic is nested under another Topic. |
Output
The node outputs JSON data representing the updated Topic object as returned by the Gladly API. This typically includes the Topic's current properties such as its ID, name, disabled status, parent ID, and possibly other metadata fields depending on the API response.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The node uses the Gladly REST API endpoint to perform the update.
- Proper network access to the Gladly API base URL is necessary.
Troubleshooting
- Invalid or missing Topic ID: If the Topic to update is not specified correctly, the API may return an error indicating the resource was not found.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Validation errors: Providing invalid values for properties (e.g., empty name) may cause the API to reject the request.
- Network issues: Connectivity problems can prevent the node from reaching the Gladly API.
To resolve these:
- Double-check the Topic identifier and ensure it exists.
- Verify API credentials and permissions.
- Validate input property values before execution.
- Confirm network connectivity and proxy settings if applicable.
Links and References
- Gladly API Documentation (for Topics): Gladly API Docs
- n8n HTTP Request Node Documentation: n8n HTTP Request (useful for understanding API interactions)