Source record · tier 2 current vendor documentation
Transfer conversation - WxEngage standalone
- Publisher
- Cisco Systems, Inc. (Webex Connect documentation)
- URL
- https://help.webexconnect.io/docs/transfer-conversation
- Published
- unknown
- Updated
- unknown
- Accessed
- 2026-09-15
- HTTP status
- 200
- License
- Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only
Claims citing this source
- Cisco recommends setting the node's authorization to a default authentication configured in Engage's integrations screen, because re-authenticating there updates the token for every node across every flow. fact in context
- The transfer node is addressed by a conversation identifier held in a flow variable, which is the identity a digital interaction is transferred by. fact in context
- The transfer node is a wrapper over the Transfer conversation API from Webex Engage, so a digital transfer configured in a Webex Connect flow is executed by a different product. fact in context
- The transfer node's own configuration procedure instructs the reader to double-click the Fetch team working hours node, and it does so in both the team queue and the skill queue variants. disputed in context
- The transfer node publishes one success outcome and six named error outcomes: transfer failed, timeout, invalid data, middleware error, invalid choice and authorization failure, with a seventh unnamed Failure category for any other runtime failure. field-pattern in context
- The timeout outcome means no API response was received within the agreed time, so it does not say whether the transfer happened, and a flow taking that branch cannot know the conversation's state. inference in context
- A digital conversation is transferred to a team queue or to a skill queue, and the transfer node offers those two targets and no option to name an agent. field-pattern in context
- The node's only output variable is a request identifier generated by Webex Engage, so what the flow gets back identifies the API call and not the transferred conversation. fact in context
Cite this source record
APA
WarmTransfer. (2026, September 15). Transfer conversation - WxEngage standalone. WarmTransfer. https://warmtransfer.net/knowledge/sources/webexconnect-docs-transfer-conversation-node
BibTeX
@misc{warmtransfer-webexconnect-docs-transfer-conversation-node,
title = {Transfer conversation - WxEngage standalone},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/webexconnect-docs-transfer-conversation-node},
note = {Cisco Systems, Inc. (Webex Connect documentation), accessed 2026-09-15}
}