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 "Get Media" under the "Conversations" resource is designed to retrieve media associated with a specific conversation item. It is useful in scenarios where you need to access attachments, images, or other media files linked to messages or conversation entries within a customer support or communication platform.
For example, if a support agent wants to download an image sent by a customer during a chat, this operation can fetch that media using the unique identifier of the conversation item.
Properties
| Name | Meaning |
|---|---|
| Item Id | The unique identifier of the conversation item whose media you want to retrieve. |
Output
The output will contain JSON data representing the media associated with the specified conversation item. This typically includes metadata about the media and possibly the media content itself or a link to it.
If the media is binary (e.g., images, videos), the node may output binary data corresponding to the media file, allowing further processing or saving within n8n workflows.
Dependencies
- Requires an API key credential for authenticating with the Gladly API service.
- The node communicates with the Gladly API endpoint (base URL:
https://petstore3.swagger.io/api/v3as per the bundled code, which is likely a placeholder). - Proper configuration of the API credentials in n8n is necessary to successfully call the API.
Troubleshooting
- Invalid or missing Item Id: Ensure the "Item Id" property is correctly set and corresponds to an existing conversation item.
- Authentication errors: Verify that the API key credential is valid and has the necessary permissions.
- API endpoint issues: The base URL in the bundled code points to a pet store example; ensure the actual Gladly API endpoint is configured correctly in your environment.
- Media not found: If no media exists for the given item ID, the node might return empty results or an error indicating no media available.
Links and References
- Gladly API Documentation (for detailed API usage and authentication)
- n8n Documentation - Creating Custom Nodes