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 allows you to add a new Topic in the Gladly system. Topics are used to categorize or group conversations, requests, or tickets within the platform. Adding a Topic is useful when you want to organize your customer interactions by specific subjects or themes, such as "Order Returns" or "Technical Support."
Practical examples include:
- Creating a new Topic for a product launch to track all related customer inquiries.
- Adding nested Topics under a parent Topic to create a hierarchical structure for better organization.
- Disabling Topics that are no longer relevant without deleting them.
Properties
| Name | Meaning |
|---|---|
| Id | Unique identifier for the Topic. Optional; if not provided, a new id will be generated. |
| Name | Name of the Topic. Must be unique. This is a required field. |
| Disabled | Boolean flag indicating if the Topic is inactive (true) or active (false). Defaults to false. |
| Parent Id | Identifier of the parent Topic if this Topic is nested under another. Optional. |
Output
The node outputs JSON data representing the newly created Topic object. This typically includes the Topic's id, name, disabled status, and parent id if applicable. The output can be used downstream in workflows to reference the created Topic or to confirm successful creation.
No binary data output is involved.
Dependencies
- Requires an API key credential to authenticate with the Gladly API.
- The node communicates with the Gladly REST API endpoint at
https://petstore3.swagger.io/api/v3(placeholder URL in source). - Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
- Duplicate Topic Name Error: Since the Topic name must be unique, attempting to add a Topic with an existing name may result in an error. Ensure the name is unique before adding.
- Invalid Parent Id: Providing a non-existent or invalid parent Topic id may cause the operation to fail. Verify the parent id exists.
- Authentication Errors: Missing or incorrect API credentials will prevent the node from connecting to the Gladly API. Confirm that the API key is correctly configured.
- Network Issues: Connectivity problems or incorrect base URL settings can cause request failures. Check network access and API endpoint correctness.
Links and References
- Gladly API Documentation (replace with actual URL)
- n8n Documentation on HTTP Request Nodes and Credentials Management