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 answer by its unique identifier. It is useful in scenarios where you need to fetch detailed information about a particular answer stored in the Gladly system, such as for customer support ticketing or knowledge base management. For example, a user might want to pull an answer's content and metadata to display it in a custom dashboard or to use it in further automated workflows.
Properties
| Name | Meaning |
|---|---|
| Answer Id | The unique identifier of the answer to retrieve. This must be provided as a string. |
Output
The node outputs JSON data representing the details of the requested answer. This typically includes all fields returned by the Gladly API for that answer, such as the answer text, metadata, creation date, and any other relevant properties defined by the API schema. There is no binary output from this operation.
Dependencies
- Requires an active connection to the Gladly API.
- Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
- The base URL for the API requests is set to
https://petstore3.swagger.io/api/v3(likely a placeholder in the bundled code; should be replaced with the actual Gladly API endpoint).
Troubleshooting
- Invalid Answer Id: If the provided Answer Id does not exist or is malformed, the API will likely return an error indicating the resource was not found. Verify the correctness of the Answer Id.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key credential is properly configured.
- Network Issues: Connectivity problems can prevent the node from reaching the Gladly API. Check network settings and API availability.
- API Endpoint Configuration: The base URL in the bundled code points to a generic Swagger Petstore URL, which is not the real Gladly API. Make sure the node configuration uses the correct Gladly API endpoint.
Links and References
- Gladly API Documentation (replace with actual URL)
- n8n HTTP Request Node Documentation (for understanding API calls)