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 allows you to reply to a message within a conversation using the Gladly API. It is useful in customer service automation workflows where you want to programmatically send replies to ongoing conversations, for example, responding to customer inquiries or support tickets directly from an n8n workflow.
Practical examples include:
- Automatically sending follow-up messages after processing customer data.
- Integrating with other systems to trigger replies based on external events.
- Streamlining customer communication by automating responses.
Properties
| Name | Meaning |
|---|---|
| Item Id | The unique identifier of the conversation item (message) you want to reply to. |
| Content | The content of the reply message. This is a JSON object that includes both HTML and plain text versions of the message body. Example structure: json { "body": "<h1>Customer service is being reinvented by Gladly</h1>", "bodyPlain": "Customer service is being reinvented by Gladly" } |
Output
The node outputs JSON data representing the response from the Gladly API after posting the reply message. This typically includes details about the newly created reply message such as its ID, timestamps, and content confirmation.
If the API supports binary data (e.g., attachments), it would be included accordingly, but based on the provided code and properties, the primary output is JSON structured message data.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The base URL for the API is set to
https://petstore3.swagger.io/api/v3in the bundled source, which appears to be a placeholder; in a real scenario, this should be replaced with the actual Gladly API endpoint. - The node depends on the
@devlikeapro/n8n-openapi-nodepackage for building properties from the OpenAPI specification.
Troubleshooting
- Invalid or missing Item Id: Ensure the conversation item ID is correct and exists in the Gladly system.
- Malformed Content JSON: The content must be valid JSON with required fields (
bodyandbodyPlain). Invalid JSON will cause errors. - Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- API endpoint issues: Confirm the base URL points to the correct Gladly API endpoint rather than a placeholder.
- Network or connectivity problems: Check network access to the Gladly API server.
Links and References
- Gladly API documentation (replace with actual URL when available)
- n8n OpenAPI Node integration guide: https://docs.n8n.io/integrations/creating-nodes/openapi/
- JSON formatting guide: https://www.json.org/json-en.html