Source note · Calling an external API from a Webex Contact Center flow
Because a JSONPath that matches nothing returns an empty result, and Cisco does not document what Flow Designer writes to the output variable in that case, a lookup flow should test the parsed variable for empty before routing on it.
inferred · Checked 2026-09-30
- Vendor
- Cisco
- Product
- Webex Contact Center
- Subsystem
- Flow Designer HTTP Request activity
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Status
- inferred
- Checked
- 2026-09-30
Sources
- RFC 9535: JSONPath: Query Expressions for JSON — IETF · tier 1 standards and regulators · Section 2.1.2, applied to Flow Designer Parse Settings
Cite this note
APA
WarmTransfer. (2026, September 30). Calling an external API from a Webex Contact Center flow: source note wxcc-http-request-setup-empty-match-check. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxcc-http-request-setup-empty-match-check
BibTeX
@misc{warmtransfer-claim-wxcc-http-request-setup-empty-match-check,
title = {Calling an external API from a Webex Contact Center flow: source note wxcc-http-request-setup-empty-match-check},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxcc-http-request-setup-empty-match-check},
note = {Source note wxcc-http-request-setup-empty-match-check, checked 2026-09-30}
}