Which Flow Designer activities can send customer data outside the platform

Verified 2026-09-15 · 39 claims · sources tier 2

Also known as BRE Request, Notify URL, Use Authenticated Endpoint, secure variable.

The Start Media Stream activity streams live caller and agent voice media out of the call 19. WarmTransfer's reading of the sources is that Flow Designer carries at least 15 distinct activities or product features that can move data or media to a destination outside Webex Contact Center, though the article never presents such a list itself 8.

Web requests and API integrations

The HTTP Request activity supports 7 HTTP methods, 4 of which write to the receiving destination, and Cisco documentation describes no mechanism for an administrator to restrict which methods a flow author may use 9. Setting the activity's Use Authenticated Endpoint toggle to off replaces the connector configuration with a free-text Request URL typed directly into the flow, with no allow-list, domain restriction, or approval step described 22. Furthermore, the article contains no statement restricting the address an HTTP Request may target, with terms such as allowlist, firewall, egress, and residency occurring 0 times 11. The response timeout and retry count settings for the HTTP Request activity are each described as accepting any unlimited value 21.

The Business Rules Engine (BRE) Request activity arrives with the caller's phone number already configured as an Automatic Number Identification (ANI) query parameter, requiring a flow author to actively delete it to prevent transmission 4. The BRE Request documentation names no authentication mechanism, connector, or credential field, in contrast to the HTTP Request activity which explicitly documents Basic Auth and OAuth 2.0 options 5.

For identity verification, the Verify OTP activity provides an optional Notify URL field that posts a status payload to any endpoint specified by the flow author, without requiring a connector or credential field 23.

Voice media and recordings

Cisco documents from both ends that caller audio captured via the Record activity can be uploaded to an external third-party server or API using the HTTP Request activity 12. This upload can occur through the Request Body Value File sub-option, and a second file path exists through the HTTP Request activity's Form Data content type 12​13. Cisco states that audio recorded by the Record activity is stored in an unencrypted format, advises against recording sensitive information with it, and documents uploading that audio to third-party endpoints 14.

The Start Media Stream activity streams live caller and agent voice media out of the call 19. The Flow Designer documentation states no destination, protocol, authentication, encryption, or payload description for the activity, although the activity appears in Flow Designer's self-loop limit table with a limit of 20 19​20.

SIP headers and browser egress

Incoming session initiation protocol headers are ingested into a flow variable in JSON form, holding up to 20 headers and 1000 bytes 10. Outgoing SIP headers configured during transfer activities are capped at 20 headers per INVITE 18. Cisco provides an outbound-data warning naming 5 categories of information not to place in SIP headers, which is scoped to the smallest payload the platform transmits 17.

The Screen Pop activity sends flow variables to a free-text external URL by opening it in the agent's browser, with no connector, credential, or domain restriction described 15.

Egress visibility and logging controls

The documentation for Flow Designer says nothing about transport security for any outbound call, with the terms encryption, transport layer security, in transit, and at rest each occurring 0 times 2. Furthermore, the word audit does not appear in the Flow Designer documentation, describing no audit trail for outbound calls, changes to egress configurations, or use of the decrypt control 3.

Operational visibility into outbound calls per interaction is restricted to the Debug pane, which retains only the most recent 100 interactions for the flow 6. Flow log decryption applies solely to calls initiated after the flow is published, preventing an investigator from enabling decryption to read data that a flow transmitted prior to that point 7. While the documentation states that a secure variable prevents the logging and storing of a value, it never states whether a secure variable may be placed in an outbound payload 16.

Applicability

Across the claims in this article, the evidence covers Cisco Webex Contact Center, verified as of 2026-09-15. The deployment model is not covered by any claim in this article.

What remains uncertain

Whether Flow Designer Functions code can open a network connection is not covered by any claim in this article.

Cisco documentation states that a secure variable prevents logging and storing a value, but whether a secure variable may be placed in an outbound payload is not covered by any claim in this article 16.

What a Control Hub integration connector stores and who may create it is not covered by any claim in this article.

Payload and rate limits for the egress activities are not covered by any claim in this article.

Whether reserved SIP header patterns are stripped from outgoing INVITEs is not covered by any claim in this article.

See also

• The Webex Contact Center Flow Designer activity set
• The Start Media Stream activity and what feeds on it
• What each Webex Contact Center connector type stores
• Author-written functions in Flow Designer

WarmTransfer. (2026, September 15). Which Flow Designer activities can send customer data outside the platform. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-flow-data-egress

@misc{warmtransfer-wxcc-flow-data-egress,
  title  = {Which Flow Designer activities can send customer data outside the platform},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-flow-data-egress},
  note   = {Verified 2026-09-15}
}