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
The "Add Answer" operation in the "Answer Management" resource allows users to create a new answer entry within the Gladly system. This node is useful for customer support teams who want to add predefined answers that agents can use when responding to customers via email or messaging channels. By adding structured answers with associated metadata, agents can quickly find and provide consistent responses, improving efficiency and customer experience.
Practical examples include:
- Adding a new FAQ answer about resetting passwords.
- Creating canned responses for common customer inquiries.
- Associating answers with specific audience segments to tailor communication.
Properties
| Name | Meaning |
|---|---|
| Id | Unique identifier for the answer. Optional; if not provided, a new ID will be generated automatically. |
| Name | The customer-facing name of the answer, e.g., "How to reset your password". |
| Description | Additional information about the answer visible to agents during search, especially for email/messaging. |
| Audience Ids | A JSON array listing IDs of audiences associated with this answer, defining which customer groups see it. |
Output
The node outputs JSON data representing the newly created answer object as returned by the Gladly API. This typically includes the answer's unique ID, name, description, associated audience IDs, and any other metadata provided or generated by the service.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The node sends requests to the Gladly API endpoint (base URL shown as a placeholder in the source).
- Proper configuration of the API authentication in n8n credentials is necessary.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key is correctly configured in n8n credentials.
- Invalid JSON format in Audience Ids: The Audience Ids property expects a valid JSON array string; malformed JSON will cause errors.
- Duplicate Id error: If providing a custom Id, ensure it does not conflict with existing answers.
- Network or API errors: Check connectivity and API status; verify request headers and payload structure.
Links and References
- Gladly API documentation (replace with actual URL when available)
- n8n documentation on creating and using API credentials
- JSON formatting guides for inputting Audience Ids property