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 a specific public answer by its ID within an organization. It is useful when you want to fetch detailed information about a particular answer that has been made publicly available, for example, to display FAQs or support answers dynamically in your workflow.
A practical use case would be integrating this node into a customer support automation where you need to pull a specific answer from your organization's knowledge base and present it to users or use it in further processing steps.
Properties
| Name | Meaning |
|---|---|
| Org Id | The unique identifier of your organization. You can find this ID using the "Get organization" API call. |
| Answer Id | The unique identifier of the public answer you want to retrieve. |
| Lng | The language code for the answer content (e.g., "en-us"). This controls the language of the returned data. |
Output
The node outputs JSON data representing the details of the requested public answer. This typically includes fields such as the answer's content, metadata, language, and any other relevant information provided by the Gladly API for that answer.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The node uses the Gladly API endpoint at
https://petstore3.swagger.io/api/v3(likely a placeholder URL in the bundled code). - Proper configuration of the API authentication token or key in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing organization ID or answer ID will result in errors or empty responses.
- Incorrect or expired API credentials will cause authentication failures.
- Providing an unsupported language code may lead to default language responses or errors.
Error messages:
- Authentication errors usually indicate invalid API keys; verify and update credentials.
- Not found errors suggest the specified answer or organization ID does not exist; double-check IDs.
- Network or timeout errors require checking connectivity and API availability.
Links and References
- Gladly API documentation (for organization and answer endpoints) — consult the official Gladly API docs.
- n8n documentation on creating and using API credentials.
- Language codes reference for specifying the
Lngproperty (e.g., ISO language codes).