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 update (patch) an existing conversation in the Gladly system. It is useful for modifying details of a conversation such as changing its assignee or updating its status. Typical use cases include reassigning conversations to different agents or inboxes, marking conversations with new statuses, or automating workflow steps based on conversation updates.
For example, you might use this node to:
- Assign a conversation to a specific agent and inbox after it has been created.
- Change the status of a conversation to indicate progress or resolution.
Properties
| Name | Meaning |
|---|---|
| Conversation Id | The unique identifier of the conversation you want to update. |
| Assignee | JSON object specifying the new assignee details. It includes: |
- agentId: The ID of the agent to assign the conversation to. |
|
- inboxId: The ID of the inbox where the conversation should be assigned. |
|
| Status | JSON object specifying status update details. It includes: |
- force: A boolean indicating whether to force the status update (true or false). |
Output
The node outputs the updated conversation data in the json field of the output item. This typically contains the full conversation object reflecting the changes made by the patch operation, including updated assignee and status fields.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The node uses the Gladly REST API endpoint (base URL shown as a placeholder in the source).
- Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
- Invalid Conversation Id: If the provided conversation ID does not exist or is malformed, the API will return an error. Verify the conversation ID before running the node.
- Malformed JSON in Assignee or Status: Since these properties expect JSON strings that are parsed, invalid JSON syntax will cause errors. Ensure valid JSON formatting.
- Permission Issues: If the API key lacks permissions to update conversations, the request will fail. Confirm the API key has appropriate scopes.
- Network or API Errors: Temporary network issues or API downtime can cause failures. Retry or check API status if errors occur.
Links and References
- Gladly API Documentation (for Conversations): https://developer.gladly.com/api/conversations
- n8n Documentation on HTTP Request Nodes and JSON Handling: https://docs.n8n.io/