Labs · early, not fully tested. Check what it produces before you rely on it.
{"version":"2026-09-22.3","entries":[{"code":"missing-error-path","topicSlug":"wxcc-flow-designer-activities","topicTitle":"The Webex Contact Center Flow Designer activity set","articleHref":"/knowledge/wxcc-flow-designer-activities","askHref":"/?topic=wxcc-flow-designer-activities","claims":[{"id":"wxfdcat-error-handling-has-three-tiers","text":"Error handling runs 3 tiers deep: an activity's own error path, then a global error event flow, then the flow ends.","status":"fact","verifiedAt":"2026-09-05","href":"/knowledge/claims/wxfdcat-error-handling-has-three-tiers","sources":[{"id":"cisco-help-nhovcy4-wxcc-flow-designer","title":"Build and manage flows with Flow Designer","publisher":"Cisco Systems, Inc. (Webex Help Center)","tier":2,"tierLabel":"current vendor documentation","locator":"Flow Designer, configure error handling","href":"/knowledge/sources/cisco-help-nhovcy4-wxcc-flow-designer"}]},{"id":"wxcc-fd-onglobalerror-is-the-fallback","text":"If a flow developer does not configure an error handling path for an activity, execution falls back to the path defined in the OnGlobalError event handler.","status":"fact","verifiedAt":"2026-09-04","href":"/knowledge/claims/wxcc-fd-onglobalerror-is-the-fallback","sources":[{"id":"cisco-help-nhovcy4-wxcc-flow-designer","title":"Build and manage flows with Flow Designer","publisher":"Cisco Systems, Inc. (Webex Help Center)","tier":2,"tierLabel":"current vendor documentation","locator":"Configure error handling","href":"/knowledge/sources/cisco-help-nhovcy4-wxcc-flow-designer"}]},{"id":"wxfep-six-activities-have-named-branches","text":"Only 6 Flow Designer activities carry error branches beyond the generic undefined error node: menu, collect digits, virtual agent, virtual agent version 2, queue to agent and cryptographic hash.","status":"fact","verifiedAt":"2026-09-15","href":"/knowledge/claims/wxfep-six-activities-have-named-branches","sources":[{"id":"cisco-help-nhovcy4-wxcc-flow-designer","title":"Build and manage flows with Flow Designer","publisher":"Cisco Systems, Inc. (Webex Help Center)","tier":2,"tierLabel":"current vendor documentation","locator":"Flow Designer, activity error outputs","href":"/knowledge/sources/cisco-help-nhovcy4-wxcc-flow-designer"}]}]},{"code":"mutating-http-request","topicSlug":"wxcc-flow-data-egress","topicTitle":"Which Flow Designer activities can send customer data outside the platform","articleHref":"/knowledge/wxcc-flow-data-egress","askHref":"/?topic=wxcc-flow-data-egress","claims":[{"id":"flowgress-http-request-methods","text":"The HTTP Request activity supports 7 HTTP methods, 4 of which write to the destination, and the article describes no mechanism for an administrator to restrict which methods a flow author may use.","status":"fact","verifiedAt":"2026-09-05","href":"/knowledge/claims/flowgress-http-request-methods","sources":[{"id":"cisco-help-nhovcy4-wxcc-flow-designer","title":"Build and manage flows with Flow Designer","publisher":"Cisco Systems, Inc. (Webex Help Center)","tier":2,"tierLabel":"current vendor documentation","locator":"HTTP Request step 3, Method Types","href":"/knowledge/sources/cisco-help-nhovcy4-wxcc-flow-designer"}]},{"id":"flowgress-record-audio-to-third-party-form-data-second-path","text":"A second file path for uploading a Record activity's captured caller audio to an external third-party server exists through the HTTP Request activity's Form Data content type, in addition to the File sub-option.","status":"fact","verifiedAt":"2026-09-05","href":"/knowledge/claims/flowgress-record-audio-to-third-party-form-data-second-path","sources":[{"id":"cisco-help-nhovcy4-wxcc-flow-designer","title":"Build and manage flows with Flow Designer","publisher":"Cisco Systems, Inc. (Webex Help Center)","tier":2,"tierLabel":"current vendor documentation","locator":"HTTP Request step 3, Request Body Value, File sub-option; Record step 8, Output Variables note","href":"/knowledge/sources/cisco-help-nhovcy4-wxcc-flow-designer"}]},{"id":"flowgress-record-audio-to-third-party","text":"Cisco documents, from both ends, that a Record activity's captured caller audio can be uploaded to an external third-party server or API through the HTTP Request activity.","status":"fact","verifiedAt":"2026-09-05","href":"/knowledge/claims/flowgress-record-audio-to-third-party","sources":[{"id":"cisco-help-nhovcy4-wxcc-flow-designer","title":"Build and manage flows with Flow Designer","publisher":"Cisco Systems, Inc. (Webex Help Center)","tier":2,"tierLabel":"current vendor documentation","locator":"HTTP Request step 3, Request Body Value, File sub-option; Record step 8, Output Variables note","href":"/knowledge/sources/cisco-help-nhovcy4-wxcc-flow-designer"}]}]},{"code":"plain-http-endpoint","topicSlug":"wxcc-flow-data-egress","topicTitle":"Which Flow Designer activities can send customer data outside the platform","articleHref":"/knowledge/wxcc-flow-data-egress","askHref":"/?topic=wxcc-flow-data-egress","claims":[{"id":"flowgress-http-request-methods","text":"The HTTP Request activity supports 7 HTTP methods, 4 of which write to the destination, and the article describes no mechanism for an administrator to restrict which methods a flow author may use.","status":"fact","verifiedAt":"2026-09-05","href":"/knowledge/claims/flowgress-http-request-methods","sources":[{"id":"cisco-help-nhovcy4-wxcc-flow-designer","title":"Build and manage flows with Flow Designer","publisher":"Cisco Systems, Inc. (Webex Help Center)","tier":2,"tierLabel":"current vendor documentation","locator":"HTTP Request step 3, Method Types","href":"/knowledge/sources/cisco-help-nhovcy4-wxcc-flow-designer"}]},{"id":"flowgress-record-audio-to-third-party","text":"Cisco documents, from both ends, that a Record activity's captured caller audio can be uploaded to an external third-party server or API through the HTTP Request activity.","status":"fact","verifiedAt":"2026-09-05","href":"/knowledge/claims/flowgress-record-audio-to-third-party","sources":[{"id":"cisco-help-nhovcy4-wxcc-flow-designer","title":"Build and manage flows with Flow Designer","publisher":"Cisco Systems, Inc. (Webex Help Center)","tier":2,"tierLabel":"current vendor documentation","locator":"HTTP Request step 3, Request Body Value, File sub-option; Record step 8, Output Variables note","href":"/knowledge/sources/cisco-help-nhovcy4-wxcc-flow-designer"}]},{"id":"flowgress-record-audio-to-third-party-form-data-second-path","text":"A second file path for uploading a Record activity's captured caller audio to an external third-party server exists through the HTTP Request activity's Form Data content type, in addition to the File sub-option.","status":"fact","verifiedAt":"2026-09-05","href":"/knowledge/claims/flowgress-record-audio-to-third-party-form-data-second-path","sources":[{"id":"cisco-help-nhovcy4-wxcc-flow-designer","title":"Build and manage flows with Flow Designer","publisher":"Cisco Systems, Inc. (Webex Help Center)","tier":2,"tierLabel":"current vendor documentation","locator":"HTTP Request step 3, Request Body Value, File sub-option; Record step 8, Output Variables note","href":"/knowledge/sources/cisco-help-nhovcy4-wxcc-flow-designer"}]}]}]}Flow Studio
Loading the local flow reviewer…