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, Handoff Automation Session under the Message Automation resource, allows users to hand off an ongoing automation session to a live agent. This is useful in customer support or service automation scenarios where automated messaging reaches a point that requires human intervention. For example, if a chatbot cannot resolve a customer's issue, this operation can transfer the session to a human agent with a description explaining why the handoff is necessary.
Properties
| Name | Meaning |
|---|---|
| Session Id | The unique identifier of the automation session to be handed off. |
| Description | A brief, mandatory explanation for handing off the session to an agent (cannot be blank). |
Output
The output JSON will typically contain confirmation details about the handoff action performed on the specified automation session. This may include status information or metadata confirming the session was successfully transferred to an agent. There is no indication that binary data is involved in this operation.
Dependencies
- Requires access to the Gladly API endpoint configured via an API key credential.
- The node uses standard HTTP headers (
Accept: application/jsonandContent-Type: application/json) and connects to the Gladly API base URL. - Proper API authentication credentials must be set up in n8n for the Gladly service.
Troubleshooting
- Missing or invalid Session Id: Ensure the session ID provided exists and is correctly formatted.
- Empty Description: The description field is required and cannot be blank; provide a meaningful reason for the handoff.
- API Authentication Errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API Endpoint Issues: Confirm network connectivity and that the Gladly API endpoint is reachable.
- Unexpected API Responses: Check the API documentation for error codes and ensure request payloads conform to expected formats.
Links and References
- Gladly API Documentation (for Message Automation and session handoff): Gladly API Docs
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/