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 you to add one or more topics to an existing conversation within the Gladly platform. It is useful for categorizing or tagging conversations with relevant topics, which can help in organizing, filtering, and managing customer interactions more effectively.
Practical examples:
- Automatically tagging a customer support conversation with specific issue categories.
- Adding multiple topic identifiers to a conversation based on detected keywords or sentiment analysis.
- Updating conversation metadata to reflect new developments or changes in the discussion context.
Properties
| Name | Meaning |
|---|---|
| Conversation Id | The unique identifier of the conversation to which topics will be added. |
| Topic Ids | A JSON array of topic identifiers that should be added to the specified conversation. |
Output
The node outputs JSON data representing the updated conversation after the topics have been added. This typically includes the conversation details along with the newly associated topics.
If binary data were involved (e.g., attachments), it would be summarized here, but this operation deals only with JSON data related to conversation metadata.
Dependencies
- Requires an API key credential for authenticating requests to the Gladly API.
- The node uses the Gladly API endpoint configured with a base URL (default shown as a placeholder).
- Proper network access to the Gladly API service is necessary.
Troubleshooting
- Invalid Conversation Id: If the provided conversation ID does not exist or is malformed, the API may return an error indicating the conversation was not found. Verify the ID before running the node.
- Malformed Topic Ids JSON: The
Topic Idsproperty expects a valid JSON array. Invalid JSON syntax will cause parsing errors. Ensure the input is correctly formatted. - Authentication Errors: Missing or invalid API credentials will result in authorization failures. Confirm that the API key is set up correctly in n8n credentials.
- API Rate Limits or Downtime: If the Gladly API is unreachable or rate-limited, the node will fail. Check API status and retry later if needed.
Links and References
- Gladly API Documentation (for detailed API usage and topic/conversation management)
- n8n Documentation (for general guidance on using credentials and JSON properties)