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 interacts with the Gladly API to retrieve the content of a specific answer based on its ID, language, and type. It is useful in scenarios where you need to fetch localized answer content for customer support or knowledge base systems that use Gladly. For example, a support workflow could dynamically load an answer in the customer's preferred language and format (public, email, messaging, or reference) to provide consistent and relevant responses.
Properties
| Name | Meaning |
|---|---|
| Answer Id | The unique identifier of the answer to retrieve. |
| Language | The language code (ISO 639 format) specifying the language of the answer content to fetch. |
| Type | The type of answer content to retrieve. Must be one of: public, email, messaging, or reference. |
Output
The node outputs JSON data containing the content of the requested answer filtered by the specified language and type. The exact structure depends on the Gladly API response but typically includes fields such as the answer text and metadata related to the answer content.
No binary data output is indicated.
Dependencies
- Requires access to the Gladly API endpoint.
- Needs an API key or authentication token configured in n8n credentials to authorize requests to the Gladly service.
- The base URL for the API is set to
https://petstore3.swagger.io/api/v3in the bundled code, which is likely a placeholder and should be replaced with the actual Gladly API endpoint.
Troubleshooting
- Invalid Answer Id: If the provided answer ID does not exist, the API may return an error or empty result. Verify the ID is correct.
- Unsupported Language: The language must be configured for the organization in Gladly; otherwise, no content will be returned.
- Invalid Type: The type must be one of the allowed values (
public,email,messaging,reference). Using an unsupported type will cause errors. - Authentication Errors: Ensure the API key or authentication token is correctly set up in n8n credentials.
- API Endpoint Misconfiguration: The default base URL points to a Swagger petstore demo. Replace it with the real Gladly API URL to avoid connection failures.
Links and References
- Gladly API Documentation (for detailed API usage and answer management)
- ISO 639 Language Codes (for valid language codes)