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 allows you to add a note to an existing conversation in the Gladly system. It is useful for customer support or service teams who want to append additional information, updates, or context to ongoing conversations with customers. For example, after speaking with a customer, an agent can add a detailed note summarizing the interaction or next steps directly into the conversation record.
Properties
| Name | Meaning |
|---|---|
| Conversation Id | The unique identifier of the conversation to which the note will be added. |
| Body | The content of the note. Can be plain text or rich content (HTML). This is the actual note text that will be appended to the conversation. |
Output
The node outputs JSON data representing the result of adding the note to the conversation. This typically includes confirmation details such as the note's ID, timestamp, and possibly the updated conversation state. The output does not include binary data.
Dependencies
- Requires access to the Gladly API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for the API is set to
https://petstore3.swagger.io/api/v3in the bundled code, but in practice should point to the actual Gladly API endpoint.
Troubleshooting
- Invalid Conversation Id: If the provided conversation ID does not exist or is malformed, the API will return an error. Verify the ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly configured.
- Malformed Note Content: If the body contains unsupported formatting or invalid HTML, the API might reject the request. Use valid plain text or properly formatted rich content.
- API Endpoint Issues: The default base URL in the code is a placeholder; ensure it is replaced with the correct Gladly API URL in your environment.
Links and References
- Gladly API Documentation (for detailed API usage and note formatting)
- n8n Documentation - Creating Custom Nodes