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 retrieves all conversations associated with a specific customer. It is useful in scenarios where you want to fetch the communication history or ongoing interactions for a given customer within a system that manages conversations, such as a customer support platform.
Practical examples include:
- Displaying all past and current conversations of a customer in a CRM.
- Analyzing customer interaction history for support quality assessment.
- Automating workflows based on conversation data, like triggering follow-ups.
Properties
| Name | Meaning |
|---|---|
| Customer Id | The unique identifier of the customer whose conversations you want to retrieve. |
Output
The output contains a JSON object representing the list of conversations for the specified customer. Each item in the output corresponds to a conversation record, typically including details such as conversation ID, timestamps, participants, messages, and status.
If the node supports binary data (not evident from the provided code), it would represent attachments or media related to conversations, but this is not indicated here.
Dependencies
- Requires an API key credential to authenticate requests to the Gladly API.
- The base URL for API requests is set to
https://petstore3.swagger.io/api/v3(likely a placeholder). - The node depends on the
@devlikeapro/n8n-openapi-nodepackage for building properties from the OpenAPI specification.
Troubleshooting
- Missing or invalid Customer Id: Ensure the Customer Id property is provided and correctly formatted; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is configured properly in n8n.
- API endpoint issues: The base URL appears to be a placeholder; confirm that the correct Gladly API endpoint is used.
- Network or connectivity problems: Check network access to the API server.
Common error messages might include authentication failures, resource not found (if the customer ID does not exist), or rate limiting errors from the API.
Links and References
- Gladly API Documentation (for detailed API usage)
- n8n OpenAPI Node Package